... | @@ -54,7 +54,7 @@ Tor Project websites, the first step is to request access. This can be done by |
... | @@ -54,7 +54,7 @@ Tor Project websites, the first step is to request access. This can be done by |
|
joining the `#tor-www` channel on IRC and asking!
|
|
joining the `#tor-www` channel on IRC and asking!
|
|
|
|
|
|
The access level granted for website content contributors is normally
|
|
The access level granted for website content contributors is normally
|
|
*Developper*. This role grants the ability to push new branches to the GitLab
|
|
*Developer*. This role grants the ability to push new branches to the GitLab
|
|
project and submit Merge Requests to the default `main` branch.
|
|
project and submit Merge Requests to the default `main` branch.
|
|
|
|
|
|
When a Merge Request is created, a CI pipeline status widget will appear under
|
|
When a Merge Request is created, a CI pipeline status widget will appear under
|
... | @@ -63,7 +63,7 @@ the branch, it will publish the build artifacts and display a **View app** |
... | @@ -63,7 +63,7 @@ the branch, it will publish the build artifacts and display a **View app** |
|
button. Clicking the button will navigate to the build result hosted on
|
|
button. Clicking the button will navigate to the build result hosted on
|
|
`review.torproject.net`.
|
|
`review.torproject.net`.
|
|
|
|
|
|
Project members with the *Developper* role on the TPO blog and main website
|
|
Project members with the *Developer* role on the TPO blog and main website
|
|
have the permission to accept Merge Requests.
|
|
have the permission to accept Merge Requests.
|
|
|
|
|
|
Once the branch is deleted, after the Merge Request is accepted, for example,
|
|
Once the branch is deleted, after the Merge Request is accepted, for example,
|
... | @@ -94,7 +94,7 @@ the Lektor documentation to get started. |
... | @@ -94,7 +94,7 @@ the Lektor documentation to get started. |
|
|
|
|
|
## Design
|
|
## Design
|
|
|
|
|
|
The workflows around Lektor websites is heavily dependant on GitLab CI: it
|
|
The workflows around Lektor websites is heavily dependent on GitLab CI: it
|
|
handles building the sites, running tests and deploying them to various
|
|
handles building the sites, running tests and deploying them to various
|
|
environments including staging and production.
|
|
environments including staging and production.
|
|
|
|
|
... | @@ -113,7 +113,7 @@ There are several elements that can be used to customize the build process: |
... | @@ -113,7 +113,7 @@ There are several elements that can be used to customize the build process: |
|
variable to `npm` will cause `-f npm` to be appended to the build command.
|
|
variable to `npm` will cause `-f npm` to be appended to the build command.
|
|
|
|
|
|
* `LEKTOR_PARTIAL_BUILD`: this variable can be used to alter the build process
|
|
* `LEKTOR_PARTIAL_BUILD`: this variable can be used to alter the build process
|
|
occuring on non-default branches and l10n-staging jobs. When set (to
|
|
occurring on non-default branches and l10n-staging jobs. When set (to
|
|
anything), it will append commands defined in `.setup-lektor-partial-build`
|
|
anything), it will append commands defined in `.setup-lektor-partial-build`
|
|
to the job's `before_script`. Its main purpose is to pre-process website
|
|
to the job's `before_script`. Its main purpose is to pre-process website
|
|
sources to reduce the build times by trimming less-essential content which
|
|
sources to reduce the build times by trimming less-essential content which
|
... | | ... | |