What to use 'Widgets' or Layouts etc.?
Hi All, I’ve been erring on the decision of whether or not to use Orchard on a project as I’m struggling to separate what can and can’t be done, and more importantly, with what? Looking up tutorials and documentation, I’m not sure if I’m really dense, or if there is a lot of misinformation/deprecated literature; my main point of confusion is with widgets and layouts / elements / blueprints / templates etc., and when to use what type? So, I thought I’d propose a simple situation and have you helpful folk tell me if I’m on the right track ;) I’ll have six pages of content, which I assume will be straight forward to implement, though I wish to reuse all those six pages content into one page [let’s ignore SEO for now] – and using that pages name/type as a conditional marker – reduce the amount of content [some elements like image sliders etc.] that is displayed for each section; basically, becoming a synopsis of each. Am I right in assuming Layouts is the key for this scenario, along with ‘I think’, Element Rules? My concern is what to use [as some old widget literature seemed to fit the bill as well]. So assuming Layouts is what I’m after, what should I use as these reusable containers [ignoring the overall sites template which I believe I can create/override via document/Layout.cshtml] – the six pages will have some common wrappers etc. [so some sort of template], but the content will need to be altered for each by the user – so then some way to make the template editable on each page’s layout as well as reusable/automatically updating on other pages [namely the synopsis page] that use this 'element'? Is this possible and can anyone clear up my understanding/terminology if needed. Thank you very much for your time, PP