Feature Roadmap

In October 2009 the project team began working on our first application, the Orchard CMS. We are following a three week iteration model, using an agile, test-driven approach to software development. In the near term, we’ll be implementing the features below. The feature roadmap is subject to change as the project evolves, and we welcome your input.
Currently implemented
  • Basic admin panel and login
  • CMS page creation and management
  • Page templates and content zones within pages
  • Content editing and publication (drafts, scheduling, preview)
  • Some initial composability infrastructure (based on MVC2 areas)
Priorities for the current iteration [ending 11/13]
  • Media management (RTE support for images, videos, etc)
  • Users, roles, membership and profile data (Users/Roles, Mgmt, OpenID)
  • XML-RPC (Live Writer, WordPress API, MetaWebBlog)
Areas of focus for future iterations (backlog, not in priority order)
  • Pages – Creation of pages, layout of content on pages (zones), page templates
  • Content – Different content types/metadata, viewers and editors for content
  • Editing – Rich text editing experience over content
  • Publishing – Workflow/permissions, draft approval, history (restore from)
  • Media – Media upload, management, insertion to content
  • XML-RPC – MetaWeblog (Live Writer), WordPress API
  • Blog – Implement Oxite functionality as an Orchard module
  • Tags – Associate tags with content types
  • Votes/ratings – Associate ratings/rankings with content types
  • Comments – Associate comments and reviews with content types
  • Moderation – Comment/content moderation and spam protection
  • SEO – Semantic URLs, metas/keywords, Web standards, sitemap
  • Search – Ability to easily search application content using local and external engines
  • Navigation – Navigation management, front-end UI (menus, breadcrumbs)
  • Syndication – RSS and Atom Feeds (in-bound, out-bound), Email subscriptions
  • Setup – In-browser, Web PI, and hoster control panel
  • Admin – Extensible dashboard for app/extension configuration and management
  • Settings – App-level, extension-level settings definition and UI/management
  • Database – Database configuration (local in-memory and server), import/export
  • Users/Roles – Authentication/permissions, users and role management
  • Modules – Componentization architecture, based on MVC Areas
  • Themes – Theming model, UI to install/remove themes
  • Plug-ins – Extensibility model for event handling and filtering hooks
  • Widgets – UI components mapped to content zones
  • Packaging – Extension packaging and installation UI
  • Servicing – Update notifications, in-place and non-destructive updates
  • Performance – Caching, optimization, script combining/minification
  • Logging – Trace, debugging, profiling
  • Analytics – Reporting, site-use statistics
  • i18n – Localizable, time zone and calendar aware
  • Marketplace – Ability to browse/install extensions from online gallery
  • Other Domain-specific Modules – Commerce, Wiki, Forums, Ads, etc
Last edited Nov 9 at 1:41 PM by bradmi, version 3
Comments
findbug Fri at 3:38 AM 
I do not know what is the reason for guys from ASP.NET team to create another CMS. There are already Umbraco and Kooboo CMS or even Share point, which almost does anything you described here. Why didn't your guys choose something that is new and niche?

This is great for end users, because end users will get more choices, good for developers to learn coding as well.

However this will seriously discourage developers like me to write another CMS in ASP.NET MVC. Something directly come out from ASP.NET team will have unfair advantages on the competition.

ScottGal Fri at 10:02 AM 
I don't believe that Orchard is designed to compete with those platforms, it's more about building a framework which anyone can use. There's a ton of plumbing that has to go into building things like CMS applications / even forums and ecommerce sites. Personally I'm delighted that the team (disclaimer, I was on the ASP.NET team, but not the Orchard team which is distinct) are building a totally open, extensible framework that I can frankly steal for my own apps; or even just steal ideas.

Updating...
© 2006-2009 Microsoft | About CodePlex | Privacy Statement | Terms of Use | Code of Conduct | Advertise With Us | Version 2009.10.27.15987