twill VS sqlc

Since you're asking for PHP, it sounds like you want a framework to build your site with, and to manage content. There's Twill based on Laravel, or Ghost and Wordpress if you want tools in that space.

PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves Laravel based for marketing.

I've worked with Twill before, so I decided to use it for my project: an open, free system with rich features and good support. Why not? :-)

Twill is a great one for content focused admins.

PHP Headless Or you go with a Headless PHP CMS. Some options for that are Bolt CMS, Suru, Twill and ExpressionEngine. A Headless CMS doesn't have any frontend. It can provide you with a REST API or you create it in their template engine and integrate your JS stuff there. There are so many, i can't count them all. You can also search for Cockpit and Strapi.

Perhaps Twill comes close. It supports running it as a headless CMS. However, I am not so sure whether RESTful API's are provided out of the box. But it seems like the Twill (PHP) API allows you to relatively easy create the required REST API's.

I'm building something similar. Intranet/wiki site first and then later going to build the marketing site on top of it. Using Twill: https://twill.io/

So currently I set the goal for myself to learn inertia via https://laracasts.com/series/build-modern-laravel-apps-using-inertia-js and also maybe connect it to twill cms.

Twill

"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"

I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.

Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).

Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.

sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.

I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.

Now, we are going to generate the code. For this purpose, we are going to use sqlc.

https://github.com/sqlc-dev/sqlc — for use with //go:generate