Skip to content

Commit 78d75bd

Browse files
authored
Updated instructions for clarity
1 parent ac31882 commit 78d75bd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/community/write-a-blog-post/contents.lr

+1-1
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ New blog posts must be submitted **by submitting a [pull request](/contributing-
4141
* If there is no subdirectory for that category, create one using **the exact category name** as the blog post with its own `contents.lr` file within.
4242
* The new `contents.lr` file within should follow the same format as the other categories. Here's an [example category content file](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/master/content/blog/categories/gsoc-2019/contents.lr).
4343
1. Similarly, each author must have their own subdirectory in the [content/blog/authors](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/authors) directory.
44-
* If there is no subdirectory for your username, create one using **the exact username** as the blog post with its own `contents.lr` file within.
44+
* If there is no subdirectory for your username, create one using **the exact username** as the author field of the blog post with its own `contents.lr` file within.
4545
* The new `contents.lr` file within should follow the same format as the other authors. Here's an [example author content file](https://raw.githubusercontent.com/creativecommons/creativecommons.github.io-source/master/content/blog/authors/TimidRobot/contents.lr).
4646
1. Build the `creativecommons.github.io-source` project locally (instructions are in the `README` in the repository) and ensure your blog post shows up correctly locally. If you have not created the appropriate category or author files, you will see a build error in this step.
4747
1. Push your code and make a pull request.

0 commit comments

Comments
 (0)