4 ms·

One of Sitecore's sells (.NET CMS) is non-technical users can manage content and control the layout of the page WYSIWYG style. Developers still work on it, but

One of Sitecore's sells (.NET CMS) is non-technical users can manage content and control the layout of the page WYSIWYG style. Developers still work on it, but it's less about app and page development and more about component and tools development. The key is allowing non-technical folks to work without much training. I don't think anyone has found the right balance yet.

Scotups 6y ago
With tipe, this is possible. You as a developer have complete control over what non technical people can edit. From layouts to actual text on a page. You opt into what you want to be dynamic. Snd with our instant preview feature, your team can see their changes fast.
- sbarre 6y ago
  A follow-up question, if you happen to see this: How does Tipe handle experience management, as opposed to content management? Since headless CMSes became popular 5-6 years ago (in large part thanks to Contentful), a lot of companies have moved to them based on the promise of separation of concerns, "omnichannel" publishing and better developer experience. But what a lot of people missed was that a traditional CMS like Sitecore or Wordpress etc provides not only content management (for structured content) but also experience management (for pages and layouts). And in larger orgs, these two things are often managed by different teams, but both are driven by business users, not necessarily developers. Headless CMSes typically only provide structured content management - by design - and so experience management ends up needing to be built into the consuming applications, which vastly increases their complexity (not to mention how you manage updates over time - developers now need to be involved), and that doesn't scale well. Or it gets shoe-horned into the CMS as a less-than-ideal type of structured content, and becomes hard to manage by non-technical folks. How do you see Tipe being used for experience management?
  - Scotups 6y ago
    Well said. We like to call that the magic of a CMS. Headless cms' are all so disconnected which ruins the magic. We want to maintain that illusion, like you're back in the wordpress days. So experience management is huge for us and we're putting much effort and research into it. Also allowing the community to build and share with others because we're open source.
cringepirate 6y ago
I am certified with Sitecore 6.5, However I haven't worked with it regularly in over 4 yeras so things have probably have changed (I've heard Sitecore 9 is very different than 6-8). One of the problems with the WYSIWYG editor was that the developer effort typically added and extra 50% effort onto any task and like anything with Sitecore you ended up having to dig through PDFs on their development portal. A slight aside though. One of the best things about Sitecore was its OOP approach to content. Every piece of content was an instance of a template. If you knew what you were doing with it you could build things very cleanly. I haven't seen anyone else implement anything similar in their CMS.

Scotups 6y ago

With tipe, this is possible. You as a developer have complete control over what non technical people can edit. From layouts to actual text on a page. You opt into what you want to be dynamic. Snd with our instant preview feature, your team can see their changes fast.

sbarre 6y ago
A follow-up question, if you happen to see this: How does Tipe handle experience management, as opposed to content management? Since headless CMSes became popular 5-6 years ago (in large part thanks to Contentful), a lot of companies have moved to them based on the promise of separation of concerns, "omnichannel" publishing and better developer experience. But what a lot of people missed was that a traditional CMS like Sitecore or Wordpress etc provides not only content management (for structured content) but also experience management (for pages and layouts). And in larger orgs, these two things are often managed by different teams, but both are driven by business users, not necessarily developers. Headless CMSes typically only provide structured content management - by design - and so experience management ends up needing to be built into the consuming applications, which vastly increases their complexity (not to mention how you manage updates over time - developers now need to be involved), and that doesn't scale well. Or it gets shoe-horned into the CMS as a less-than-ideal type of structured content, and becomes hard to manage by non-technical folks. How do you see Tipe being used for experience management?
- Scotups 6y ago
  Well said. We like to call that the magic of a CMS. Headless cms' are all so disconnected which ruins the magic. We want to maintain that illusion, like you're back in the wordpress days. So experience management is huge for us and we're putting much effort and research into it. Also allowing the community to build and share with others because we're open source.

cringepirate 6y ago

I am certified with Sitecore 6.5, However I haven't worked with it regularly in over 4 yeras so things have probably have changed (I've heard Sitecore 9 is very different than 6-8). One of the problems with the WYSIWYG editor was that the developer effort typically added and extra 50% effort onto any task and like anything with Sitecore you ended up having to dig through PDFs on their development portal. A slight aside though. One of the best things about Sitecore was its OOP approach to content. Every piece of content was an instance of a template. If you knew what you were doing with it you could build things very cleanly. I haven't seen anyone else implement anything similar in their CMS.