- We have the Open Spending community site at http://community.openspending.org/
- It currently runs on Wordpress
- We plan to migrate it from Wordpress to Jekyll and Github pages
- and refactor the site a bit at the same time
- The new site repo is at https://github.com/openspending/dotorg
- Note: this repo was used 2y ago for a bunch of community content which is a bit confusing. We are gradually going to rework the repo as we go
- “Master” tracker issue for this in github: https://github.com/openspending/dotorg/issues/28
Why are we doing this
- Situation: our community site at community.openspending.org is powered by wordpress. We do not have a wiki. Other material includes tech docs are at http://docs.openspending.org/en/latest/, various google docs in gdrive etc
- Complication: no wiki-like experience and so not easy for newcomers (or others to contribute). Giving access to wordpress is quite slow, no immediate ability to edit, and even with access somewhat painful to do editing.
- Question: What setup could we create that would allow for a well structured community site that provides key information and allows people to contribute easily
- Solution: 2 parts
- Migrate to a new platform (github pages)
- Restructure content and flag areas for development and contribution
Why Github Pages
It delivers the best balance of:
- Ease of deployment and maintenance
- Ease of editing (can do one click editing and see changes appear)
- Auditable / moderatable (spam not a problem)
- Configurability and themability
- Wiki (mediawiki)
- Pros: standard wiki and quite easy to use
- Cons: spam is now almost uncontrollable. Sysadmin needed to maintain and relatively complex to configure and hack
- Pros: standard, stable and with a lot of CMS features. Also OK already host this by defalt
- Cons: not really a wiki and difficult to make it so.
- Github pages
- Pros: nice moderation workflow that prevents spam. Reasonable and improving GUI for editing. Halfway between wiki and website so can look quite nice. Reasonably easy to configure and theme.
- Cons: somewhat geeky/technical for contributors (jekyll, markdown etc)
- Do we keep wordpress for the blog (maybe at blog.openspending.org). Ans: maybe.
The New Site Structure
/Landing page - gateway to the project from community side
/about/About - incl Governance
/events/- Events and collaboration
/get-involved/Contribute / Get Involved pages - team pages (if we still have teams)
- Blog section
/help/Help - Using and contributing to OpenSpending (Guides and Howtos)
- I want a visualization fast … (should just point to site as UX should be good enough to not need a guide!)
- Data Wrangler
- Where does my money go maker
/resources/Resources on Financial Data - guides, research, reports, archives (?)
- Reports - is this a separate section (?)
Details per section below
Note: we can ignore things that are hard to migrate from wordpress e.g. special embeds etc (and come back to these later).
Can follow current front page pretty closely
- What is the project
- Links to key other sections
- Instructions for newcomers and old-hands
Already largely exist. Just need to migrate
Ditto - migrate what we have
Maybe leave stuff on wordpress for time being and move it to blog.openspending.org (where it was originally). Either way defer this for the time being
This definitely needs sorting out and consolidating from the existing materials. We could do a straight migrate to start with though.
Currently called “Research” - “Guides” may be a bit ambiguous (guides to OpenSpending or to Money).
Maybe we call it something fun like “Guides to the World of Money” (though that won’t work in navbar)
Again, this is a bit of hodgepodge and we probably want to consolidate where we can.
Events and Collaboration
Ditto - can migrate what we have.
We plan to reuse the theme from http://opendatahandbook.org/