Thread

Hmmm…. it’s kind of fun discovering this world of EE. But there is some discomfort, cause I never really get the big picture. As soon as I thought I understood something, a new feature comes up, irriting me, not knowing how to use it, how to build it into my site design, blurring again what I had just learned.

So, no comes Pages. Got to know about it here. And sounds great. But: a) I am not sure if I totally understand how to differentiate between dynamic and static content and b) I am working with the EE Core (where Pages is not part of).

My site won’t be one of these today-so-many-similar-to-blogs-sites (I love blogs!), but a “traditional” site, covering a scientific research project. So, I guess, once the site has been designed and content filled in, it will live on forerver without any major changes/inputs.

So, generally speaking, this is more of the “static” content. So, should I then use Pages (and invest 99$) (or some other way of including static content as mentioned “Static Pages” page), instead of the normal EE Entries?

Thanks for any advice.

Yes you have a couple options using static content in EE with the core version. First you could use the older page module which has been renamed Toam Mark Hout did an excellent job programing it. Simplify EE - Sorting Out Static Content (part 1) is a tutorial on how to use it.

Also Boyink posted a great tutorial on using static content without using a module. No-Module-Required Static Content in ExpressionEngine I have used both ways and they are both excellent.