Project Requirements for the New Orchard Website

7 Comments

requirements

To help achieve the projects objectives and goals, the project must meet certain criteria. These requirements can be seen as “Success Factors” or “Victory Conditions” in which the project can be measured.

I tend to write requirements down as User Stories which forces them to be user related. By doing this, each feature has a reason to exist and we combat against stakeholders asking for features that stem from opinion.

Creator Requirements

  • As a Creator I want to be able to quickly and easily download the right Orchard package for me so I can evaluate it
  • As a Creator I want to be able to quickly and easily find out how to install and setup Orchard so I can evaluate it with minimal effort
  • As a Creator I want to be able to learn more about developing with Orchard so I can get the most out of it
  • As a Creator I want to be able to learn how I can contribute to Orchard so I can help make Orchard better

End User Requirements

  • As an End User I want to be able to quickly and easily try Orchard so I can evaluate it without the need to download and install it
  • As an End User I want to be able to learn how to use Orchard so I can administer and manage my site effectively

Researcher Requirements

  • As a Researcher I want to be able to quickly and easily understand what features Orchard offers so I can validate whether it’s right for me
  • As a Researcher I want to be reassured that Orchard is a well-supported and fully featured CMS and is not going away anytime soon
  • As a Researcher I want to be able to assess the benefits of Orchard and compare with other platforms so I can be fully informed when making my decision on adoption

Administrator Requirements

  • As an Administrator I want to be able to quickly and easily add, edit and delete pages so I can keep the website up-to-date.
  • As an Administrator I want to be able to quickly and easily add community videos and articles so it doesn’t take too long to keep the website resources up-to-date.

Summary & Next Steps

Hopefully we have recognised and defined all the key requirements for the site. There may be other requirements that surface as we build the site but these are likely to be edge cases and shouldn't affect the design or development. Next we'll map the primary requirements as User Journeys.

  1. Objectives & Audience
  2. Orchard CMS Website Audit
  3. Comparing CMS Vendor Websites
  4. Humanising our Audience with Personas
  5. Project Requirements for the New Orchard Website (this post)
  6. User Journeys for the New Orchard Website
  7. Information Architecture for the New Orchard Website

7 Comments

  • Zoltán Lehóczky () - Reply

    Regarding the "try Orchard" point: as it came up on today's Orchard Community Meeting that we also have http://tryorchard.net/. Sebastien's opinion was, and I can't disagree, that "it's ugly" :-).

  • steve () - Reply

    Hi Zoltán,

    Thanks for your feedback.

    Yes, I'm aware of this site and I think I also agree about the presentation of it. But with that said, I think it could be a great way to demo Orchard quickly and easily. If the sites 'reset' themselves to an organised state so that every user has the same experience, then I think it would be better.

    Currently, and correct me if I'm wrong but our "try" options are TryOrchard or DotNest directly. That correct?

    I was initially thinking of a form like on Ghost that could post to DotNest and provision an account quickly. What are your thoughts on this?

    Thanks

    Steve

  • Zoltán Lehóczky () - Reply

    Hi Steve,


    didn't notice your reply, sorry! Will bookmark this page now and check back.

    TryOrchard sites are actually reinstalled every hour (5 sites in a shifted manner, so there is a new site every 12 minutes) so it works as you suggest.

    The two easiest/quickest/least technical ways to try Orchard are indeed TryOrchard and DotNest. Another slightly more complex way is to install an Orchard site from the Azure Gallery to an Azure App Service. And the final option before firing up VS is to use WebMatrix (even locally) to run Orchard easily.

    Re the Ghost-related idea: do you mean to have a form like on the top of https://ghost.org/? We could very well do that: it's basically a quick registration form which brings you to a quick setup form.


    Cheers,

    Zoltán

  • steve () - Reply

    Hi Zoltán,

    Yes, if we could have a really simple form such as email and password and this posts to dotnest with and creates a trial account automatically then i think this would be brilliant. In addition, the base content that is created could be a "getting started" guide that helps them try out some of the commonly used features.

    What you think?

    Thanks

    Steve

  • Zoltán Lehóczky () - Reply

    Hi Steve,


    I see, thanks for the suggestion! The current registration/site setup is not too much different so we'll look into this.

    Regarding a getting started guide: such an interactive guide is presented to users on the TryOrchard demo sites (in for of tooltips). This is what you meant?


    Cheers,

    Zoltán

    • steve () - Reply

      Hi Zoltán,

      RE: Getting started, I was thinking something really simple. When the site is provisioned and instead of a Welcome to Orchard page of content we populate that content with a getting started guide. There could be a few pages in the navigation with each page covering some useful features of orchard.

      What you think?

      Thanks

      Steve

  • Zoltán Lehóczky () - Reply

    Hi Steve,

    I see what you mean. This is basically just a matter of adding a new recipe to DotNest. The current TryOrchard demo site recipe and the walkthrough is more focused on being some kind of a tutorial, less a showcase. We could brainstorm about the idea during the weekly meeting.

    Cheers,

    Zoltán

Comments have been disabled for this content.