Ghost VS pages-gem

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 -

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.