#1495 - Composr website documentation plan

Identifier #1495
Issue type Feature request or suggestion
Title Composr website documentation plan
Status Completed
Handling member Chris Graham
Addon General / Uncategorised
Description Make a TextMate bundle for previewing Comcode

Move docs to Wiki+ http://compo.sr/tracker/view.php?id=360

Move other docs to tutorials:
Community docs
Stuff from 'Goldmine' Dropbox directory
Steve Jarvis's tutorials into git (might need meet up with Steve to also review what is on the tracker) (needs clear Arvixe credit/banners) (maybe Steve gets adsense credit)
Any wordy or negative copy from our site
Chris's blog
The video from our old front page
Possible videos Chris uploading via Jing

Put video tutorials in our gallery, and have them syndicate to Youtube. Monetise Youtube videos via ads.

Implement the website design's carousel for showing particular tutorials. It must support Wiki+, and the gallery, and some predefined Amazon books (affiliate account). Automatically generate thumbnails based on standard images for keywords.

Pinned tutorials will answer the direct needs of particular personas - addressing their key concerns / requirements. All the latest buzz will come up as pinned tutorials, e.g. "social", "mobile", "big data", "cloud", "multi-channel delivery", "repository".

Add a generic git/Wiki+-based tutorial that links to the video tutorials inside the compo.sr gallery, and to the list of recommended books.

Create the concept of an 'Opinion piece' tutorial (keyword: opinion). Also the concept of a 'Transferable skills' tutorial and a 'bizdev' tutorial. Each tutorial will have tags to specify a target audience/persona (e.g. decision makers, implementors, developers, designers). Tags for all the broad categories we currently have (e.g. Progmattic customisation)
Apply requisite tags into the git tutorials. Add a unit test to ensure it is done thoroughly.

Should have a nice docs menu like https://developers.google.com/appengine/docs/php/config/does, plus a keyword list. Make it easier to add a new page to Wiki+, via a link on the nav.

Monetise tutorials via Google ads. Have an ad slot where revenue goes to the person who made it (do this via storing ad IDs in user profiles). Explain this on the contribute page.

Make sure tutorials are easily searchable. Maybe just use Google for it.

We will need to set up a redirects map on the old 'docs' URL structure [automated], mapping to whatever now is the best tutorial. Don't bother maintaining documentation for old versions (tell people it's in github).
Steps to reproduce

Related to

#360 - Unify Wiki+ with git

Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated