Summary
The project aims to translate the configuration of each entity display into a JSON response usable by any frontend solution.
Each response will include all necessary data to render a page, eliminating the need for subsequent calls for child entities or media.
Features
Site settings
The route '/ejson' provides basic site info:
- Site name
- Site slogan
- Default language
- Languages (each with lang code, labels and path)
- Hompage entity type and uuid
Retrieving content
Access content in JSON format through the route /ejson/{entity_type}/{uuid}/{display_id}. This endpoint:
- Handles References: Automatically iterates through all referenced entities to compile comprehensive content data, ensuring a complete representation of the requested entity.
- Optional Display ID: The {display_id} parameter is optional. If omitted, 'default' is used, allowing flexibility in specifying display modes for entities.
- Entity Display Customization: Leverage entity display settings to control which fields are visible. This is especially useful for tailoring the JSON output, including customizing image URLs for thumbnails and other media.
- Views: Using the type Entity/Content will provide the same structure as entities outside views.
Language Specific Content:
To retrieve content in a specific language, append a query parameter like ?lang=en to the URL. This feature enables on-the-fly language customization for your content, making the module adaptable for multilingual sites.
Supporting organizations:
Development time
Project information
- Project categories: Decoupled
27 sites report using this module
- Created by rfmarcelino on , updated
Stable releases for this project are covered by the security advisory policy.
Look for the shield icon below.

