Merge pull request #150 from diana-lakatos/master

Adds part 4 of platformOS article series, fixes previous articles

Author: annegentle

_posts/articles/2018-10-12-platformos-1of4.md

@@ -1,19 +1,19 @@
 ---
 layout: post
-title: "Building Our Documentation Site on PlatformOS — Part 1: Information Architecture"
-excerpt: This article series describes our process for building the PlatformOS documentation site, with in-depth insights into our approach, decisions, and plans. In this part, we share how we started, how we got to know our audience, how we figured out what content we need, and how we outlined a sitemap for our documentation site.
+title: "Building Our Documentation Site on platformOS — Part 1: Information Architecture"
+excerpt: This article series describes our process for building the platformOS documentation site, with in-depth insights into our approach, decisions, and plans. In this part, we share how we started, how we got to know our audience, how we figured out what content we need, and how we outlined a sitemap for our documentation site.
 last_modified_at: Fri Oct 12 21:01:44 CDT 2018
 categories: articles
 author: diana_lakatos
 tags: [developer documentation, Design Thinking, Information Architecture, docs, documentation, UX]
 image:
   path: /images/platformos/platformos_part1/part1_cover.jpg
-  caption: "[Courtesy PlatformOS blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platform-os-part-1-information-architecture)"
+  caption: "[Courtesy platformOS blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platform-os-part-1-information-architecture)"
 comments: false
 share: true
 ---
 
-This article series describes our process of building our [documentation site](https://documentation.platform-os.com/) for [PlatformOS](https://www.platform-os.com/), with in-depth insights into our approach, decisions, and plans. We have planned four parts for this series, each describing a unique aspect of our journey:  
+This article series describes our process of building our [documentation site](https://documentation.platform-os.com/) for [platformOS](https://www.platform-os.com/), with in-depth insights into our approach, decisions, and plans. We have planned four parts for this series, each describing a unique aspect of our journey:  
 
 * Part 1: **Information Architecture**  
   In this part, we share how we started, how we got to know our audience, how we figured out what content we need, and how we outlined a sitemap for our documentation site.
@@ -24,7 +24,7 @@ This article series describes our process of building our [documentation site](h
 * Part 4: **Implementation**  
   In this part, we take a look under the hood, and discuss the technologies we used, how we built our auto-generated API Reference, and how we pull content and related information from Github. We also share our future plans with you.  
 
-All these articles together will show you a complete framework for building a documentation site on PlatformOS.
+All these articles together will show you a complete framework for building a documentation site on platformOS.
 
 We are continuously working on our documentation, but decided to make it public early on to get valuable feedback and show you the whole process, so please expect the documentation site to change and evolve while you learn more about it through these articles. At the time of the publication of this article, our documentation site is in alpha.  
 
@@ -109,6 +109,6 @@ This concluded our Information Architecture phase. We have discovered and organi
 
 _We involved [UX Strategist Katalin Nagygyörgy](https://www.linkedin.com/in/nagygyorgykatalin/) in our process from the start. Through our collaboration, we could extract and collect all the necessary information using tried and true research methodologies and UX best practices._
 
-_This article was originally written for the [PlatformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-1-information-architecture)._
+_This article was originally written for the [platformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-1-information-architecture)._
 
 {% include sign-up.html %}

_posts/articles/2018-11-01-platformos-2of4.md

@@ -1,19 +1,19 @@
 ---
 layout: post
-title: "Building Our Documentation Site on PlatformOS — Part 2: Content Production and Layouts"
+title: "Building Our Documentation Site on platformOS — Part 2: Content Production and Layouts"
 excerpt: Welcome to part 2 of our article series where we discuss how content production started, and how we created the layouts and navigation for the site.
 last_modified_at: Thu Nov 01 22:01:44 CDT 2018
 categories: articles
 author: diana_lakatos
 tags: [developer documentation, Content-First Design, community, style guide, templates, editorial workflow, wireframes, docs, documentation, UX]
 image:
   path: /images/platformos/platformos_part2/part2_cover.jpg
-  caption: "[Courtesy PlatformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platform-os-part-2-content-production-and-layouts)"
+  caption: "[Courtesy platformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platform-os-part-2-content-production-and-layouts)"
 comments: false
 share: true
 ---
 
-Welcome to part 2 of our article series where we describe the process of building the [PlatformOS documentation site](https://documentation.platform-os.com/) from discovery to development, with in-depth insights into our approach, decisions, plans, and technical implementation.
+Welcome to part 2 of our article series where we describe the process of building the [platformOS documentation site](https://documentation.platform-os.com/) from discovery to development, with in-depth insights into our approach, decisions, plans, and technical implementation.
 
 Now that you’ve seen how we explored the needs of our audience, outlined the types of content we’d work on, and created a sitemap in part 1, let’s move on to discuss how content production started, and how we created the layouts and navigation for the site.  
 
@@ -136,12 +136,12 @@ _Wireframe for the tutorial topic type_
 
 As you can see from the process so far, we put our focus on audience, content, and UX — leaving visual design for later.
 
-Both the Design Thinking approach, and the Content-First approach we described in this article push visual design to a later stage. At the same time, the branding of PlatformOS is still in the making — with the help of the wonderful [Yiying Lu](https://www.linkedin.com/in/yiyinglu/). This means, that by the time our branding is done, we will have a working documentation site tested with real users, continuously improved based on relevant feedback. We believe that this way we could focus on the most important aspects for each phase, and our documentation site will have a solid foundation that the design can enhance. This is why, for now, we went with a very simple, clean design.  
+Both the Design Thinking approach, and the Content-First approach we described in this article push visual design to a later stage. At the same time, the branding of platformOS is still in the making — with the help of the wonderful [Yiying Lu](https://www.linkedin.com/in/yiyinglu/). This means, that by the time our branding is done, we will have a working documentation site tested with real users, continuously improved based on relevant feedback. We believe that this way we could focus on the most important aspects for each phase, and our documentation site will have a solid foundation that the design can enhance. This is why, for now, we went with a very simple, clean design.  
 
 We hope you enjoyed learning about how we started content production, how we built our editorial workflow, and how we created wireframes for our documentation site. **Stay tuned to learn more about the community aspects of our docs in part 3 of our series!**
 
 _We involved [UX Strategist Katalin Nagygyörgy](https://www.linkedin.com/in/nagygyorgykatalin/) in our process from the start. Through our collaboration, we could extract and collect all the necessary information using tried and true research methodologies and UX best practices._
 
-_This article was originally written for the [PlatformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-2-content-production-and-layouts)._
+_This article was originally written for the [platformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-2-content-production-and-layouts)._
 
 {% include sign-up.html %}

_posts/articles/2018-11-25-platformos-3of4.md

@@ -1,19 +1,19 @@
 ---
 layout: post
-title: "Building Our Documentation Site on PlatformOS — Part 3: Community"
+title: "Building Our Documentation Site on platformOS — Part 3: Community"
 excerpt: Welcome to part 3 of our article series where we explore how we collaborate with our community.
 last_modified_at: Thu Nov 25 22:01:44 CDT 2018
 categories: articles
 author: diana_lakatos
 tags: [developer documentation, contributor experience, community, style guide, templates, editorial workflow, docs, documentation]
 image:
   path: /images/platformos/platformos_part3/part3_cover.jpg
-  caption: "[Courtesy PlatformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-3-community)"
+  caption: "[Courtesy platformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-3-community)"
 comments: false
 share: true
 ---
 
-In this [article series](/articles/platformos-1of4) we describe the process of building the [PlatformOS documentation site](https://documentation.platform-os.com/) from discovery to development, with in-depth insights into our approach, decisions, plans, and technical implementation. Welcome to part 3, where we explore how we collaborate with our community. 
+In this [article series](/articles/platformos-1of4) we describe the process of building the [platformOS documentation site](https://documentation.platform-os.com/) from discovery to development, with in-depth insights into our approach, decisions, plans, and technical implementation. Welcome to part 3, where we explore how we collaborate with our community. 
 
 # Community-driven documentation
 
@@ -52,9 +52,9 @@ In order to encourage collaboration and keep our community up-to-date with what
 
 Our main communication channel for now is a dedicated Slack channel, where community members **ask questions, share ideas, and get to know our team members and each other**.
 
-Here, they can ask questions about anything related to PlatformOS, and someone from our team, or another community member who has the answer will jump in to reply. We get a wide variety of questions from business related enquiries like pricing to specific questions about development.
+Here, they can ask questions about anything related to platformOS, and someone from our team, or another community member who has the answer will jump in to reply. We get a wide variety of questions from business related enquiries like pricing to specific questions about development.
 
-This is also the place where both we and our community members **share news**. We let them know of new **features planned, bugs fixed, articles posted, and new docs added, and they show what they’re building on PlatformOS**. This constant exchange of information is extremely valuable for all involved: community members can share what they’ve learned, plan their module development in sync with our roadmap and each other’s projects, and allocate their resources according to what’s going on in the business and the wider community.   
+This is also the place where both we and our community members **share news**. We let them know of new **features planned, bugs fixed, articles posted, and new docs added, and they show what they’re building on platformOS**. This constant exchange of information is extremely valuable for all involved: community members can share what they’ve learned, plan their module development in sync with our roadmap and each other’s projects, and allocate their resources according to what’s going on in the business and the wider community.   
 
 The Slack channel also provides a great opportunity for community members to start conversations, share relevant news and articles, and engage with like-minded professionals.
 
@@ -76,13 +76,13 @@ _A documentation status report in our Slack channel_
 
 ## Weekly video conferencing 
 
-Initiated by our community, Town Hall is a weekly video conference over [Zoom](https://zoom.us/), where community members and the PlatformOS team share news, demo features and modules, and have the opportunity to engage in real-time, face-to-face conversation. 
+Initiated by our community, Town Hall is a weekly video conference over [Zoom](https://zoom.us/), where community members and the platformOS team share news, demo features and modules, and have the opportunity to engage in real-time, face-to-face conversation. 
 
 Our team and community members are distributed over different continents, so we try to accommodate participants in different time zones by rotating the time of this event so that everyone has the chance to participate. We also share the recording of each meeting. 
 
 ![](/images/platformos/platformos_part3/town_hall.jpg) 
 
-_Town Hall meeting: A community member demoing an application he developed on PlatformOS_
+_Town Hall meeting: A community member demoing an application he developed on platformOS_
 
 ## Surveys
 
@@ -103,15 +103,15 @@ As our community grows, we are preparing to scale with it. Here are some of our
 
 * **Topic wish list**: A feature that allows community members to add topics they’d like to see documented.
 * **Voting on topics**: Vote on topics, and we will start working on the topics with the most votes.
-* **Community site**: Our community members are active on many channels now, including on some of their own initiatives, like an Airtable for keeping track of community members, questions and answers, and community activities. Although it works for now, we are planning to give the PlatformOS community a home — a site similar to Intel Devmesh, a developer community site we built for Intel on PlatformOS.
-* **Community Manager**: In the near future, we are hiring a Community Manager to give the PlatformOS community dedicated attention from an experienced professional.
+* **Community site**: Our community members are active on many channels now, including on some of their own initiatives, like an Airtable for keeping track of community members, questions and answers, and community activities. Although it works for now, we are planning to give the platformOS community a home — a site similar to Intel Devmesh, a developer community site we built for Intel on platformOS.
+* **Community Manager**: In the near future, we are hiring a Community Manager to give the platformOS community dedicated attention from an experienced professional.
 * **Gamification**: After building a solid user flow, we are planning to  strengthen it with gamification elements to help and reward the user’s journey from onboarding to mastering the site. 
-* **Devcon**: We are planning a PlatformOS Devcon for 2019, a proper get-together for our community members with workshops and presentations by our team members and experienced members of our community.
+* **Devcon**: We are planning a platformOS Devcon for 2019, a proper get-together for our community members with workshops and presentations by our team members and experienced members of our community.
 
-Now that you’ve seen how we discovered the needs of our target audience, planned content and layout for our documentation site, and connected with our community, all that’s left from our series is to show you how we implemented our documentation site on PlatformOS. See you again in part 4! 
+Now that you’ve seen how we discovered the needs of our target audience, planned content and layout for our documentation site, and connected with our community, all that’s left from our series is to show you how we implemented our documentation site on platformOS. See you again in part 4! 
 
 _We involved [UX Strategist Katalin Nagygyörgy](https://www.linkedin.com/in/nagygyorgykatalin/) in our process from the start. Through our collaboration, we could extract and collect all the necessary information using tried and true research methodologies and UX best practices._
 
-_This article was originally written for the [PlatformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-3-community)._
+_This article was originally written for the [platformOS Blog](https://www.platform-os.com/blog/post/blog/building-our-documentation-site-on-platformos-part-3-community)._
 
 {% include sign-up.html %}