Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tipe raises $2.1M seed round to build a customizable CMS for developers

tipe.io

Post reply on HN
Print view View original

41–50 of 50 posts

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#41

Post by ErikAugust »

solidasparagus wrote: post #11

I can't find anything that explains what Tipe actually is. It's a plugin-based, customizable SaaS? Their GitHub page is some confusing bullshit where they seem to have taken the repo of a completely unrelated Angular animation library that has been inactive for 6 years and converted it to be Tipe, presumably to make it seem as if Tipe has earned 2.1k stars when it was actually the Angular project that earned those st…

Hey, at least you got $1000 in seed money for every fake star you got for the repo.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#42

Post by sk5t »

Scotups wrote: post #28
masonhensley wrote: post #27

Earlier quoted context omitted.

I think you are missing the point. Seems questionable to repurpose the repo to leverage the stars regardless of whether you posted it here or someone else did.

oh, yes, that was one of many mistakes we made early on. As we move to a public release, that is on our list to clean up.

But... you did this intentionally--when it would have been easier and simpler to not do so? Doesn't really fit the mold of "clean it up later" chores.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#43

Post by shard972 »

masonhensley wrote: post #27
Scotups wrote: post #24

Earlier quoted context omitted.

I agree. We didn't intend to post on HN until everything was public. Someone else posted it, so I'm here rolling with it.

I think you are missing the point. Seems questionable to repurpose the repo to leverage the stars regardless of whether you posted it here or someone else did.

Probably right down there on the list of questionable things a startup did to get funding.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#44

Post by shiftpgdn »

jameslk wrote: post #39
shiftpgdn wrote: post #37

Can anyone in plain English explain the advantage of JAMstack over the typical nodejs or LAMP stack? All I seem to get is jargon filled press releases from companies with millions of dollars of venture capital.

One offloads a large portion of rendering to the browser where as the other does it mostly on the server. Less processing on the server means less server costs. The former results in an API that can usually be repurposed more easily by other types of clients, such as Android and iOS apps. Also the API can usually be anything that responds to a HTTP request, such as Firebase, PostgREST, or even Airtable's API. Since t…

That makes sense. But isn't that punishing to lower end hardware users? Also aren't you moving much more data back and forth to do that?

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#45

Post by jameslk »

shiftpgdn wrote: post #44
jameslk wrote: post #39

Earlier quoted context omitted.

One offloads a large portion of rendering to the browser where as the other does it mostly on the server. Less processing on the server means less server costs. The former results in an API that can usually be repurposed more easily by other types of clients, such as Android and iOS apps. Also the API can usually be anything that responds to a HTTP request, such as Firebase, PostgREST, or even Airtable's API. Since t…

That makes sense. But isn't that punishing to lower end hardware users? Also aren't you moving much more data back and forth to do that?

> That makes sense. But isn't that punishing to lower end hardware users?

Yes, and the punishments will continue until hardware improves. More seriously, this is definitely a big trade-off. That's why page weight has been growing over time and client side metrics haven't been getting much better despite improved hardware and connection speeds. There's no free lunch. As I've mentioned in past comments, now's a great time to be a web performance consultant.

> Also aren't you moving much more data back and forth to do that?

Considering that usually the bulk of the frontend arrives once and then gets cached/runs continuously, I would say generally no. Server side rendering requires the page to be sent in whole on each request, unless you're doing some funky hybrid stuff with partial server rendering.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#46

Post by sbarre »

jameslk wrote: post #39
shiftpgdn wrote: post #37

Can anyone in plain English explain the advantage of JAMstack over the typical nodejs or LAMP stack? All I seem to get is jargon filled press releases from companies with millions of dollars of venture capital.

One offloads a large portion of rendering to the browser where as the other does it mostly on the server. Less processing on the server means less server costs. The former results in an API that can usually be repurposed more easily by other types of clients, such as Android and iOS apps. Also the API can usually be anything that responds to a HTTP request, such as Firebase, PostgREST, or even Airtable's API. Since t…

The other problem with this approach is that is moves a lot of complexity to the edge of your environment.

All the transformation & orchestration of your content has to happen in your app.

If you have one backend and one app, that's not necessarily a bad thing, because you have to do that work somewhere, but if you have multiple apps (perhaps by multiple teams) that all consume the same backend, you start to duplicate a lot of that complexity all along the edge of your system.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#47

Post by sbarre »

Scotups wrote: post #17
vsareto wrote: post #4

Earlier quoted context omitted.

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.

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?

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#48

Post by Scotups »

sbarre wrote: post #47
Scotups wrote: post #17

Earlier quoted context omitted.

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 li…

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.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#49

Post by Scotups »

former_cms_dude wrote: post #32

i used to work in enterprise cms implementations. a couple of thoughts: - in my experience most cms implementations are handled by a partner or vendor with some expertise. few businesses have the direction/leadership in place to hire a few devs of the intended cms and start hacking away. - if you are targeting enterprise you need to market to C-level (or slightly below) marketing people, not devs. marketing holds the…

Some good info there, thanks. I'll take note.

Re: Tipe raises $2.1M seed round to build a customizable CMS for developers

#50

Post by Scotups »

Ericson2314 wrote: post #35
Scotups wrote: post #28

Earlier quoted context omitted.

oh, yes, that was one of many mistakes we made early on. As we move to a public release, that is on our list to clean up.

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 am the original repo owner. I invite you all to try tipe for your selves. Signup
Post reply on HN