Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

Merged
merged 9 commits into from
May 6, 2025

Conversation

Howriq
Copy link
Member

@Howriq Howriq commented Apr 15, 2025

This also a base for the next documentation changes

@Howriq Howriq requested a review from alexmerlin April 15, 2025 14:40
@Howriq Howriq linked an issue Apr 15, 2025 that may be closed by this pull request
Copy link
Member

@arhimede arhimede left a 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 ?


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.
Copy link
Member

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.
Copy link
Member

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.
Copy link
Member

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.
Copy link
Member

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.
Copy link
Member

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.

@Howriq Howriq linked an issue May 6, 2025 that may be closed by this pull request
@arhimede arhimede merged commit ee83584 into dotkernel:main May 6, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

new structure: split the code in Core and App new handlers structure, with map and patterns
3 participants