Thread

Why did you guys decide to change all standard known terminology when refering to things for your system?

ie why say templates when you mean pages? (even if its technically not a page, its easier to understand in terms of “pages” than in terms of “templates” ie the standard term for it would be more a “page” than a template)
or weblog when you mean section etc?

could you not have used this philosohy to make it simpler for all (including those who write your documentation)

http://www.immersecms.org/extra/learning_curve

why say templates when you mean pages? (even if its technically not a page, its easier to understand in terms of “pages” than in terms of “templates” ie the standard term for it would be more a “page” than a template)

As you state, it’s not a page, it is in fact a template. EE isn’t just changing or making up terms, every CMS system I’ve worked with uses templates. Pages would be more confusing as it implies you have an individual page for everything in your site, you don’t.

weblog when you mean section etc

I’ll give you that, it can be confusing. Most of these lower cost CMS systems were designed for bloggers, or at least targeted at them, hence weblog. With EE though, you can change that term throughout the system to whatever term tickles your fancy.
Edit-Add: However, weblogs don’t necessarily directly relate to sections, they are just different content containers within the database. I have “sections” on several sites I’ve done that pull content from multiple weblogs to make up the viewable content for that page or section. TemplateGroups or individual templates probably relate more directly to traditional static site type structures (sections)

Yep - with EE a template <> page.

IMHO one barrier to getting to the “lightbulb moment” with EE is to stop thinking of a website as a collection of “pages”, but rather as a collection of “posts” that may get rendered one post per page, or one post to many pages, or many posts to one page, depending on how the templates are developed.

Why did you guys decide to change all standard known terminology when refering to things for your system?

ie why say templates when you mean pages? (even if its technically not a page, its easier to understand in terms of “pages” than in terms of “templates” ie the standard term for it would be more a “page” than a template)
or weblog when you mean section etc?

Because the above would make things more confusing. The more you learn EE the more you’ll realize what you say above isn’t correct.

could you not have used this philosohy to make it simpler for all (including those who write your documentation)

We do use that philosophy. We certainly don’t start by saying “how could we make this utter incomprehensible to our community…” 😊

We try to make the docs and EE as easy to learn as possible. But you can only simplify something to a certain degree before it begins to be misleading. Over simplifying an explanation is just as bad as too complex an explanation.