Hi folks (both in @website-wg and everyone else)!
As you've probably noticed, we're ramping up to get a new site framework launched as soon as possible, and start the ongoing process of improving & refining its content. Thanks to everyone who's provided some ideas and inspiration in our discussion topic from last week -- it's not too late to add ideas if you have more:
Moving forward, I wanted to get feedback from all of you on the website team (as well as the ODK PMC & the "general public" too) about some "requirements" for what the new release of the web site should accomplish/include. These are based on some earlier discussions, but it's not too late to change or improve them.
7 Key Requirements
- The new site should have an open team of self-identified volunteers -- @website-wg -- to help support it over time.
- The content of the new site should be up-to-date and reflect the current state of all of our community's major software development work. (There may be some "experiments" & smaller projects not mentioned.) This includes pointers to end-user & developer documentation for the ODK 1 & 2 families. Some content may live on the forum or other documentation sites. The "download" section should also be improved.
- The site should "go live" as soon as possible, with a goal of launching the "first new release" at the end of January.
- The technology platform should allow anyone to recommend content changes, and ensure those content changes have some type of peer review process before going live.
- There should be a system to allow different individuals permission to edit different parts of the web site. (e.g., Not everyone should be allowed to edit the home page, but folks should be allowed to make changes to their own specific project content.)
- Where possible, URL redirects should be used to avoid broken links from old versions of the web site.
- The site should allow easy updates & "growing room" for a new ODK logo, new project names, and other organizational & strategic changes from the PMC (and any successors) as well as software projects teams such as the TSC's. It should not be stressful or difficult to deploy these content changes as ODK projects grow.
So, what do you think? Please vote here:
- These look good to me!
- No strong opinion.
- I've got a suggestion or new idea to discuss. (Please comment below.)