You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/v6/extended-features/core-and-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ In the 6.0 version, the project is split into two main parts: **App** and **Core
5
5
When you start a new project, there are chances that the requirements are not defined well.
6
6
Because of that, your platform needs to be flexible and allow growth in the long term.
7
7
8
-
Our purpose is to reach a headless CMS architecture for easier scalability.
8
+
Our purpose is to reach a Headless CMS architecture for easier scalability.
9
9
Headless CMS is a backend-only content management system that acts primarily as a content repository.
10
10
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.
11
11
The content is delivered through APIs allowing any frontend to fetch and display it, which also enables working in parallel on the backend and potentially multiple frontends.
0 commit comments