This page lists first steps you can take after installing Ibexa Platform. These are most common actions you may need to take in a new installation.
To go through a full tutorial that leads from a clean installation to creating a full site, see Building a bicycle route tracker in Ibexa Platform.
Remove welcome page¶
To remove the welcome page and get a completely clean installation to start your project with, remove the following files and folders from your installation:
- Delete the file
- Delete the
- Delete the
- Delete all
Encore.addEntrysection and uncomment the last line, so that the end of the file looks like this:
1 2 3 4 5 6 7 8
Create a Content Type¶
1. In your browser, go to the Back Office:
<your_domain>/admin, and use the default credentials to log in:
You will be requested to change your password at first login. For more information about passwords, see Passwords.
2. Select Admin and go to Content Types.
3. Enter the Content group and create a new Content Type.
4. Input the Content Type's name, for example "Blog Post", and identifier:
5. Below, add a Field definition of the type Text Line. Name it "Title" and give it identifier
6. Add another Field definition: Text (type Rich text) with identifier
7. Save the Content Type.
Create Twig templates and match then with view config¶
To display Content in the front page you need to define content views and templates.
Content views decide which templates and controllers are used to display content.
add the following block (pay attention to indentation:
site_group should be one level below
1 2 3 4 5 6 7
Content view templates use the Twig templating engine.
2. Create a template file
Create content and test view templates¶
1. Go to the Back Office, activate Content/Content structure and create a new Content item using the button in the right menu.
2. Select a Blog Post Content Type. Fill in the Content item and publish it.
3. To preview the new Content item on the front page, go to
For example, if the title of the Blog post is "First blog post", the address will be
You can use SiteAccesses to serve different versions of the website.
SiteAccesses are used depending on matching rules. They are set up in YAML configuration under the
config/packages/ezplatform.yaml add a new SiteAccess called
de for the German version of the website:
1 2 3 4 5 6
The SiteAccess will automatically be matched using the last part of the URI.
2. You can now access the front page through the new SiteAccess:
At this point you need to log in to preview the new SiteAccess, because an anonymous visitor does not have permissions to view it. See section about permissions below.
For now the new SiteAccess does not differ from the main site.
Add a language and translate Content¶
One of the most common use cases for SiteAccesses is having different language versions of a site.
1. To set up the
de SiteAccess to use a different language, add its configuration under
1 2 3 4 5 6
This means that German will be used as the main language for this SiteAccess, and English as a fallback.
2. Go to the Back Office and select Admin > Languages. Add a new language called "German", with the language code
Make sure it is enabled.
3. Next, go to the Content structure and open the blog post you had created earlier. Switch to the Translations tab and add a new translation.
4. Select German and base the new translation on the English version. Edit the Content item and publish it.
5. Go to the front page. The blog post will now display different content, depending on which SiteAccess you enter it from:
Add a design¶
The design engine enables you to use different themes consisting of templates and assets. Each theme is stored in a separate folder and assigned to a SiteAccess.
To create a new theme:
1. Add the following configuration at the bottom of
config/packages/ezplatform.yaml (at the same level as
1 2 3 4
2. In configuration of the
de SiteAccess (under
4. Go back to the
content_view configuration for the blog post. Change the path to the template so that it points to the folder for the correct design:
This means that the app will look for the
blog_post.html.twig file in a folder relevant for the SiteAccess:
de_design for the
de SiteAccess, or
site_design for other SiteAccesses in
5. Create a
themes folder under
templates, and two folders under it:
6. Move the existing
full\blog_post.html.twig file under
7. Copy it also under
de_design. Modify the second one in any way (for example, add some html), so you can preview the effect.
8. To see the difference between the different themes, compare what is displayed at
Set up permissions¶
To allow a group of users to edit only a specific Content Type (in this example, blog posts), you need to set up permissions for them.
Users and User Groups are assigned Roles. A Role can contain a number of Policies, which are rules that permit the user to perform a specific function. Policies can be additionally restricted by Limitations.
1. Go to Admin > Users. Create a new User Group (the same way you create regular Content). Call the group "Bloggers".
2. In the new group create a User. Remember their username and password. Mark the user as "Enabled".
3. Go to Admin > Roles. Create a new Role called "Blogger".
4. Add Policies that will allow the User to log in:
5. Now add Policies that will allow the User to create and publish content, limited to Blog Posts:
Content/Createwith Limitation for Content Type Blog Post
Content/Editwith Limitation for Content Type Blog Post
Content/Publishwith Limitation for Content Type Blog Post
6. In the Assignments tab assign the "Blogger" Role to the "Bloggers" group.
You can now log out and log in again as the new User. You will be able to create Blog Posts only.