Thread

I am coming from a different CMS that allowed me to build “templates” and then include in the templates tags where content will be placed. With such a system, I could then build new pages based on the templates and my information would automatically show up where it was supposed to be. Simple concept. Build a page and base it on a certain template. If I develop a new look, I can then just use a different template.

With EE, it seems very different and I am having a hard time understanding. I realize I can create a “template” and add tags to that template which tells it where content is to go and which content to use. However, it seems that for every page I want in my site, I will need a new template. So if I were to change the look of my site, I would have to modify every single template instead of just one.

This can’t be the case so can somebody please explain where my thinking is wrong. Thanks!

EE is very similar, build a template, place tags. The number of templates you need is totally dependent on your site, its content, and the functionality you need/want. It’s even possible to build an entire site through one template even though it’s not really recommended.
Without more details on your site, it’s hard to get specific though.

PXLated is right- it’s hard to be specific w/out seeing what you’re up to.  But the key thing to remember is that EE is dynamic- the content displayed can use the same template but display different data based on the url.  So- you put a weblog tag on ‘site/index’ then mysite.com/index.php/site/index will show all entries (assuming the parameters of the tag allow that), mysite.com/index.php/site/index/C5 will show all entries in category 5, mysite.com/index.php/site/index/first_entry will show only the single entry with the url title of ‘first_entry’.  Same template- but different data.

Of course- I tend to use a dedicated template for my default, a template for multiple entry display and then a different template for single entry display.  But that is largely a matter of personal preference.

What I’d suggest doing to get the hang of the logic?  Read the Getting started guide and work through the tutorial there.  The video tutorials are also a good idea, as is Boyink’s tutorial.  Also, read over the section on embeds- many folks make use of those for shared navigation, headers, footers etc.  The provide another nice way to reduce maintenance/setup time.  After that?  It should start coming together for you.

Great info, thanks. I appreciate the quick repliese. It’s starting to make sense to me now.