Ghost VS tinacms

Diversifying a lot. Next acquisition will be Ghost(https://ghost.org/) I bet. Similar DNA, fits in the portfolio (If they are trying to match the feature set of Google) and have no VC backing.

For example, if you are in a country where you can accept Stripe and are publishing a newsletter through, Substack or using the Ghost platform, enabling the ability to accept payments is a few clicks away. For those who cannot accept payment with Stripe, well, you are up the creek without a paddle. I do not know about you, but I see that as a barrier to access.

This response from one of the Tea developers seems disingenuous https://github.com/TryGhost/Ghost/pull/19743#issuecomment-19...

How could they not have predicted this outcome?

glee our dev friendly blogging setup has been undergoing a huge transformation for the last few weeks. For those who don't know, glee is a simple open source CLI tool that converts markdown posts into ghost blog posts. Check out the glee demo video when you have a moment! glee: Dev-friendly Blogging Setup

Ghost: The Underground Storyteller

Ghost is used by creators to run their own website to publish private content

Not the OP but it looks to be https://ghost.org/

I use it as well for a small development blog and it's been an enjoyable experience

PlanetScale and Ghost were previously incompatible due to differences in their support for foreign key constraints. With PlanetScale now supporting foreign key constraints, a seamless collaboration between the two is achievable. Nonetheless, there remain minor incompatibilities that require resolution.

I'm a big fan of Ghost for new blogs https://github.com/tryghost/ghost

Ghost -

> Why is are all static site generators (that I am aware of) are CLI? What prevent simplistic drag and drop GUI/WYSIWYG that generates those clean static files?

Check:

- Tina CMS: https://tina.io/

- Primo CMS: https://primocms.org/

Anyway, you seem to be holding the wrong end of the stick. Static generation is the easy part, what you're looking for is a subset that falls under the CMS umbrella, just search for `CMS+SSG` you'll find a diverse set of solutions.

You can also setup any generic Headless CMS to trigger generation for a static site. Why would someone build a full fledged CMS and limit it to a niche market inside a niche?

Tina CMS, formerly Forestry, is one of the best open source Git-based CMSs in terms of the provided feature set. It covers the basics, such as:

Try tina cms https://tina.io

Currently testing it with Docusaurus for our documentation site.

The next step in building this demo blog application is to set up TinaCMS, an open source headless CMS that supports the Markdown format.

Solutions like CloudCanon or TinaCMS use this approach.

With TinaCMS, all your content changes are committed directly to Git. This enables your team to create a variety of workflows for reviewing and merging content updates. By leaning on GitHub, you can integrate CI/CD into your content workflow.

Check out this license for example: https://github.com/tinacms/tinacms/blob/main/LICENSE

It's an Apache 2.0 license, but with adendums.

Would it be reasonable to say that I could fork their repo for own purposes, and argue in court that I was only familar with Apache 2.0, and not their modified terms?