Orchard Harvest Keynote 2015 - the CMS of the future
•Download as PPTX, PDF•
0 likes•2,840 views
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform. Orchard is built on a modern architecture that puts extensibility up-front, as its number one concern. All components in Orchard can be replaced or extended. Content is built from easily composable building blocks. Modules extend the system in a very decoupled fashion, where a commenting module for example can as easily apply to pages, blog posts, photos or products. A rich UI composition system completes the picture and ensures that you can get the exact presentation that you need for your content.
More Related Content
Similar to Orchard Harvest Keynote 2015 - the CMS of the future
Similar to Orchard Harvest Keynote 2015 - the CMS of the future (20)
More from Bertrand Le Roy
Recently uploaded
Recently uploaded (20)
Orchard Harvest Keynote 2015 - the CMS of the future
- 1. Keynote: The CMS of the future Sébastien Ros, Nick Mayne, Bertrand Le Roy
- 2. In 2010 Let’s look at the future of the past By that I mean the present as we viewed it back then
- 3. In 2010 We looked at the best CMS of the time That were all built on one of the worst languages ever for some reason
- 5. A streamlined setup experience Ask as little as we need Postpone decisions Accept temporary insecurity for simplicity
- 6. A runtime type system built from the right abstractions Content types Content items Content parts
- 8. Extreme extensibility Yo! I heard you like extension points, so I put extension points on your extension
- 9. X-copy deployment And we’ve been totally successful at making Orchard deployment as simple as copying a bunch of files. Lots of files
- 10. Edit source & save Because editing the source code of a site in production is such a bright idea
- 11. Modern admin What Would WordPress Do?
- 12. Multi-tenancy It’s so nice when your neighbor prevents the whole block from sleeping with their partying What are those walls made of? Paper?
- 13. Open++ Random strangers know better
- 14. We also screwed up a bit…
- 15. Relational schema Yo! I heard you like relations
- 16. All your app is belong to us You have to build on Orchard You have to refactor your features into Orchard modules
- 17. Undiscoverable processes You know this content type is a taxonomy, right?
- 18. Versioning - Will that module install properly on 1.9? - I don’t know. Try to install it.
- 19. Back to the future Which is less than three weeks away Unless you’re watching this on YouTube, in which case the future is in the past
- 20. It worked! Teslas for everyone! Well, no, not really.
- 21. Now what? Reset for the future of our present (which is the past’s future too, but more so than the present) Try to follow
- 22. The world has changed For the better Mostly Right?
- 23. Document databases are mainstream So people can switch from modeling documents in relational databases to modeling relations in a document database
- 24. The Cloud has won And all clouds have this exact shape
- 25. Containers & micro- services are in Because what your application needs in order to scale is http for procedure calls
- 26. JavaScript & CSS frameworks & transpilers 127 new ones have popped up while you were reading this Try to keep up, dammit!
- 27. Commodity site builders Just like Geocities, but with, like, video backgrounds instead of animated gif? Progress!
- 28. Mobile first Testing for a million devices is fun!
- 29. Social media & email So many more ways to sell you stuff
- 30. Beards are the new moustaches Facial hair is cool Like bow-ties and fezzes
- 31. Everyone develops on a Mac (which has nothing to do with the previous slide)
- 32. and deploys to Linux I have nothing My employer won’t let me
- 33. What are we doing? Finally, getting to the point
- 34. DecentCMS Trust me, I’m a scientist Listening to customers? Pff.
- 35. Orchard 2.0 Not your typical 1.x
- 36. New World The new .NET
- 37. X-Platform We’re all friends now
- 38. Composition It's what we do Erm, so why aren't we doing it!?
- 39. No implementations here Just give me the abstractions please
- 40. Swappable parts If you don’t like how something is implemented, change it.
- 41. Content Management This is not a CMS anymore
- 42. Build your own Create your own host!
- 43. Storage vs Querying They just aren’t the same thing!
- 44. Storage Store where you want!
- 45. Query Give me my stuff now!
- 46. I WANT NEW NOW Packages are cool man
- 47. Logging Log4Net is so not X-Platform
- 48. Configuration JSON vs XML vs INI vs YAML = Who cares
Editor's Notes
- Orchard is like an orchestra: there’s a partition, that lots of musicians follow to build a beautiful result together, but they are all doing something unique. Except for all those violins playing the same thing. OK, analogies are like vacuum cleaners.
- DI; modules; themes; small core; the rest is implemented as modules; all default implementation can be replaced Extensions are extensible
- Nothing to install except for ASP.NET; Dependencies are deployed with the application, even the database engine;
- It’s about site density, and it has strong architectural consequences. Good consequences: isolation, scope, etc. Picture source: By Robertafelice [GFDL (http://www.gnu.org/copyleft/fdl.html) or CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons https://commons.wikimedia.org/wiki/File:Row_houses_in_alternating_cream,_yellow,_and_gray_brick,_in_Bushwick,_Brooklyn.jpg
- License, governance, project management, code, documentation, translations, triage; public meeting twice a week We were ahead of the curve for a Microsoft team: not much was OSS at MS at the time. Other communities emulated what we did: Nuget, etc.
- This is actually Drupal’s schema. Ours is worse.
- For example, have a creative use of taxonomies, and your users won’t know where to add contents. Why are media, taxonomies, blog posts, lists, regular content items, in different places? What if I need to create related content items? Where’s my custom workflow?
- How do you know that an extension will work with the new version of Orchard? You don’t.
- Image from Back to the Future by Robert Zemeckis
- Image from Mass Effect by Bioware / EA
- Image credit: This file is licensed under the Creative Commons Attribution-Share Alike 4.0 International license. https://commons.wikimedia.org/wiki/File:InternetSlowdown_Day.gif
- We knew from the start that doc dbs were the best fit, but went against our gut: https://weblogs.asp.net/bleroy/nosql-is-not-about-object-databases What does this mean for our reliance on nHibernate as a deep layer of Orchard? Image credit: Couchbase http://docs.couchbase.com/developer/dev-guide-3.0/compare-docs-vs-relational.html
- Seriously, no, micro services doesn’t mean they have to communicate by http, let alone remotely: it’s about separation of concerns, single responsibility, deployment, elastic scalability, tool independence, and maintainability. Image credit: http://martinfowler.com/articles/microservices.html Martin Fowler
- Angular, Bootstrap, grid-based responsive design, LESS/SASS, TypeScript, Grunt/Gulp/NPM Image credit: © CEphoto, Uwe Aranas / CC-BY-SA-3.0 https://commons.wikimedia.org/wiki/File:Salarom_Sabah_Frame-of-a-new-house-01.jpg
- CMS as a service, with rich layout capabilities & e-commerce: SquareSpace, Wix, Weebly, etc. Image credit: Weebly
- Hi-DPI, too, and transitions In other news, IE is dead And so is the Web, to an extent: apps everywhere Image: http://www.last100.com/2007/08/27/nokia-to-revive-n-gage-for-the-third-time/
- Image credit: https://whatsnexttrinna.wordpress.com/2013/03/07/social-media-changed-the-world/
- Image credit: Junya Watanabe
- Image: https://xkcd.com/149/
- Image: Don Box “you’re doing what with XML?”
- My free-range experiment in understanding Node.js and building a CMS thingy with no external constraints. Image: Metropolis by Fritz Lang
- So we have done alot, we have learnt alot... So if we were to start again, what would we do better! Image from: https://www.youtube.com/watch?v=jcEws7il4EY
- Microsoft are building a new Asp.Net platform, we hear its better!
- Lets embrace these other platforms, the new world will allow us to do it.
- Orchard is composed of multiple modules of discreet functionality.... except Framework.. Lets break it up.
- In this new world, we want to break things up more. Implementations are great, but if they sit so low in the stack, changing them can be hard work. Lets change that. Image: http://www.amcgltd.com/archives/2005_05.html
- Swapping something out of the framework is hard... it 'almost' requires a rewrite... lets fix it. Image: http://www.fastcompany.com/3020825/tech-forecast/like-lego-for-smartphones-motorolas-ara-takes-things-modular
- One gripe we have had is that people love some aspects in Orchard, but decoupling other things like Content Management is a pain... lets change that.
- Orchard.Web is convenient... changing anything requires changes to core... That sucks... so lets change it! Image: http://legacy.nerdywithchildren.com/create-your-own-super-hero-kit/
- There has been this perception in the data access world that the fastest way to get your data is to query where it is stored... Not a bad idea... if everything is keyed on ID... But in today's world thats not even enough... So we should split it.
- By splitting storage we hand the power to you to tell the system where to store the data, if you want to use Entity Framework... cool, if you want to sdtore everything in json on the filesystem as well, thats fine. So you can then filter what you store where. Image: http://www.digitalspy.co.uk/tv/s269/red-dwarf/news/a662119/red-dwarf-wont-be-back-in-march-2016-trust-us.html
- So how do I get my data... Well, when the content is stored it is then indexed. You then use map reduce to query for that content which hit the index, the goes off to get your content by id and the reduces it. The idea behind map reduce is not for performance but for scalability, allowing you to deal with large dataset distributed.
- The Asp.Net team publish every build out to myget with updated package... you can get them... Lets do the same. Use the latest X and not the latest Y. Image: http://www.diaryofaninja.com/blog/2013/01/31/why-nuget-package-restorersquos-not-for-me
- Log4Net is cool, except... Its not cross platform and not everyone wants to use it, or they want to use multiple Loggers. VNext has a nice framework for that, so we dotn have to write our own! Lets do it. Image: http://www.fs.fed.us/wildecology/decaid/decaid_background/oldphotos.htm
- At the moment we have lots of configuration... in alot of places. Some YAML, Some JSON, Some XML... Lets provide the ability to allow you to choose what you want to use. VNext has a nice extension point for that. Sweet! Image: https://en.wikipedia.org/wiki/File:Dilbert-20050910.png