Monolog VS cms

To add onto this, what's more commonly done these days is to use a library like Monolog which can be configured with multiple log handlers. One of the handlers which are typically enabled is one which writes to error_log. You can add more which write directly to a logging service like Sentry or whatever, or even in dev write an HTTP header paired with a browser extension which puts your backend log messages in your browser console (see the handler + install the extension for chrome or firefox)

Monolog is a highly regarded PHP logging library with open source code. This project extends a straightforward and adaptable API, allowing developers to log messages from their PHP applications to diverse channels, including files, databases, and various third-party services. The modularity of this project’s source code provides an assortment of handlers and processors that seamlessly combine and configure to cater to specific logging requirements for any application.

If you need something more flexible you could always use Monolog which provides a bunch of adapters to log to any service want. You could for example use the syslog adapter to send your logs to syslog, and then configure rsyslog to print them directly into your terminal (or just `tail -f` a log file).

PHP -> Built in Logger, Monolog, Analog, KLogger, Log4PHP

So far, I've been discussing what PHP itself has to offer, which, quite frankly, is not very appealing. Luckily, though, there are great developers involved in pushing beyond those boundaries, making the appearance of great tools a reality. That is the case for Monolog.

Laravel (and many other frameworks) use the Monolog Package for logging by default. Using their formatter does everything you need!

Nowadays all popular frameworks comes with logging system built in. If not, you should use http://seldaek.github.io/monolog/.

Laravel logging is created on top of Monolog, which is a powerful logging library for PHP projects. In this guide, we will be looking at how to send our laravel logs to telegram channel with the help of the Telegram Bot API.

Statamic is one of the best flat-file CMSs. It’s built with Laravel and can be used as a headless Git-based CMS as well. The paid professional version allows you to use REST APIs and GraphQL APIs for content management and offers a GitHub integration for content storage and editorial workflows.

Aah, that's always a controversial question, on one hand, some universal rules of usability do exist, but on the other hand, everyone's habits, taste and use cases are very different.

The most neutral definition of a "well designed" website, without any further context, could be "created in a way that helps users achieve intended goals efficiently, while keeping max number of users happy about its look".

Again, different audiences will have very different answers. Here at HN, sites like https://www.mcmaster.com/ and https://www.craigslist.org win – because HN users appreciate old look and how efficient these sites are.

https://www.apple.com/ is an industry standard of a marketing site for consumer tech. It's not universally "well designed".

Other examples of well done marketing pages: https://www.sketch.com/ ; https://statamic.com/ ; https://linear.app/ got its share of hype recently.

Other times, a website is well designed because its content is awesome and is easy to consume. See https://ciechanow.ski/ and https://www.joshwcomeau.com/

Is https://github.com/ well designed? As an amateur developers, I'd say yes.

Is https://htmx.org/ well designed? Hmm, at a glance, there's no design at all. Is no design also design? That's a rabbit hole.

P.S. I often hear my website is well-designed :-)

Local CMSs are the ones that are mostly file-based (like Statamic or Astro). This means that you can edit everything locally and deploy the data. This way, our CMS is more secure, but on the downside, you have to have a local server working, and you might experience more conflicts, especially when two people will work on the same article (although Git might save you from many of those). It also means that there is a higher learning curve. A remote CMS works somewhere on a server, and most users don't care how.

I use Statamic, the free version will do everything your looking for and it can be as simple or as complex as you need it to be. It's flat file based (by default) too so deployment / version control is super easy.

Statamic (PHP / Laravel)

I'm not in the market for a CMS but if I were I'd likely go with https://statamic.com/ if I needed to build something from scratch.

If you're looking for a great CMS and were bitten by WordPress back in the day, you should take a look at Statamic (https://statamic.com)

It's a Laravel package and it's the best CMS I've ever used (from a dev perspective). v4 just dropped the other day

https://statamic.com free for personal. Your welcome.