search

OrchardCMS / Orchard

Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
https://orchardproject.net
BSD 3-Clause "New" or "Revised" License
2.37k stars 1.12k forks source link

Orchard Ambassadors ideas #7499

Open Piedone opened 7 years ago

Piedone commented 7 years ago

For anyone not on today's Community Meeting, this is now open: http://ambassadors.orchardproject.net/. The point is to gather community members who want to evangelize Orchard and give them various help to do this better and easier.

Under this issue we can discuss ideas related to Orchard Ambassadors. Below are some ideas that came up on the meeting.

  1. Also add highlights for content editors who know nothing technical under "How to present Orchard to specific audiences" on http://ambassadors.orchardproject.net/resources-for-orchard-ambassadors. Any suggestions on this?
  2. Having a slide deck and an elevator pitch for different audiences (including non-technical) would indeed be useful. Non-developers could also use this (e.g. "I'm a project manager and I like how my dev team works with Orchard.")
  3. Would pre-prepared basic code demos be useful? (Not tutorials, just some code to give a half an hour demo to a C# dev audience on how Orchard development works.) BTW we at Lombiq commonly use the Abstractions module's (https://github.com/Lombiq/Orchard-Abstractions-Examples) simplified content part development model to showcase content part development by keeping the core concept but shaving off the boilerplate.
  4. Let's formulate the vision of Orchard, i.e. why is there an Orchard if there is also an Umbraco and DNN for example? What is the main distinction?
  5. Let's not have a barrier of entry to become an ambassador apart from some basic check that the person doesn't just want to promote their presence. On a related note, who should check applications? At the moment Benedek and me get the e-mail notifications and if it's just a simple check we can do it.
  6. Badges on the websites with specialties of the person: e.g. Azure, AngularJS.... This way it's visible how the person's viewpoint on Orchard can be different (e.g. how do you host it in the cloud? How does it play together with modern client-side frameworks, how to I build SPAs with it?).
  7. Accept contributions in some form. We could e.g. have an "Ambassador's Swiss Army Knife" GitHub repo with everything in it: slide deck PPTX, elevator pitch in Markdown... This could be even synced to content items on the site, i.e. the textual content could be browsable there too.
  8. Free custom domain usage for Ambassadors on DotNest to be able to create a quick portfolio/introduction site?

Anything else? What would you need to evangelize Orchard to fellow devs or to "sell" it to prospective users?

BTW if anybody wants access to the website, just ask.

Who have taken part in the discussion, FYI: @bleroy @sebastienros @DanielStolt @sfmskywalker @roballred @jersiovic

abhishekluv commented 7 years ago

I'm in 👍

Piedone commented 7 years ago

Added Abhishek's profile.

durkc commented 7 years ago

In! This is a great idea, and I am looking forward to getting involved.

I think that it would be useful to have a datasheet of CMS features that compares Orchard side by side with some of the other popular CMSes. It would help with proposals where the client is considering multiple options but leaning toward a particular CMS.

I like the idea of the Swiss Army Kit repo.

Another thing that would be great to have would be some all inclusive quickstart website samples for different types of Orchard websites. For example a business website, personal portfolio, e-commerce, simple blog, etc. I'm talking about not just themes, but actual content with nice design, full module configuration according to best practices, etc. This is something which IMO would greatly simplify adoption of Orchard by developers who might otherwise feel lost when starting up. It would also make it easier for us to set up demos to present to prospective clients.

Piedone commented 7 years ago

Do you have some specific format for the datasheet in mind @durkc , or any examples where there are CMSs listed already and we could add Orchard?

For the website quickstarts, I think that's a good idea we could implement even with DotNest (there's a similar older idea to have some typical websites pre-baked, like a better Blog recipe): there could be recipes to do the various configuration and add some test content. These recipes could be used in a stand-alone way too (or on DotNest for quick demo sites), given they only use freely available modules and themes.