Angular Full Stack Boilerplate Starter with PayloadCMS, Nx and Express. Free Open-Source Web App Boilerplate.
Full Stack Angular boilerplate starter with the integrated open-source CMS PayloadCMS. Monorepository, Secure, Stable, Automated.
View our themes & templates https://binarystarter.com/themes-templates
View our themes & templates https://binarystarter.com/themes-templates
For full documentation refer to Documentation.
Using infrastructure as code, the infrastructure gets automatically based on typescript source code, using Pulumi. (https://www.pulumi.com/)
Latest stable versions are used. The repository is kept up to date and maintained by Florin Mateescu.
For full documentation refer to → DOCUMENTATION.
Let’s get started! 🚀
Run in a terminal git clone https://github.com/binarystarter/binarystarter-angular.git
. To specify another folder name, you can do a direct git clone https://github.com/binarystarter/binarystarter-angular.git <project_name>
.
Run pnpm install
.
nx serve web
nx serve express
The angular app can be accessed using http://localhost:4200. All paths are considered server side rendered, except the child routes of /c
https://example.com/c/**
which are part of the client app. (e.g. /c/dashboard
). Of course this can be adjusted per your needs.
The Angular client-side app can be accessed at http://localhost:4200/c/*
The express server is running by default on localhost:8080
. This can be adjusted by updating the .env
file
2.1.1 The payloadcms administration panel can be accessed at http://localhost:8080/admin
2.1.2 The payloadcms API can be accessed at http://localhost:8080/api
ExpressJs endpoints can be accessed from http://localhost:8080
The authentication system is based on Passport Js.
You get the following pages in Angular, connected with the ExpressJs and Payload CMS.
Angular comes with separated modules for the static pages and the single page application.
Separation of concerns is very important at this stage of development of the Angular Universal.
Static Pages are encapsuled in their modules and they don’t interact with browser APIs hungry components.
The Backend TypeScript types should not be available on the Frontend.
What most developers do is create the same types on both frontend and backend APIs, which makes a bad precedence of duplicated code.
This problem is solved by using a mono repository.
Managed by nx.dev tools - now extending TypeScript types from the Backend or creating them from scratch can be done in a single shared library between your Angular app and ExpressJs Backend.
We get all the benefits of a monorepository.
ExpressJs is tightly integrated with PayloadCMS, but you can still add your own routes, outside of Payload.
We believe in TypeScript, hence everything is based on TypeScript.