Merge branch 'master' into iso-date

Author: dhruvkb

content/blog/authors/JackieBinya/contents.lr

@@ -0,0 +1,8 @@
+username: JackieBinya
+---
+name: Jacqueline Binya
+---
+md5_hashed_email: 05fbbdaf9f9d84074e200f88f662688f
+---
+about:
+[JackieBinya](https://github.com/JackieBinya) is a software developer, technical writer, cloud enthusiast, and a Google Season of Docs 2020 participant.

content/blog/categories/cc-wp-base-theme/contents.lr

@@ -0,0 +1 @@
+name: cc-wp-base-theme

content/blog/entries/cc-wp-base-theme-docs-intro/contents.lr

@@ -0,0 +1,39 @@
+title: WordPress Base Theme Usage Guide (GSOD-2020): Hello World!
+---
+categories:
+cc-wp-base-theme
+gsod
+gsod-2020
+---
+author: JackieBinya
+---
+series: gsod-2020-wordpress-base-theme-usage-guide
+---
+pub_date: 2020-09-30
+---
+body:
+My name is Jacqueline Binya. I am a software developer and technical writer from Zimbabwe. I am going to write a series of blog posts documenting my experience and lessons as I contribute to the [Creative Commons WordPress Base Theme(CC WP Base Theme)](https://github.com/creativecommons/wp-theme-base) during the [Google Season of Docs (GSOD-2020)](https://developers.google.com/season-of-docs) as a technical writer.
+
+## What is Google Season of Docs?
+
+The Google Season of the Docs was born out of a need to improve the quality of open-source documentation as well as to advocate for open source, for documentation, and for technical writing. Annually during the GSOD, technical writers are invited to contribute to open-source projects through a highly intensive process geared at ensuring that the technical writers and the projects they contribute to during GSOD are a good fit, after that has been determined GSOD then resumes.
+
+## Building the docs
+The CC WP Base theme is a WordPress theme used to create front-facing Creative Commons (CC) websites. My task is to collaborate with the engineering team to create community facing docs for the theme.
+
+### Guiding principles
+The docs should be inclusive meaning: they should be written in an easy-to-understand manner taking care to avoid the use of excessive technical jargon, they should be accessible and they should have support for internationalization. We hope to provide our users with a smooth and memorable experience whilst using the docs hence the docs site should be fast and easy to navigate.
+
+### Technical stack of the project
+We decided to build the docs using [Jamstack](https://jamstack.org/), to be specific we are using  [Gridsome](https://gridsome.org/) a static generator for [Vuejs](https://vuejs.org/). We are using Gridsome as it is highly performant, and it also integrates smoothly with the [CC Vocabulary](https://cc-vocabulary.netlify.app/). Gridsome also has out-of-the-box support for important features like Google Analytics and [Angolia](https://www.algolia.com/), these features will obviously be useful in future iterations of the docs. To quickly scaffold the docs we used a Gridsome theme called [JamDocs](https://gridsome.org/starters/jamdocs/).
+
+### Progress
+Currently, the project is on track. As it's been stated we are creating the docs collaboratively. The very first step in our workflow is to create draft content using Google docs. That task is assigned to me, it involves doing lots of research, reading and also testing out the theme. Afterwards, my mentors Hugo Solar and Timid Robot Zehta then give me feedback on the draft. Then I implement the feedback and continuously work on improvements. The final step is migrating the approved draft content to the docs projects in markdown format.
+
+### My lessons so far:
+- Always ask questions: frankly, the only way you can create good content is when you have a solid understanding of the subject matter.
+- It's better to over-communicate than under-communicate especially when working in a remotely, this is especially more important if you encounter blockers whilst executing your work.
+- Push that code and open PR quickly and then go ahead and ask for a review don't procrastinate this will ensure  fast turnover you get feedback quickly and can work on improvements.
+
+
+_Thank you for reading, watch out for the next update which will be posted soon._

content/blog/series/gsod-2020-wordpress-base-theme-usage-guide/contents.lr

@@ -0,0 +1 @@
+name: GSOD-2020: WordPress Base Theme Usage Guide

databags/issues.json

@@ -13,7 +13,7 @@
             "number": 423,
             "repo": "cccatalog",
             "title": "[API Integration] Natural History Museum (UK)",
-            "updatedAt": 1601410964,
+            "updatedAt": 1601507650,
             "url": "https://github.com/creativecommons/cccatalog/issues/423"
         },
         {
@@ -302,7 +302,7 @@
             "number": 274,
             "repo": "cccatalog",
             "title": "[API Integration] Walters Art Museum",
-            "updatedAt": 1601478507,
+            "updatedAt": 1601489296,
             "url": "https://github.com/creativecommons/cccatalog/issues/274"
         },
         {
@@ -316,7 +316,7 @@
             "number": 159,
             "repo": "creativecommons.github.io-source",
             "title": "Move information about old GSoC projects to CC Open Source ",
-            "updatedAt": 1601485174,
+            "updatedAt": 1601490653,
             "url": "https://github.com/creativecommons/creativecommons.github.io-source/issues/159"
         },
         {
@@ -575,7 +575,7 @@
             "number": 33,
             "repo": "licensebuttons",
             "title": "Deduplicate `/www/l`",
-            "updatedAt": 1601076506,
+            "updatedAt": 1601553699,
             "url": "https://github.com/creativecommons/licensebuttons/issues/33"
         },
         {
@@ -773,7 +773,7 @@
             "number": 60,
             "repo": "ccos-scripts",
             "title": "Code organisation can be improved",
-            "updatedAt": 1601450075,
+            "updatedAt": 1601542673,
             "url": "https://github.com/creativecommons/ccos-scripts/issues/60"
         },
         {