twill VS Nest

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

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/