Pelican VS tinacms

In my experience, [Pelican](https://getpelican.com/) does a good job of allowing you to edit themes on all pages at once with its static page generator.

There are a lot of built in features designed more for blog-like websites, but I’ve found it pretty easy to make my personal website with it.

Pelican is a preferred option for Python developers.

There's also Pelican but I haven't used it and seeing as Github serves static pages I'd imagine it builds and deploys your page and is done with it.

I use Pelican (https://getpelican.com/) for my blog, which works decently for me. It is a static site generator written in Python.

But you probably won't learn much Python by using it (or Rust when using a generator written in it) since you probably won't need to change anything in it.

Surely a "local private wiki ... not web based ... on a desktop application" is not really a "wiki" at all, but rather a "static site generator" with a built-in "search". If that's what you want, there's a Python app called Pelican. Writing such an app from scratch isn't really a beginners project.

Pelican — best for Python developers

You can - you'd basically just create a python script that parses your HTML/CSS files and replaces strings with values from your YAML. However I wouldn't recommend that unless you're just using this as an opportunity to learn Python. If you want to standup a real site and you want to use python, I'd recommend a Python static site generator like Pelican or Nikola.

As you're familiar with Python, how about https://getpelican.com?

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