Content Folder
A content folder, in Jahia, is a folder that holds content items independently of the page tree. It supports a content-first way of working, where you create a product sheet, a news item or a biography once, in a folder, then display it wherever it is useful. One source can feed several pages, several sites or an application.
Definition and how it works
Content in a folder can be referenced in pages, displayed automatically by a list that queries the folder, or read by an application through the GraphQL API. Publishing a page that references folder content also starts the publication of that content if it is not published yet. It is managed in jContent, in the Content Folders section, where you create folders and sub-folders and then the content items themselves with Content Editor. A folder can be given an alternative, translatable name shown in jContent, separate from its system name (its technical name).
A folder can be limited to certain content types, so a "News" folder only accepts news items. This setting sits in the folder’s advanced options, is reserved by default for site administrators and only applies to content created afterwards. Folder content can also be exported and imported (XML or ZIP).
Academy documentation: introduction to content folders
Related terms: Content Repository · Content Editor · GraphQL API · Child · Content Reference
Resources that cover this term
Content folder vs media folder: the differences
A content folder differs both from file folders and from pages, which can also hold content.
| Term | How it differs |
|---|---|
| Media folder | Folders in the Media section store files (images, documents). A content folder stores structured content entered in Content Editor. |
| Page | Content created in a page area belongs to that page. Content created in a folder belongs to no page and can be displayed in several. |
| Content repository | The repository is where all content is stored. A folder is just one location in it, chosen to organize reusable content. |
Content folder in practice
An organization publishes the biographies of its experts. Rather than entering them on each page, the team creates an "Experts" folder limited to the "Biography" type. Section pages display the relevant experts through a filtered list, an article cites an expert by content reference and a mobile app reads the same folder through the API.
A corrected biography is corrected everywhere at once. The folder becomes the single source. The type restriction prevents other content from slipping in by mistake.
Frequently asked questions
Should a Jahia news item be created in a content folder or on a page?
If the news item only needs to appear in one place, creating it in a page area is simplest. If it must be reused on several pages, listed automatically by topic or read by another application, a content folder is the better choice, because the source stays unique and each page displays it in its own way. Both approaches can coexist in the same site.
Can we stop contributors from creating any content type in a folder?
The folder’s advanced options allow it, through content type restrictions that limit what contributors can create there. This setting is reserved by default for site administrators. It only applies to new content and leaves items already in the folder where they are. It is therefore best to set restrictions when the folder is created.