Added blog post submission instructions #221
Conversation
(issue 197) Signed-off-by: Jurj-Bogdan <[email protected]>
(issue 197) Signed-off-by: Jurj-Bogdan <[email protected]>
|
An important part is missing from the content: Who is allowed to write blog posts? |
|
@froschdesign Here we have the answer to the question how |
If only the how is explained here, we need to add two links in the list view. That cannot be the goal. |
| - If submitting for the first time an [author](#blog-author) YAML file must be added to the `data/blog/authors` directory. | ||
| - Add an MD file containing the [blog post's metadata and body](#blog-post-content). | ||
| - each file must be added in the current year's directory, found in `data/blog/`. | ||
|
|
There was a problem hiding this comment.
I suggest that you state the filename convention yyyy-mm-dd-title with an example
|
@Jurj-Bogdan has provided instructions to create the post and author files and in which folder which is great. In my opinion, anyone should be welcomed to submit a blog entry in the same way anyone can submit a PR to any repo. PRs are revview and approved (or rejected). What we may need are some guidelines as to what a blog post should contain or not. |
Signed-off-by: Jurj-Bogdan <[email protected]>
|
@froschdesign @arhimede @visto9259 I ran into a potential issue after checking the linting command from the CI pipeline - only the README.md file is being linted. Should it be extended to include the blog entries and author yaml files as well? |
I am not sure that I can make the call here. I would suggest to open a separate issue (RFC) to start a discussion on adding linting blog entries and author files to the CI pipeline so that we can close this PR for now. @froschdesign @arhimede any thoughts? |
Description
Added blog post submission instructions, as mentioned in #197. Let me know of any issues or extra sections that should be added