Bridgetown VS tinacms

Jekyll is a simplistic framework for static websites that originally sparked the static website and JAMstack movements. While there are many similar frameworks with more features, Jekyll remains one of the simplest on the market. It has been somewhat forgotten and hasn't evolved much lately, to the point where some people decided to take matters into their own hands and fork this framework into something called Bridgetown.

I use https://www.bridgetownrb.com/ and it works pretty well. Very easy to use and deploy. Blog posts are listing line by line, like "index". I didn't customize much from the generated code(only logo and header). You can take a look: ruzig.com

I'm using bridgetown because I like sitting on the bleeding edge, its basically a newer Jekyll which I would recommend checking out too. Bridgetown has a great modern dev experience but its missing some of the ecosystem from Jekyll. Not a problem for me because I'm really comfortable with Ruby.

If you want to have a different UI or your blog to look in a very specific way I recommend using Jekyll or Bridgetown.

If I wanted to post a simple website today I would look into Jekyll. There are a ton of articles and answers to common questions etc. It itself is written in Ruby but using it will not likely help you to learn Ruby. One-step in the direction of learning Ruby and getting a simple website could be Bridgetown. This will start you down a path of learning Ruby and not Rails. We use Bridgetown for our company site at Flagrant.

In the Hotwire Turbo world specifically, several discussions about integrating transition animations also took place and a few promising approaches emerged, namely the Turn project or the transitions in Bridgetown. There is also a chapter in the Noel Rappin’s Modern Front-End book and an interesting article but overall, frankly, this topic still fells somewhat early-stage and exploratory.

https://www.bridgetownrb.com/ static site generator. Can be linked with prism of you want a kind of panel to add new articles.

FYI. I used Bridgetown as a static site generator recently and rather enjoyed it. https://github.com/bridgetownrb/bridgetown.

Its inconvenient to have to sit in front of a computer and open a text editor to write a blog post every time. A common solution is to use a CMS (Content Management System). I used to use Decap CMS (formally Netlify CMS), but it wasnt very convenient for connecting to a GitHub repo, and it didnt generate a blank line between YAML frontmatter and the body, which sometimes caused issues. So this time, I used Tina CMS. Fortunately, Tina Cloud is free for up to two users.

Oh thank the stars!

> Do note that I believe the current plan is to have two-way sync between files and the db, so presumably custom modification of md files should still work fine. But we'll see how that evolves.

Perfect, fingers crossed. There was a submission Trying TinaCMS a couple months ago that mentioned what sounds similar & ideal to me, Keeping flat files as a source of truth then having a projection of those files in a DB for faster querying. You can just throw the whole DB away & TinaCMS will rebuild it as needed. I love this approach as a way to give everyone what they need, fingers crossed we see similar here with by beloved Logseq.

https://tina.io/

Tina.io

> 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.