The Next.JS Boostrap is used inside headless projects only.
But what is headless?:
Traditional websites have their own back-end and front-end (graphical user interface). All the pieces work with the same code base and communicate directly with each other, making the website as a whole. However in a headless installation the front-end is a stand-alone piece of software, which through API communicates with a back-end. Both parts operate separately from each other, and can even be placed on separate servers, creating a minimum version of a multi-server architecture. The bridge between both parts is the API client. The endpoints of the API are connected to each other.
The biggest advantages of this technology can be found in performance optimisation and flexibility of the software stack.
_scripts/ <-- Contains a collection of scripts
build/ <-- Contains the config files used on other environments
drupal-config/ <-- Contains all drupal config files (yml)
utils/ <-- Contains all util scripts (bash)
vagrant/ <-- Contains all vagrant provision files (yml, conf)
app/ <-- Contains the Next.JS custom server
config/ <-- Contains the app config
log/ <-- Contains the app logs
mocking/ <-- Contains the app mocking database files (json)
tasks/ <-- Contains the CLI task files used for crons (js)
bundle.js <-- Is the default entry file when building for production and requires the <code>server.js</code>
server.js <-- Is the default entry file when developing
frontend/ <-- Contains the frontend files (React/Preact)
pages/ <-- Contains all frontend pages
scss/ <-- Contains all global SCSS
public/ <-- Contains all static public assets
public/ <-- Contains all public available files
cms/ <-- Contains the CMS
next.config.js <-- Contains the Next.JS config
package.json <-- Contains all NPM dependencies
README.md <-- Contains the project readme
Vagrantfile <-- Contains the Vagrant configuration
Last modified | Friday, April 30, 2021, 12:00:21 PM UTC |
Last author | Colin van Eenige |
Commit ID | 4c7a701 |