[MGNLINTEMPL-56] As a developer I can edit the templates of a live website in a sustainable best-practice manner without deploying a new war Created: 04/Dec/13  Updated: 20/Dec/18  Resolved: 20/Dec/18

Status: Closed
Project: Magnolia In-place templating Module (closed)
Component/s: template editor, template loader
Affects Version/s: 2.2
Fix Version/s: Ideas

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty

 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.

Generated at Mon Feb 12 05:58:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.