Skip to content

Commit 804c186

Browse files
committed
Straighten headline levels in first-metamodel.
1 parent 21b4bce commit 804c186

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

manual/first-metamodel.rst

+17-17
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
The first MetaModel
2-
-------------------
2+
===================
33

44
Install with composer
5-
=====================
5+
---------------------
66

77
You’ll need the MetaModels core and some attributes / filter to get MetaModels running. In you composer search
88
``metamodels/core`` an ``metamodels/bundle_all`` to install the core and all bundles and filters.
@@ -12,10 +12,10 @@ When installed, run the database update and your MetaModels installation is done
1212
.. note:: If you know that you don’t need all attributes and/or filter you can install every single package by it’s own.
1313

1414
Your first MetaModel
15-
====================
15+
--------------------
1616

1717
Create MetaModels
18-
-----------------
18+
.................
1919
To get started with MetaModels we need at least one MetaModel, jai! We will build a small MetaModel, non translated,
2020
MetaModel for real estate references.
2121

@@ -29,7 +29,7 @@ In our example we need two MetaModels:
2929
Create reference and category metamodels.
3030

3131
Create attributes
32-
-----------------
32+
.................
3333

3434
An (empty) MetaModel is just a container for your data objects. But before you can store data in your MetaModel, you
3535
need to define some types of data which you like to store.
@@ -147,7 +147,7 @@ Choose:
147147
:Sorting: sorting
148148

149149
Create Rendersettings
150-
=====================
150+
.....................
151151

152152
For now, we have two MetaModel with some attributes and a link between booth. But we didn’t want just to store some
153153
data, we also like to display them.
@@ -192,7 +192,7 @@ The filter setting define the rules for the target, your detail page.
192192
:hide labels: yes
193193

194194
Create a rendersetting (backend)
195-
--------------------------------
195+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
196196

197197
Go to the „render settings“ of „reference“.
198198

@@ -203,7 +203,7 @@ Go to the „render settings“ of „reference“.
203203
.. note:: When you (later) add attributes to your MetaModel you need to add them also in your render setting.*
204204

205205
Create a rendersetting (frontend list)
206-
---------------------------------------
206+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
207207

208208
Go to the „render settings“ of „reference“.
209209

@@ -212,7 +212,7 @@ Go to the „render settings“ of „reference“.
212212
* After adding, activate „name“, „category“, „picture_highlight“
213213

214214
Create a rendersetting (frontend detail)
215-
----------------------------------------
215+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
216216

217217
Go to the „render settings“ of „reference“.
218218

@@ -221,7 +221,7 @@ Go to the „render settings“ of „reference“.
221221
* After adding, activate „name“, „description“, „category“, „picture_highlight“, „picture_gallery“
222222

223223
Input Screens
224-
=============
224+
.............
225225

226226
For now there are two MetaModels with some Attributes and Rendersetting. But how do we get data in our MetaModels?
227227
With input screens!
@@ -245,15 +245,15 @@ So create a Input Screen with the following settings:
245245
:Data manipulation permission: We want to allow editing, creating and deleting items - so choose all three.
246246

247247
Select configuration
248-
--------------------
248+
^^^^^^^^^^^^^^^^^^^^
249249

250250
Okay. Now we got the empty Input Screen container with a few settings. But to get things working, we need (remember
251251
the render setting!) some attributes in it.
252252

253253
Switch to the „settings“ of your currently created Input Screen and choose „add all“.
254254

255255
Define Attribute settings
256-
-------------------------
256+
^^^^^^^^^^^^^^^^^^^^^^^^^
257257

258258
Our input screen is ready. But we need tweak the attributes a little bit. For example we always want a name, description
259259
and Highlight Picture.
@@ -263,14 +263,14 @@ To get this done, we choose in these attribute settings the „mandatory“.
263263
.. info:: Input Screens are very powerful. Take a coffee and explore the visibility conditions and attribute settings.
264264

265265
Grouping and sorting settings
266-
-----------------------------
266+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
267267

268268
In the grouping & sorting section you need to create at least one object to sort & maybe group your entries.
269269

270270
For example: "Enable manual sorting" without grouping.
271271

272272
View conditions
273-
===============
273+
...............
274274

275275
View conditions are the easy part in MetaModels. But, you might guess that you also need here at least one to get things
276276
work.
@@ -281,7 +281,7 @@ The view conditions define who could see and use which render setting and input
281281
group“ blank.
282282

283283
Define a view condition
284-
-----------------------
284+
^^^^^^^^^^^^^^^^^^^^^^^
285285
Define one view condition with following settings:
286286

287287
:member-group: -leave this empty-
@@ -292,11 +292,11 @@ Define one view condition with following settings:
292292
.. info:: Wasn’t it a good Idea to prefix our input screens and render setting? ;-)
293293

294294
We are ready to enter Data
295-
--------------------------
295+
..........................
296296
Some time ago, we started with just a MetaModels package and already arrived to create data. Easy, hm?
297297

298298
Continue to the new „Referenz“ entry in your „content“ navigation and add a first item.
299299

300300
Filter Setting
301-
==============
301+
--------------
302302
(Todo)

0 commit comments

Comments
 (0)