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.
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?
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.
We agree as well. Thats why we made tipe. We are focused on deeper, low code / no code integrations with frameworks that still allow fluid customizations.
1. Our frontend editor, where you edit content, is open-source. You can add new field types with react components easily.
2. The editor is also mounted on your site and lives there wherever you want. So, yousite.com/cms. We handle auth as well.
3. You define your schema in your code, like a DB schema, instead of in a GUI. Your schema lives in git with your app.
4. You can get started completely from the CLI, never touching a web app.
5. You can extend your schemas with plugins from the community.
6. We give your features like content previews right out the box with no code setup.
yea, you're absolutely right! I am the author of that said animation lib, ngFx, from years ago. Was actually my first open source project. When we started tipe years ago, we sunsetted that project and used the stars to generate hype for tipe. We were way ahead of ourselves :). Because we're in private release, all of our open source is private on github right now. Once we're not longer in private release, it will be public.
GitHub should tie stars to commit hashes to avoid this sort of crap. Your repos stars is calculated from the started commits that are in this repo but not any it's forked from, on the default branch.
Still prone to abuse from transferring repo to credit somebody else, but the original repo owner would have to sign off on the transfer at least.
I'm Scott Moss, CEO of Tipe (YC W18). We actually just saw that someone posted us on HN. So here to just drop a little bit about Tipe. Tipe is a headless, open-source CMS with a focus on Jamstack apps. Our goal is to have the quickest setup to allow your team to edit, preview, and publish content. We also want to enable you to customize and extend your CMS to fit your team's needs. You can even reuse components you already created in your app to customize tipe. The sky is the limit. We handle the API and infrastructure. We're currently in a Private release and are looking for teams who are using Next.js. If that's you, please sign up!
I'm not in this industry anymore but used to work for a company that provides CMS to fortune 500s. A significant portion of our customers used angular (not angularjs). Are you planning on supporting that as well or remaining react focused?
Absolutely, my career started with Angular and my co-founder created Angular Universal. We have big plans with Angular. You can actually use Tipe with any framework or platform, we're just focusing on our deep integrations one framework at a time for now it get it magical.
