Thread

I want to start a new website with ±200 different “statics” pages and I want to use the add-on NavEE en the Page module.

I read on the user guide from EE this”:

If you’ve created more than 10 pages, carefully consider your other options before adding more pages because there’s probably a much better way to do what you want to do.

Bij “statics” pages I mean no: read more - no detail page. Just Titel and a long text and an image.
Do you have some experience with site having a lot of “pages” made with the Page module.

Francois

Why do they have to be handled as static pages?

My english is quite poor, maybe is statics not the correct word.

It will be ±200 pages, who has to be made by my client, but this pages are just information pages, not like a news page with a read more or a blog. No comments will be had to this pages.

Maybe sometime my client will have to make some changes in the text or place a different image, that it.

How do you name such pages?

Francois

I don’t think you need the Pages module.  Possibly not even NavEE.

The fact that this content won’t have read mores or comments doesn’t change the way you can manage it in ExpressionEngine.

If the content is all the same type / structure, just create a channel for it with the necessary fields. Each “page” as it comes out on the front end will just be an entry in the channel. Your client will edit them in the channel as an entry.

Quite likely that EE can build the navigation to the entries dynamically - depending on how the 200 entries are presented on the front end (are they categorized, etc).

The only real reason to use the Pages Module is if there are specific URL requirements for each page that the normal EE URL structures don’t match (landing pages, etc).

Some more on the Pages Module:
http://www.train-ee.com/courseware/free-tutorials/comments/pages-module-1-an-introduction-and-history

Static Content
http://www.train-ee.com/courseware/free-tutorials/comments/static-content-inconcievable

I will need specific URL. the navigation will have 4 levels.
I normally always work with the add-on “structure” but because now it is a site with a lot of pages (for what I’m use to) I’m afraid “structure” won’t be able to do it.

What’s the URL structure?

There is also now template routing that may be able to help with the URLs.

site_url/level1 URL Title/level2 URL Title/level3 URL Title/level4 URL Title

But what are the contents of url levels 1-3? Are they categories or other lower-level containers?  How many different values will be at those levels?

The challenge with the Pages module is that you have to define the entire URL manually - so there will be lots of room for error.

There are other ways to run EE more dynamically that might be more efficient.

It will be a site like this one:
http://www.voordejeugd.nl/

except for Actueel (this are dynamic page with read more…)

Sorry…I might have been born in Holland (MI, USA) but I can’t read Dutch…tough for me to tell what’s going on there.

It is in Dutch but I send this example for the structure of the URL, that what you asked for or not?

It’s an answer, but not a direct one..😉

I’d rather not have to explore the site to find all the URL variants as that can be time-consuming.

Each page has a Title and a URL Title and in the URL I want to see the URL Titel, not the template-group/url_titel.

If I have:
-home
-information
—about me
—about my dog
—about my car
-what I like
—as food
—as country
—as city

If I am on the page “about my dog” I want the URL to be:
site_url/information/about-my-dog

If your template group was named ‘information’ you could use the index template to achieve that URL.

I also though of this solution.