[community] Workflow for changing Support website

[emma peel]

Derek Cameron:
> I want to understand the workflow for changing a page on the Support website. How is this:
> 
> 1. On GitHub, fork https://github.com/torproject/support
> 
> 2. In your fork, create a new branch named after the change
> 
> 3. Clone this fork to your local PC
> 
> 4. On your local PC, make the change(s) in the new branch
> 
> 5. Build the website on your PC, from the changed content, as per https://gitlab.torproject.org/tpo/web/tpo/-/wikis/Compiling-a-local-version-of-the-website
> 
> 6. When the content is correct, commit to the new branch on your local PC
> 
> 7. Push from your local PC back to GitHub
> 
> 8. Submit a PR to merge from your fork's new branch back into the master
> 
> 9. Notify #tor-www on IRC
> 
> Is this workflow correct?

Yes, this workflow is correct.
> 
> At what point does the translation into Spanish, etc., get made?

tl;dr: the translation gets made after this process.

Once there are changes on the repository content, we update the translations branch,
and the content on our translation platform gets updated.

The translators receive a message about new strings, and translate them.
They appear on the site then.



emmapeel

Localization Coordinator