[DOCU-280] Best Practice Guide: Developing with Magnolia CMS Created: 28/May/12  Updated: 25/Apr/17  Resolved: 25/Apr/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Lauri Assignee: Unassigned
Resolution: Done Votes: 0
Labels: documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-675 Create a tips & tricks page for diffe... Closed

 Description   

Magnolia is quite complex and feature reach framework with mutliple ways of deployment. Steepness of learning curve much depend on the way you pick to go. Personally when I got basics covered it is still hard to quickly work with because my current setup require redeployment after each change which delays development cycle a lot (not to mention its boring).

Idea: publish best practice(s) of magnolia usage for newbies and advanced users. Covering simple and obvious areas like:

  • IDE setup
  • bundled or mavenized
  • .jsp or freemarker.
  • module or .war
  • blossom or bootstrap
    etc

For now I think i know the best way to develop .jsp templates - to go for mavenized magnolia + netbeans IDE. It would allow to update .jsp and see immediate result in your browser, still haveing IDE to edit the templates.

Community member runger has other preferences: http://forum.magnolia-cms.com/forum/thread.html?threadId=69ea1310-8a60-4f43-a32d-ad8d6d62511f&page=1


Generated at Mon Feb 12 01:07:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.