... | ... | @@ -66,7 +66,7 @@ should still be created to allow the review process to occur. |
|
|
* 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
|
|
|
#### 9. In the text editor which appears, draft the new blog post
|
|
|
|
|
|
* Required fields are `title`, `author`, `pub_date`, `summary` and `body` and
|
|
|
`categories` (see **Sample contents.lr** section below)
|
... | ... | @@ -84,7 +84,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Upload images and/or attachments
|
|
|
|
|
|
#### 11. 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
|
|
|
|
|
|
* The lead image must be uploaded as `lead.png`, `lead.jpg` or `lead.gif`
|
|
|
|
... | ... | @@ -101,7 +101,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Create and push a new commit and create a Merge Request
|
|
|
|
|
|
#### 12. When finished, open the `Source Control` panel
|
|
|
#### 11. When finished, open the `Source Control` panel
|
|
|
|
|
|
* Look for a branching icon on the left-hand side with the purple notification
|
|
|
dot
|
... | ... | @@ -113,7 +113,7 @@ should still be created to allow the review process to occur. |
|
|
* 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
|
|
|
#### 12. Click `Create MR` in the dialog that appears in the bottom right
|
|
|
|
|
|
* The IDE will open a new tab in your navigator to the `New merge request`
|
|
|
page
|
... | ... | @@ -127,12 +127,12 @@ should still be created to allow the review process to occur. |
|
|
* Click the `View app` to open a browser tab to the preview URL, once the
|
|
|
preview build is finished, it will appear at this URL
|
|
|
|
|
|
#### 14. Add more commits if any changes or adjustments are needed
|
|
|
#### 13. Add more commits if any changes or adjustments are needed
|
|
|
|
|
|
* New commits on the branch will automatically trigger a new preview build and
|
|
|
deployment
|
|
|
|
|
|
#### 15. Once the blog post is finalized, retitle the Merge request to remove the `Draft:` prefix
|
|
|
#### 14. 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
|
... | ... | @@ -146,7 +146,7 @@ should still be created to allow the review process to occur. |
|
|
|
|
|
### Comment topic
|
|
|
|
|
|
#### 16. When the blog post is published, visit the page with a javascript-enabled browser
|
|
|
#### 15. 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.
|
... | ... | |