twill VS Sentry

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

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry