Post has attachment
Hoping to do a Sprint in August 2015. Will post the information in this forum but also over at PythonJamaica https://plus.google.com/u/0/communities/111289821697212352088

Post has attachment
The Kingston Sprints community is closing down.. If you're interested in Plone and by extenstion all things Python then please join Python Jamaica. https://plus.google.com/u/0/communities/111289821697212352088

Post has attachment
https://beta.toshl.com/ good example of illustration for documentation

Post has attachment
Examples of attractive documentation, with effective illustrations  are http://pow.cx/, http://yeoman.io and http://numberlaundry.whatcheer.com/ (just a single page). I also like this learn HTML book http://learn.shayhowe.com/html-css/

Post has attachment
https://moqups.com might be a useful tool for webpage related explanatory diagrams 

Post has attachment
New diagram explaining typical developer workflow, now added to the documentation see it in place at http://tinyurl.com/plone-newbie-dev-kit
Photo

Post has attachment
The product that the PNDK teaches developers to build is a staff profile product. So we need fake staff profiles, these are some mockups I'm working on. Would LOVE to hand it over to a volunteer designer
Photo

Post has attachment
More work on the profile pics that will be part of the demo product for the PNDK.
Photo

Roles needed
Writer, Quality Assurance, Site Editor, Coder, Illustrator, User Experience

My proposed checklist of tasks for the first sprint are all newbie friendly:
- test the PNDK, make sure that it is possible to follow the instructions as provided (role: quality assurance)
- rewrite/refactor - improve the PNDK documentation, where there are issues (role: writer)
- summarize the structure of a Plone add-on, describing each important file and folder (role:writer/coder)
- screenshots for the documentation. Some screenshots will require the fully built site with multiple staff profiles and views, (role:site editor)
- write scripts that make getting started even easier (role:coder)
- create illustrations that help to enhance the user experience (role:illustrator)
- read for UX - look over the documentation and propose how a single command might replace several steps (role:user experience)

If things are going really well then we'll also look into doing other tasks:
- porting the documentation to Sphinx so that we can auto generate the docs

All in all, this will be a documentation/quality assurance sprint, but it's kinda "meta" since you'll also have the chance to learn Plone development as you "test" the PNDK documentation.

Post has attachment
Wait while more posts are being loaded