Compare commits
2 Commits
58f91fd36f
...
priority-g
Author | SHA1 | Date | |
---|---|---|---|
feda51d0f0
|
|||
ecbe9477b3
|
61
src/_posts/2021-08-16-website-priority-guide.md
Normal file
61
src/_posts/2021-08-16-website-priority-guide.md
Normal file
@ -0,0 +1,61 @@
|
|||||||
|
---
|
||||||
|
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
|
||||||
|
|
@ -1,69 +0,0 @@
|
|||||||
---
|
|
||||||
layout: post
|
|
||||||
title: Come join the good ship Autonomic!
|
|
||||||
description: Hi do you want to work with the coolest anarchist tech workers co-operative?
|
|
||||||
image: robertmccall.jpg
|
|
||||||
category: decision making, democracy, meta
|
|
||||||
date: 2021-11-25
|
|
||||||
---
|
|
||||||
|
|
||||||
|
|
||||||
## Background
|
|
||||||
|
|
||||||
Autonomic is a worker-owned co-operative, dedicated to using technology to empower people making a positive difference in the world. Since 2017, we’ve been successfully delivering projects in a range of sectors including renewable energy, labour organising, independent media, feminist research, migrant solidarity activism, sustainable fashion, and arms trade abolition.
|
|
||||||
|
|
||||||
We are currently 12 worker-owners, located on four continents worldwide. We are a Co-operative Society, registered in the UK with the Financial Conduct Authority. Legally, we are a freelance consortium, which means that we operate as a group of self-employed contractors, and are responsible for our own individual income tax.
|
|
||||||
|
|
||||||
Autonomic aspires to follow the [7 co-operative principles as defined by the International Co-operative Alliance](https://www.ica.coop/en/cooperatives/cooperative-identity).
|
|
||||||
|
|
||||||
We're currently looking to build capacity in the co-op in key areas to help take us to the next level.
|
|
||||||
|
|
||||||
## Pay
|
|
||||||
|
|
||||||
We are currently paid £16 per hour for all work.
|
|
||||||
|
|
||||||
Everyone in the co-op will always be paid the same rate, which we decide on collectively and adjust according to how well we're doing.
|
|
||||||
|
|
||||||
## Why we are cool
|
|
||||||
|
|
||||||
We are fun queer comrade hackers tryna do good things in the world.
|
|
||||||
|
|
||||||
## What we're looking for:
|
|
||||||
|
|
||||||
We are looking for folks who have expertise in the following areas:
|
|
||||||
|
|
||||||
### Required
|
|
||||||
- Care, communicatiton and compassion. Trust. Comradeship. Each according to their need.
|
|
||||||
- Available for around 10-20 hours per week **between 8am UTC and 3pm UTC**
|
|
||||||
|
|
||||||
### Skill areas
|
|
||||||
|
|
||||||
We are in need of people who have experience or interest in at least 2 of these areas:
|
|
||||||
|
|
||||||
- Project management: progress tracking and planning, budgeting and estimates.
|
|
||||||
- Client communications / relations / meeting, conflict resolution.
|
|
||||||
- Infrastrucure skills: Debian, Ansible, Git, Docker, Docker Swarm in the context of Co-op Cloud (https://coopcloud.tech).
|
|
||||||
- Wordpress development (front end and back end): PHP, CSS, Composer, Docker.
|
|
||||||
- Finance administration: invoicing, tax, forecasting,
|
|
||||||
|
|
||||||
### Bonus/Nice to Have
|
|
||||||
|
|
||||||
- Wordpress plug-in development
|
|
||||||
- Drupal development
|
|
||||||
- New business development
|
|
||||||
|
|
||||||
## Process
|
|
||||||
|
|
||||||
People of color, women, genderqueer, non-binary and trans folks, neurodiverse and queer folks strongly encouraged to apply.
|
|
||||||
|
|
||||||
Email helo@autonomic.coop with your CV (doesn't have to be fancy, just a list of work) and a little bit about yourself and what you're looking for work wise.
|
|
||||||
|
|
||||||
If we think you might be suitable for these roles, you'll be invited for a few chats with members of the co-op who will show you more about the kinds of work we do and be able to answer any questions you have.
|
|
||||||
|
|
||||||
If we want to take you on, we'll then have a vote amongst our members and you can start working for us right away as a "potential member". After 100 hours of work you can be invited to join the co-op as a full member.
|
|
||||||
|
|
||||||
<hr>
|
|
||||||
|
|
||||||
_image by Robert McCall_
|
|
||||||
|
|
||||||
|
|
Reference in New Issue
Block a user