Details
-
Story
-
Resolution: Outdated
-
Major
-
2.2
-
None
-
-
Empty show more show less
Description
The current inplace templating is very helpful for understanding how the site works, for debugging problems & for deploying hotfixes.
But the storage of the templates in the repository is not good for the maintainablity of long projects and is not a best practice.
At http://documentation.magnolia-cms.com/display/DOCS/Template+scripts it states:
"Editing template scripts in the repository is ideal for evaluation, prototyping or smaller projects. However, it is not maintainable in the long run. Don't do it in a production environment. We strongly recommend that you store the scripts in a version control system and package them into a project module."
This story is about coming up with a way that developers could easily edit content running on the live site (or author site for publication) in a maintainable way.
It would not even have to use the existing inplace templating, i'd like to look at the issue from a wider perspective.
But it would be great if it also supported the inplace templating because this is such a convenient light weight way for people to work with magnolia.
Different Thoughts:
- developers can use webdav to edit templates on file system of server.
- Developer edit files in git - tags in git can be depolyed to server.
- In place templating connects to files on the server instead of files in the repository.
- Repository of templates is somehow tied to git repository.