... | @@ -44,20 +44,27 @@ should still be created to allow the review process to occur. |
... | @@ -44,20 +44,27 @@ should still be created to allow the review process to occur. |
|
* The GitLab Web IDE allows you to create a new commit right in your browser,
|
|
* The GitLab Web IDE allows you to create a new commit right in your browser,
|
|
without the `git` command-line client
|
|
without the `git` command-line client
|
|
|
|
|
|
### Edit the content file
|
|
### Create the content folder / [post slug](https://en.wikipedia.org/wiki/Clean_URL#Slug)
|
|
|
|
|
|
|
|
#### 5. In the left-side navigation column, uncollapse `content` / `blog`
|
|
|
|
|
|
#### 5. On the left column, click the `New Directory` icon
|
|
* Each folder corresponds to a blog post and its contents
|
|
|
|
|
|
#### 6. Enter `content/blog/<blog-post-slug>`
|
|
* Folder names become post slugs during the build process
|
|
|
|
|
|
|
|
#### 6. Click the `New Folder...` icon and type in `<blog-post-slug>`
|
|
|
|
|
|
* `<blog-post-slug>` will constitute the URL part after
|
|
* `<blog-post-slug>` will constitute the URL part after
|
|
`https://blog.torproject.org/` (also called the permalink)
|
|
`https://blog.torproject.org/` (also called the permalink)
|
|
|
|
|
|
#### 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
|
|
### Edit the content file
|
|
|
|
|
|
#### 8. Click `New file` to create a new file in that directory
|
|
#### 7. Still in the navigation column, click the `New File...` icon
|
|
|
|
|
|
#### 9. Enter `contents.lr` as the new file name
|
|
#### 8. Enter `contents.lr` as the new file name
|
|
|
|
|
|
|
|
* This file must contain a number of fields which will allow the build system
|
|
|
|
to render the blog post
|
|
|
|
|
|
#### 10. In the text editor which appears, draft the new blog post
|
|
#### 10. In the text editor which appears, draft the new blog post
|
|
|
|
|
... | @@ -92,17 +99,24 @@ should still be created to allow the review process to occur. |
... | @@ -92,17 +99,24 @@ should still be created to allow the review process to occur. |
|
be deduplicated in GitLab (just make sure not to modify them unless
|
|
be deduplicated in GitLab (just make sure not to modify them unless
|
|
necessary)
|
|
necessary)
|
|
|
|
|
|
### Create a new commit and review
|
|
### Create and push a new commit and create a Merge Request
|
|
|
|
|
|
#### 12. When finished drafting the new blog post, click `Commit..`
|
|
#### 12. When finished, open the `Source Control` panel
|
|
|
|
|
|
* Look for a blue button in the lower-left corner
|
|
* Look for a branching icon on the left-hand side with the purple notification
|
|
|
|
dot
|
|
|
|
|
|
* Enter a short commit message, eg. `Adding 2022 GSoC blog post`
|
|
* Enter a short commit message, eg. `Adding 2022 GSoC blog post`
|
|
|
|
|
|
* Ensure `Start new merge request` is checked
|
|
* Click `Commit & Push`
|
|
|
|
|
|
|
|
* A dialog will pop up near the top of the page asking if a new branch should
|
|
|
|
be created, click **No**
|
|
|
|
|
|
|
|
#### 13. Click `Create MR` in the dialog that appears in the bottom right
|
|
|
|
|
|
#### 13. Click once more the `Commit` button
|
|
* The IDE will open a new tab in your navigator to the `New merge request`
|
|
|
|
page
|
|
|
|
|
|
* Prefix the Merge request title with `Draft:` to indicate the post is not yet
|
|
* Prefix the Merge request title with `Draft:` to indicate the post is not yet
|
|
ready to be merged
|
|
ready to be merged
|
... | @@ -110,8 +124,8 @@ should still be created to allow the review process to occur. |
... | @@ -110,8 +124,8 @@ should still be created to allow the review process to occur. |
|
* Within a few minutes, GitLab CI should build and upload the draft version
|
|
* Within a few minutes, GitLab CI should build and upload the draft version
|
|
online
|
|
online
|
|
|
|
|
|
* Once the build is ready, a `View app` button should appear in the merge
|
|
* Click the `View app` to open a browser tab to the preview URL, once the
|
|
request: clicking this link will open a browser tab to the preview URL
|
|
preview build is finished, it will appear at this URL
|
|
|
|
|
|
#### 14. Add more commits if any changes or adjustments are needed
|
|
#### 14. Add more commits if any changes or adjustments are needed
|
|
|
|
|
... | | ... | |