Most of the tutorials including the official one, recommends Ubuntu OS and Nginx proxy to install Ghost but I have just installed on Debian as mentioned in my previous post, and Apache stack finally. Adding some side notes, if your MySQL database is not correctly configured for Ghost then you may run into some issues. If you feel like trying Ghost with my approach, read this guide:
https://www.fastcomet.com/tutorials/ghost/apache-proxy-ghost

The past couple of days, I’ve been thinking about what blog platform would be the best option. There is a wide range of modern CMS and static page editors available on the market. Obviously my first thought went towards Wordpress but I didn’t want a robust system coupled with hardly maintainable plugins. After a week of research and testing several blog-aware platforms like HUGO or Jekyll, I've decided to take the plunge and make the next blog in Ghost rather than WP.
Ghost is a clean and lightweight platform designed for bloggers who want to focus on blogging and nothing else. It works like a fast Headless CMS using Node.js and Markdown rather than visual WYSIWYG editing, but you can change that by means of extensions. Much like WordPress, Ghost comes in two variants:

• self-hosted version that is free to download and use and
• hosted version on Ghost’s own servers.

Installing Ghost is pretty smooth unless you have a very subtle OS with lots of utils and apps running on Debian Linux, like the case of myself. In general, it only requires to install Nginx as proxy, MySQL/MariaDB, and use Let’s Encrypt SSL certificate to secure Ghost website.

Automating HTML to PDF conversion can be a real struggle. Even with wkhtmltopdf, one of the most favored command line tools was also unable to render modern CSS layouts like grid and flexbox. After testing several workarounds, the whole process has thankfully been packed into a docker image by TheCodingMachine:
 https://github.com/thecodingmachine/gotenberg
This makes the maintenance and usage of Headless Chrome based pdf generation in production environments smooth and hassle-free. As all the other solutions struggle with newer (or not so new anymore) CSS features like grid and flexbox, this was in my case the only solution to produce a proper PDF output. Of course, Headless Chrome has some limitations and requires some additional tweaking but this approach allows us to generate more useful, professional PDFs. 

Moving to microservices? Great but the first question before you write a single line of code is: How do you organize your codebase — do you create a repository for each service or do you create a single ‘mono repo’ for all services?

Reasons why you should choose a Jamstack Headless CMS: 

1. It’s easier to build fast and secure websites that scale
2. Enjoy a better developer experience with modern tools and frameworks
3. Access content in a variety of ways including REST, GraphQL, and GROQ​ 
4. Store content as data in flexible Portable Text
5. Preview anything within your CMS
6. Deploy scalable Jamstack sites in minutes with Netlify and Vercel
7. A headless CMS will let your content travel further and do more things (not just the Jamstack!)

headlessCMS.org offers a fairly comprehensive list of headless content management systems.

Sass and Tailwind CSS are not in the same league. Sass is a pre-processor for CSS, it basically allows you to write CSS in a more developer friendly way. Tailwind is a CSS framework that allows you to set CSS properties onto elements just by passing in a specific class.