You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/community/write-a-blog-post/contents.lr
+6-5
Original file line number
Diff line number
Diff line change
@@ -62,12 +62,13 @@ Once you have written your post, you can either send it to us (Markdown is easie
62
62
</pre>
63
63
64
64
*Read more about [Markdown formatting here](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).*
65
-
1.Each category you have applied to the post must have its own subdirectory in the [content/blog/categories](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/categories) directory.
66
-
*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.
65
+
1.Create category pages for any new categories that you've assigned to your post. Each category has its own subdirectory in the [content/blog/categories](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/categories) directory.
66
+
*Create a folder that uses the**the exact category name** as the blog post with its own `contents.lr` file within.
67
67
* 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).
68
-
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.
69
-
* 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.
70
-
* 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).
68
+
1. Similarly, if this is your first post, you'll need to create a file with author information. Each author has a subdirectory in the [content/blog/authors](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/authors) directory.
69
+
* Your author folder must have **the exact username** as the author field of the blog post and have a `contents.lr` file within.
70
+
* The `username` field in the `contents.lr` file should also use the same exact username.
71
+
* The author's `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).
71
72
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.
72
73
1. Push your code and make a pull request.
73
74
1. Wait for a member of CC's fulltime staff to merge the post into the `master` branch.
0 commit comments