... | @@ -86,6 +86,9 @@ should still be created to allow the review process to occur. |
... | @@ -86,6 +86,9 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
#### 10. Upload the lead image and any other images or attachments in the same directory
|
|
#### 10. Upload the lead image and any other images or attachments in the same directory
|
|
|
|
|
|
|
|
* To upload a file, right-click on the directory in the navigation panel and
|
|
|
|
click `Upload...` or drag and drop from your file manager
|
|
|
|
|
|
* The lead image must be uploaded as `lead.png`, `lead.jpg` or `lead.gif`
|
|
* The lead image must be uploaded as `lead.png`, `lead.jpg` or `lead.gif`
|
|
|
|
|
|
* A default Tor logo image will be displayed if the lead image is omitted
|
|
* A default Tor logo image will be displayed if the lead image is omitted
|
... | @@ -99,6 +102,15 @@ should still be created to allow the review process to occur. |
... | @@ -99,6 +102,15 @@ 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)
|
|
|
|
|
|
|
|
* To use such uploaded images inline in the post body, use markup such as
|
|
|
|
`![Image Alt-Text](image-filename.png)`
|
|
|
|
|
|
|
|
* Extra attributes may be added to an image's HTML markup, eg.
|
|
|
|
`![Image Alt-Text](image-filename.png "class=left")`
|
|
|
|
|
|
|
|
* To add a hyperlink to an uploaded file such as a PDF, the markup would be
|
|
|
|
`[Link Text](document-filename.pdf)`
|
|
|
|
|
|
### Create and push a new commit and create a Merge Request
|
|
### Create and push a new commit and create a Merge Request
|
|
|
|
|
|
#### 11. When finished, open the `Source Control` panel
|
|
#### 11. When finished, open the `Source Control` panel
|
... | @@ -132,7 +144,10 @@ should still be created to allow the review process to occur. |
... | @@ -132,7 +144,10 @@ should still be created to allow the review process to occur. |
|
* New commits on the branch will automatically trigger a new preview build and
|
|
* New commits on the branch will automatically trigger a new preview build and
|
|
deployment
|
|
deployment
|
|
|
|
|
|
#### 14. Once the blog post is finalized, retitle the Merge request to remove the `Draft:` prefix
|
|
#### 14. Once the blog post is finalized and ready for publishing, click `Mark as ready`
|
|
|
|
|
|
|
|
* If the blog post is ready, but should be published at a later date, it
|
|
|
|
should remain in the `Draft` state in order to prevent merging
|
|
|
|
|
|
* Once the merge request is reviewed and accepted by a project maintainer,
|
|
* Once the merge request is reviewed and accepted by a project maintainer,
|
|
a full project build will be triggered and deployed to
|
|
a full project build will be triggered and deployed to
|
... | | ... | |