Yeah, I agree with Simon. Also it depends on your or your teams skills and 
preferences. 
In general, and especially for people new to Magnolia - I would recommend 
1. creating a slim HTML website first that has one example of each of the page 
types and components that you intend to use on your site. This is what we refer 
to as the "static HTML prototype". 
2. Use this to create Magnolia page templates, component templates & dialogs 
where necessary - (Or using existing MTE components that match your needs - 
https://documentation.magnolia-cms.com/display/DOCS/MTE+module)
2b. Consider using Content Apps to store "structured data" such as "products", 
"cars", "schools", and components to display these things in your website. Its 
an option. (If setting up content apps appears too complicated - you could 
always skip it for now and store all your content in pages.)
3. Now you can build out your page tree in Magnolia.
4. Now you can enter your content in Magnolia.

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=b7cb3c2b-a519-4f47-96d3-4bd66a9e740a


----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to