-
Notifications
You must be signed in to change notification settings - Fork 2
issue #96: new structure: split the code in Core and App #101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alexmerlin can you merge this ?
Signed-off-by: horea <[email protected]>
|
||
In the 6.0 version, the project is split into two main parts: **App** and **Core**. | ||
|
||
The purpose is to reach a headless CMS format for easier scalability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CMS format -> CMS architecture?
In the 6.0 version, the project is split into two main parts: **App** and **Core**. | ||
|
||
The purpose is to reach a headless CMS format for easier scalability. | ||
Headless CMS is a back-end-only content management system that acts primarily as a content repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for consistency, it might be best to simply use 'backend' and 'frontend' everywhere (no dashes, spaces)
The purpose is to reach a headless CMS format for easier scalability. | ||
Headless CMS is a back-end-only content management system that acts primarily as a content repository. | ||
Compared to traditional CMS platforms (e.g WordPress) that tightly couple the front end and back end, a headless CMS decouples the content management from the presentation layer. | ||
The content is delivered through APIs allowing any front-end to fetch and display it, making front-end and back-end development easier to work in parallel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'making front-end and back-end development easier to work in parallel'
to
'which also enables working in parallel on the backend and potentially multiple frontends.'
|
||
### Core | ||
|
||
The **Core** like the backbone of the application. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Core like the backbone of the application.
to
The Core is the backbone of your application.
### Core | ||
|
||
The **Core** like the backbone of the application. | ||
It's where the core logic lives. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's where the core logic lives.
to
It contains the core logic.
maybe?
It contains the core logic, the lowest-level features.
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
Signed-off-by: horea <[email protected]>
This also a base for the next documentation changes