... | ... | @@ -30,27 +30,36 @@ should still be created to allow the review process to occur. |
|
|
build, open the fork project and open `Settings` -> `Pages` and click the URL
|
|
|
under `Access pages`.
|
|
|
|
|
|
#### 2. Click the `Web IDE` button just above the file listing
|
|
|
#### 2. Navigate to `Repository` ➡ `Branches` via the left-hand menu
|
|
|
|
|
|
#### 3. Pick a name for the new branch
|
|
|
|
|
|
* The name isn't very important, it will not persist after the changes are
|
|
|
merged because the branch will be deleted.
|
|
|
|
|
|
* In **Create from**, pick `main`.
|
|
|
|
|
|
#### 4. Click the `Web IDE` button just above the file listing
|
|
|
|
|
|
* The GitLab Web IDE allows you to create a new commit right in your browser,
|
|
|
without the `git` command-line client
|
|
|
|
|
|
### Edit the content file
|
|
|
|
|
|
#### 3. On the left column, click the `New Directory` icon
|
|
|
#### 5. On the left column, click the `New Directory` icon
|
|
|
|
|
|
#### 4. Enter `content/blog/<blog-post-slug>`
|
|
|
#### 6. Enter `content/blog/<blog-post-slug>`
|
|
|
|
|
|
* `<blog-post-slug>` will constitute the URL part after
|
|
|
`https://blog.torproject.org/` (also called the permalink)
|
|
|
|
|
|
#### 5. In the left column still, navigate to the new directory and open the drop-down menu to the right of the new directory item
|
|
|
#### 7. In the left column still, navigate to the new directory and open the drop-down menu to the right of the new directory item
|
|
|
|
|
|
#### 6. Click `New file` to create a new file in that directory
|
|
|
#### 8. Click `New file` to create a new file in that directory
|
|
|
|
|
|
#### 7. Enter `contents.lr` as the new file name
|
|
|
#### 9. Enter `contents.lr` as the new file name
|
|
|
|
|
|
#### 8. In the text editor which appears, draft the new blog post
|
|
|
#### 10. In the text editor which appears, draft the new blog post
|
|
|
|
|
|
* Required fields are `title`, `author`, `pub_date`, `summary` and `body` and
|
|
|
`categories` ([sample contents.lr](#sample-contentslr))
|
... | ... | @@ -68,7 +77,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Upload images and/or attachments
|
|
|
|
|
|
#### 9. Upload the lead image and any other images or attachments in the same directory
|
|
|
#### 11. Upload the lead image and any other images or attachments in the same directory
|
|
|
|
|
|
* The lead image must be uploaded as `lead.png`, `lead.jpg` or `lead.gif`
|
|
|
|
... | ... | @@ -85,7 +94,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Create a new commit and review
|
|
|
|
|
|
#### 10. When finished drafting the new blog post, click `Commit..`
|
|
|
#### 12. When finished drafting the new blog post, click `Commit..`
|
|
|
|
|
|
* Look for a blue button in the lower-left corner
|
|
|
|
... | ... | @@ -94,7 +103,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
* Ensure `Start new merge request` is checked
|
|
|
|
|
|
#### 11. Click once more the `Commit` button
|
|
|
#### 13. Click once more the `Commit` button
|
|
|
|
|
|
* Prefix the Merge request title with `Draft:` to indicate the post is not yet
|
|
|
ready to be merged
|
... | ... | @@ -105,12 +114,12 @@ should still be created to allow the review process to occur. |
|
|
* Once the build is ready, a `View app` button should appear in the merge
|
|
|
request: clicking this link will open a browser tab to the preview URL
|
|
|
|
|
|
#### 12. Add more commits if any changes or adjustments are needed
|
|
|
#### 14. Add more commits if any changes or adjustments are needed
|
|
|
|
|
|
* New commits on the branch will automatically trigger a new preview build and
|
|
|
deployment
|
|
|
|
|
|
#### 13. Once the blog post is finalized, retitle the Merge request to remove the `Draft:` prefix
|
|
|
#### 15. Once the blog post is finalized, retitle the Merge request to remove the `Draft:` prefix
|
|
|
|
|
|
* Once the merge request is reviewed and accepted by a project maintainer,
|
|
|
a full project build will be triggered and deployed to
|
... | ... | @@ -124,7 +133,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Comment topic
|
|
|
|
|
|
#### 14. When the blog post is published, visit the page with a javascript-enabled browser
|
|
|
#### 16. When the blog post is published, visit the page with a javascript-enabled browser
|
|
|
|
|
|
* This will trigger the Discourse forum to create a new topic with the contents
|
|
|
of the blog post in the [News][] category.
|
... | ... | |