-
-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Hey,
We’re currently a bit stuck with how the layout-xxx.html.twig
file define the base 'structure' of the page.
Objective
The goal is to create a dashboard page with multiple rows and columns of with the same height.
Current state
Currently, the base template forces this HTML structure:
<div class="row row-cards">
<section id="" class="content">
[...]
</section>
</div>
TablerBundle/templates/layout-vertical.html.twig
Lines 120 to 128 in 39b5e29
<div class="{{ ''|tabler_container }}"> | |
<div class="row row-cards"> | |
{% block page_content_before %}{% endblock %} | |
<section id="{% block page_content_id %}{% endblock %}" class="{% block page_content_class %}content{% endblock %}"> | |
{% block page_content_start %}{{ include('@Tabler/includes/flash_messages.html.twig') }}{% endblock %} | |
{% block page_content %}{% endblock %} | |
{% block page_content_end %}{% endblock %} | |
</section> |
Render
Current render
Here's what we have currently:
Desired render:
To achieve this, we need to apply the .row-deck
class directly after the top-level .container
class.
But we want the .row-deck
in the top div + remove the section part.
Question/Solution
- Is there specific reason for having the
section
block + defaultrow row-cards
classes? - It may be a relic of
admin-lte
bundle?
It might be more flexible if this part of the structure was left for the developers to define, rather than enforced by the top-level template.
References with differents classes just after the .container
div:
https://preview.tabler.io/
https://preview.tabler.io/activity.html
https://preview.tabler.io/photogrid.html