You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-15Lines changed: 17 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,28 +16,18 @@ To present the data on the screen (i.e. website, RSS feed, etc.), you define ren
16
16
17
17
Filtering data in list views needs configuration of filter settings. Filter settings are a very complex topic, as they can be nested (AND/OR conditions i.e.) and be of various nature.
18
18
19
-
History
20
-
------------------
21
-
Metamodels are the replacement for the famous Catalog extension for [Contao CMS](https://github.com/contao/core).
22
-
23
-
As the catalog extension was growing too complex too maintain and most support for extendability was rather hacky, we decided it was time to take everything we learned during the development of Catalog 1 and Catalog 2 to provide you with Catalog 3 which shall be even more flexible and very easy to extend with own classes.
24
-
25
-
As development did go on nicely, we realized that an easy migration from Catalog to the new version will not very likely be possible both in implementation and learning curve but that this will be a very own and unique extension reensembling only of the name with it's ancestor.
26
-
Therefore we rebranded everything as "MetaModels".
27
-
28
19
How to use it.
29
20
--------------
30
21
31
22
### Composer
32
23
33
24
MetaModels and all its dependencies are available through the great [composer extension](https://c-c-a.org/ueber-composer)
34
25
35
-
When your Contao Installation is composered, you can simply installing metamodels by adding following packages
26
+
When your Contao Installation is composered, you can simply installing MetaModels by adding following package
36
27
37
-
* MetaModels/core
38
28
* MetaModels/bundle_all
39
29
40
-
If you do not need all attributes & filters, feel free to just install the core and grab some filter and attributes of your choice. (Or another [bundle](https://github.com/MetaModels?query=bundle)
30
+
If you do not need all attributes & filters, feel free to just install the core (MetaModels/core) and grab some filter and attributes of your choice. (Or another [bundle](https://github.com/MetaModels?query=bundle))
41
31
42
32
### Nightly
43
33
@@ -49,15 +39,27 @@ Docs:
49
39
-----------
50
40
51
41
*[The official MetaModel Documentation (en)](http://metamodels.readthedocs.org/en/latest/index.html)
52
-
*[The official MetaModel Documentation - feel free to contribute!](https://github.com/MetaModels/docs)
42
+
*[The official MetaModel Documentation (de)](http://metamodels.readthedocs.org/de/latest/index.html)
43
+
44
+
Feel free to contribute the MetaModel Documentation in [EN](https://github.com/MetaModels/docs) or [DE](https://github.com/MetaModels/docs-de)
*[MetaModels Contao Community Subforum](https://community.contao.org/de/forumdisplay.php?149-MetaModels)
49
+
*[MetaModels Website](https://now.metamodel.me)
50
+
*[MetaModels Contao Wiki [DE]](http://de.contaowiki.org/MetaModels)
51
+
*[MetaModels Contao Community Subforum [DE]](https://community.contao.org/de/forumdisplay.php?149-MetaModels)
59
52
*[MetaModels IRC Channel on freenode #contao.mm](irc://chat.freenode.net/#contao.mm)
60
53
54
+
History
55
+
------------------
56
+
Metamodels are the replacement for the famous Catalog extension for [Contao CMS](https://github.com/contao/core).
57
+
58
+
As the catalog extension was growing too complex too maintain and most support for extendability was rather hacky, we decided it was time to take everything we learned during the development of Catalog 1 and Catalog 2 to provide you with Catalog 3 which shall be even more flexible and very easy to extend with own classes.
59
+
60
+
As development did go on nicely, we realized that an easy migration from Catalog to the new version will not very likely be possible both in implementation and learning curve but that this will be a very own and unique extension reensembling only of the name with it's ancestor.
61
+
Therefore we rebranded everything as "MetaModels".
0 commit comments