Page last modified 17:16, 23 Jun 2009 by Howleyda
Table of contents
- 1. The MDC Homepage
- 2. App thoughts
- 2.1.1. Name
- 2.1.2. Look and feel
- 2.1.3. Content
- 3. Deki Social
- 4. Deki Project
- 5. Comunity Building
The MDC Homepage
App thoughts
- Fix "login" redirect (registration should also store page trying to view?)
- Auto synchronization of accounts upon login if they don't exist in one system but the other (allow "bolting" on of other systems in the future
- Account merging from previous software? (assume same names == same accounts? ensure email validity)
- Ensure global cookie invalidation (dont like having one site logged in but not the other)
Name
- How about giving is a more fun name than MDC? Also, it would be nice if it said "Wiki" in the title of the site. Kind of makes it clearer to anybody that this is intended for group editing.
- I would try and ditch the name 'developer'. You are going to get editors, OSS users, etc, all collaborating here - the 'developer' in the title will put some people off. There needs to be a 'mindtouch.org' to go with 'mindtouch.com' in the way SugarCRM (and other vendors I can't recall here) do... crb 16 Dec 2008
- Also, MDC is the Mozilla community name (by its <title> at least). crb 16 Dec 2008
- community.mindtouch.com/org?
Look and feel
- Simple text-based design to reduce barrier to making changes
- Eh throw some logos around for color but keep it minimal
- Have a look similar to the Documentation page at mt.com so that people can easily navigate through the documentation along with contributing
- There's no easy way to link between the two without using external URLs - can this be fixed any? crb 9 Mar 2009
- Site should be navigable w/o the left pane (content-oriented navigation is crucial)
- Wikipedia-like Category navigation, possibly by tags? crb 9 Mar 2009
- BRING ON THE BUNNY!!!
- first, let's give this critter a name!
- second, let's make sure it's clearly feature on the homepage
- ensure the bunny doesn't dilute the branding though - I don't think I understand its relevance. opengarden was ditched, that theme at least had some relevance to wikis :) crb 9 Mar 2009
Content
Top level sections should be based on language: English, Japanese, Francais, Italiano, Korean(use language codes for the url and text for the nav display?). Also, tight coordination with the other languages is ++important. (cross reference articles that are available in other languages)
Need to consider removing unnecessary content or not indexing it. Sandbox can clutter search results as well as user pages. I think if user pages and the sandbox are not indexed then the core results should be more relevant. The other side effect of not indexing user pages is that people wouldn't post real info there. As a general rule of thumb going forward, user pages should be deemed private/staging grounds. If you want to link to information there-in then it needs to be moved it an appropriate location in the main hierarchy. Guerric
- Cleanly display the high level subprojects and 3-4 top level links for each project
- Deki
- FAQ
- API Reference
- Converters (MediaWiki, Confluence)
- Front Ends (Desktop Connector, Mobile)
- Extensions and Dekiscript
- Breakdown Extensions and DekiScript into Begginer, Intermediate, and Advanced to provide progressions for users learning
- Skinning
- Roadmap and work in progress
- Dream
- Tutorials
- Configuration
- Services
- Specs
- Roadmap and work in progress
- (Include less prominent links to subprojects such as converters and front ends)
- Include a dedicated page for EACH command line tool included with the distribution. If not documentation page exists for a command line tool, then the tool should not be included in the distribution!
- Deki
- Community Forge
- Skins
- DekiScripts (forums, blogs, etc.)
- PHP Plugins
- Extensions
- Download
- Links to the latest versions of popular packages of projects
- Get involved! (RoyK : This should be combined with the "Contribution" section)
- How to write an FAQ entry or tutorial
- Posting on the Forums
- Filing a bug
- Contribution
- SVN repo info
- How to contribute (patches, dekiscripts, localization, feature requests)
- How to report issues and get help
- Use a contribution form which would create pages and tags based on inputs and templates (?)
Dynamic contentCommunity Activity (this could be on the homepage itself - no need to bury it)
- Display top x recent page changes
- Most active recent forum posts
- Most recent mantis activity
- have a widget on our IRC channel (?)
- Breakdown legacy documentation
- Breakup documentation according to release as it still is pertinent
Deki Social
- Use PHP modules/hooks to handle the account synchronization between WordPress, vBulletin, and Deki, which removes the need to maintain a separate code base. It'd also allow Deki itself to become the focal point of the community.
Deki Project
Comunity Building
- Encourage users to join a weekly(?) scheduled chat with the mindtouch devs on irc to discuss specs, progress, feature ideas
- Job board - find contractors and find gigs?
- Localization - Encourage users to contribute localized docmentation
- migrate http://jp.opengarden.org/ to wiki.developer.mindtouch.com
- Tag page
- What links here
Images 0
Viewing 1 of 1 comments: view all
#1
crb says:
I would try and ditch the name 'developer'. You are going to get editors, OSS users, etc, all collaborating here - the 'developer' in the title will put some people off. There needs to be a 'mindtouch.org' to go with 'mindtouch.com' in the way SugarCRM (and other vendors I can't recall here) do...
Posted 16:29, 16 Dec 2008
Viewing 1 of 1 comments: view all
You must login to post a comment.