Merge branch 'main' into google-drive-blog-post

Dockerfile

@@ -1,4 +1,4 @@
-FROM ruby:2.7.4-alpine3.12
+FROM ruby:2.7.3-alpine
 
 EXPOSE 4000
 

Gemfile

@@ -1,6 +1,6 @@
 source "https://rubygems.org"
 
-ruby "2.7.4"
+ruby "2.7.3"
 
 gemspec
 

requirements.txt

@@ -1 +1 @@
-docker-compose==1.29.2
+docker-compose==1.29.1

src/_posts/2021-02-11-google-drive.md

@@ -0,0 +1,25 @@
+---
+layout: post
+title: Escaping the Google silo
+description: Opening up your Google Drive and Docs files using open source software
+image: 
+category: technology
+date: 2021-02-11
+---
+
+At Autonomic we always promote using [libre software](https://en.wikipedia.org/wiki/Free_software) whereever possible but we understand that many clients have committed to using [propietary software](https://en.wikipedia.org/wiki/Proprietary_software) either due to legacy decision or because the non-libre solutions are simply more effective and mature.
+
+The Google Workspace set of tools including Google Drive and Google Docs is one such solution. Once your organisation has deployed and is using these Google services, it's extremly difficult to migrate away. Google Docs files are not easy to extract from their propietary format and users are strongly encouragaged to only interact with the documents via the Google Workspace web apps.
+
+This is problematic for organisations that want to approach their data storage with a stratergy that suits them, rather than the Google™️ mandated workflow. 
+There are also [so many criticims](https://en.wikipedia.org/wiki/Criticism_of_Google) that could be made of Google in so many areas (as a [worker's co-operative of privacy advocates](/our-founding-principles), we're of course very biased).
+
+There is also the question of [Google outages](https://en.wikipedia.org/wiki/2020_Google_services_outages) which happened multiple times in 2020. Of course, service outages can and do happen at any scale but it is interesting to note that they are even fairly regular occurance at many of the largest technology companies. When it comes to critical services, offering reduncancy and decentralisation is very difficult to do at the monolithic scale of the tech ginats.
+
+We have been working on a solution for a client to try and make it easier for organisatons to in the short term keep non-Google hosted copies of their data and in the long term, be in a better position to migrate away from Google Workspace all together. Luckily, there is an extensive [Drive](https://developers.google.com/drive/) and [Docs API](https://developers.google.com/docs/api/) which is well documentated and relativley stable.
+
+Our system is designed to pull all of your data out of the Google [walled garden](https://en.wikipedia.org/wiki/Closed_platform) and directly into your control. We host a server for you which runs our code to extract all of your files from Google Drive and covert all of your Google Docs into open document formats (.odt .docx etc.). The files are then made available to your organisation as standard filesystem on your own [Nextcloud](https://nextcloud.com/) instance and then you can do what you want with them. You'll also be able to draw up a support contract with us that suits your needs for both maintaining the server and supporting your users.
+
+We intend to release the source code for our system under a libre license as soon whens we feel it's ready but it still needs some cleaning up and documentation which takes time. When it's released, you'll be able to find on our [Gitea instance](https://git.autonomic.zone/autonomic-cooperative).
+
+If you're interested in hosting this solution for your organsation, feel free to [get in touch](mailto:helo@autonomic.zone).

src/_posts/2021-07-05-new-coop-cloud-blog-and-socials.md

@@ -1,10 +0,0 @@
----
-layout: post
-title: New Co-op Cloud blog, socials and updates
-description: Co-op Cloud project blog, socials and monthly updates
-image: ccblog.png
-category: coop, co-op, cloud, docker, swarm, libre-software, hosting,
-date: 2021-07-07
----
-
-The Co-op Cloud is starting to come into its own and we've decided to move our posts over to a dedicated [new and shiny blog](https://coopcloud.tech/blog/). We are working on opening up shared ownership of the project and want to create digital spaces where Autonomic is not implicitly having some sort of gate keeping role. We'll be writing regularly about our progress over there. We've also made new [Twitter](https://twitter.com/Coop_Cloud) and [Mastodon](https://social.coop/@coopcloud) which can you can follow along. That's all for now!

src/_posts/2021-08-16-website-priority-guide.md

@@ -1,61 +0,0 @@
----
-layout: post
-title: Content Priority Guides for Websites
-description: What is a Content Priority Guide and how to use it for web development
-image:
-category: autonomic, content, priority, guide, web, development, design, copywriting
-date: 2021-08-16
----
-
-A Content Priority Guide (CPG) are a simpler and faster version of [wireframes](https://en.wikipedia.org/wiki/Website_wireframe) that isn't focussed on design or the actual and encourage a client to not get bogged down in details. We found this exercise, gives the client and ourselves a clear and concise map of what the site is going to look like at an earliest stages of the project as possible. This is especially useful for smaller projects where there isn't budget or the client isn't very experienced with commissioning web development work.
-
-The content itself can then be worked on referencing the structure and hierarchy laid out in the CPG and if appropriate, the design team and front-end development team will also use the CPG in their work. The common consensus on the site layout created by the CPG allows for a "multi-threaded" approach to the project where different teams are able to work on their respective specialities simultaneously. The CPG can be updated as the project proceeds as long as all teams are aware of the changes.
-
-If a client's budget allows, Autonomic will also do more in depth collaborative processes with our clients but making a CPG together is a great starting point and requires no specialist tools or knowledge.
-
-Below is a sample Content Priority Guide. It was inspired by this [blog post](https://seesparkbox.com/foundry/content_priority_guide) and this [article](https://www.smashingmagazine.com/2012/05/design-process-responsive-age/).
-
-## Sample priority guide
-### The audience
-- Who are your audiences?
-- Can you list your audiences in order of priority?
-- What are the accessibility needs of your audiences?
-- What devices are your audiences primarily accessing the site on?
-
-### Page 1 - Homepage
-1. Heading
-2. Hero image 
-3. About Us copy (3-4 sentences)
-4. Our demands section
-	- Section Title
-	- Bullet point list of demands
-5. What we do section
-	- Section title
-	- Image
-	- What we do (A few sentences describing our activities)
-	- How we do it (A few sentences that include our principles)
-	- Our outcomes (A few paragraphs that talk about what we have achieved)
-
-### Page 2 - Projects
-1. Heading
-2. Sub-heading
-3. 6-8 items displayed in chronological order
-	- Project Title
-	- Image or Headline (if an image is provided, that will display. If there is no image, the headline will display)
-	- Project Description (2-4 sentences about the project)
-	- Link to read project details entry
-
-### Page 3 -  Blog
-1. Heading
-2. List of 6-8 blog posts
-	- Blog title
-	- Blog post publish date
-	- Blog post tags
-	- Pagination navigation links
-3. Archive blog posts drop down selectable by month
-
-### Page 4 - Contact
-1. Headline
-2. Email contact form
-3. Follow us on social media subheading and icons with links to social media pages
-