The Orchard Spring Harvest Challenge is about getting as many modules updated to Orchard 1.8 as possible, thus the submissions should be about modules. The winners were announced at Harvest!

Minimal requirements for submissions:

  • Your module should be compatible with Orchard 1.8.
  • It should not emit any compilation errors or warnings.
  • It should not require any special setup or Web.config modification. Apart from other modules as dependencies (even 3rd party ones) it should be self-contained.
  • It should be available for download on the Gallery and its source should be available in an open repository.
  • All of its dependencies should meet the above criteria but dependencies won’t be taken into account.

Technical details:

  • Your repository should contain a full Orchard 1.8 source and your module should be added as a subrepository/submodule to it.
  • You should create a custom solution by copying Orchard.sln and rename it using the following pattern: Challenge.MyProjectName.sln.
  • The app path should be set to the project name, i.e. the Project Url under the properties/Web of Orchard.Web should follow this pattern: http://localhost:30321/MyProjectName.
  • Your repository should also contain an SQL CE database and a fully configured Orchard site that demonstrates the usage of module. The setup user's credentials should be: admin/password (to be safe).
  • Your repository should be powered by Git or Mercurial. You can download proper ignore files from Orchard Dojo. Make sure you use well-configured ignore files so you don't upload anything that is not needed (e.g. compiled DLLs), but you should upload everything you need for the demo site (e.g. Media folder, if you have any media items).
  • The projects will be evaluated according to their state at the application submission deadline.
  • The author and submitter can be an individual developer or a company too. If the latter, then there should be a dedicated contact person.
  • Each individual (or company) can apply with only one module. If the same person (or company) submits multiple projects, only the last one will be qualified.
  • Members of the jury and their affiliates are not allowed to take part in the competition.

The projects will be evaluated along these criteria:

  • Overall code quality:
    • Is the code well structured?
    • Does it follow common conventions?
    • Does it follow industry best practices?
    • Is it sufficiently documented?
    • Is it extensible if needed?
  • Overall user experience:
    • Is the usage easy to understand?
    • Is there enough help, either on the UI or in a separate documentation?
    • Does it work on various screen sizes?
  • Usage of appropriate Orchard features and services:
    • Does it build on existing Orchard features when appropriate?
    • Does it extend existing Orchard services when appropriate?
  • Usefulness:
    • Does it solve a real problem?
    • Does it solve that problem appropriately?


  • Every winner:
    • Paper certificate, signed by the members of the jury
    • Announcement on Orchard Harvest Seattle, the Orchard community site
  • First place:
    • Opportunity to demo the module on Harvest
    • Free entry to Harvest (this year or the next one)
    • 5 hours of online Orchard training and advisory from Lombiq
  • Second place
    • Free entry to Harvest (this year or the next one)
    • 3 hours of online Orchard training and advisory from Lombiq
    • 12 months DotNest subscription with all features
  • Third place:
    • 1 hour of online Orchard training and advisory from Lombiq
    • 6 months DotNest subscription with all features