-
Story
-
Resolution: Done
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Docu Sprint 65, Docu Sprint 66
-
5
Intro
My first translation was based on the content app which was the result of My first content app.
My first content app gets rewritten too, see DOCU-1676, using a more modern approach to create a content app.
The new My first translation should use the outcome of the new My first content app as a base to add a new translation.
Other things to change:
- No more screenshots from an IDE to show file structures. Instead use the tree command in the shell to create and render a tree.
Possible structure
- Installing a Magnolia bundle (with CLI)
- Adding an existing content app as light-module (the "books-app" from my 1st content app)
- Adding a new properties file for another language
and translating - Testing the translation
- Special stuff .. .?
Such as Icons (see old version), unsure whether that's required.
Steps 1 & 2 most probably will be used for a bunch of other tutorials.
That's why it would be very nice, if the installation part (bundle & light module) would go into an includable which is easy to reuse.
- depends upon
-
DOCU-1676 Rewrite "My first content app" tutorial
- Closed
- is depended upon by
-
DOCU-1710 Rewrite "Accessing content on the client side" tutorial
- Closed
-
DOCU-1711 Rewrite "Creating a website with Magnolia" tutorial
- Closed
- relates to
-
MGNLCT-84 Git clone operation may register app definition before ct definition and thus break the app
- Closed