canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
DevMo Project Plan Notes: Difference between revisions
Jump to navigation
Jump to search
m
→Strategies
m (→Strategies) |
|||
| Line 22: | Line 22: | ||
Keys to this project�s long term success: | Keys to this project�s long term success: | ||
* Create backend components in such a way that the front end �glue� (portal/CMS) can be completely torn down and reworked from scratch without having to redo huge amounts of content and structure. We really don�t want to have to start this over again in three years. | * Create backend components in such a way that the front end �glue� (portal/CMS) can be completely torn down and reworked from scratch without having to redo huge amounts of content and structure. We really don�t want to have to start this over again in three years. | ||
* Create backend components with an eye towards future extensibility and scalability. We need to start small and grow quickly without creating an unstable and hard-to-maintain disaster. Make sure chosen technologies are proven in the field wherever possible. | * Create backend components with an eye towards future extensibility and scalability. We need to start small and grow quickly without creating an unstable and hard-to-maintain disaster. Make sure chosen technologies are proven in the field wherever possible. | ||
* Create the system in such a way that it is easy and rewarding for users to contribute content without huge barriers to entry. Define the expected skill sets of the various expected contributors then create the system with those skill sets in mind. It has to be easy to add, edit, and update content without having to worry about gatekeepers, technology hurdles, and other flaming hoops. | * Create the system in such a way that it is easy and rewarding for users to contribute content without huge barriers to entry. Define the expected skill sets of the various expected contributors then create the system with those skill sets in mind. It has to be easy to add, edit, and update content without having to worry about gatekeepers, technology hurdles, and other flaming hoops. | ||
* Ensure that the system facilitates content creation. Lower the barrier to entry to a point where writers, editors, and translators can get in, create new content or make changes, and have that content integrated into the site as easily and quickly as possible. The caveat to this, of course, is that if it's easy to create content, then the quality of added content will be variable. There will have to be people tasked with reviewing added content and ensuring that it's of suitable quality, adheres to the editorial standards, is positioned properly within the content as a whole, and so forth. There is a place here for leaders within the community, but more as facilitators and editors, rather than as gatekeepers. | |||
== Plan == | == Plan == | ||