For the past couple of weeks we have been actively creating content for the Creative Commons Base Usage Guide. Currently the draft content is under final review before it is migrated to the main docs site. Our Strategy Our main goal in creating the docs is to create rich, intuitive, engaging, and beautifully presented community facing documentation for the Creative Commons Base. In alignment with the defined goal, our core focus is to create the docs collaboratively.

Historically REST is the accepted standard for designing web APIs. The main advantages of using REST were: REST is stateless meaning every server call is independent of any other network calls made to the server. The server will not persist any state about the queries it receives. It provides a structured way to query resources. The problem REST was intended to be a strict specification used to design APIs but in reality, it was wildly interpreted: most APIs described as being Restful aren’t really Restful, they don’t adhere to the strict specification REST APIs have shown to be too inflexible to keep up with the rapidly changing requirements on the client apps that access them.

I am participating in the Google Season of Docs 2020 as a technical writer. I am contributing to Creative Commons. 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 Base(CC Base) during the Google Season of Docs (GSOD-2020) as a technical writer.