einsteinsboi

Thanks Craig. I assume the admin side pagination supports lots of pages since quite a few people seem to have PW sites with huge numbers of pages. I will probably just want the url to be mothership/babyname, so shouldn't be too much of a problem I imagine WOW!! 100 000 pages!! That takes all my sorrows away

There won't be any search functionality as such. The pagination I refer to is in the admin backend side of things. Thanks Nik. That's very reassuring! What kind of hosting do you have these websites on? Thanks Kongondo. Yes I've read that. Definitely don't want multiple databases... that would be hell!! LOL. The whole point of this is to make maintenance as easy as possible, which is why I'm leaning towards option 1. Just wanted to know how scaleable it would be. Sounds though that PW can handle a site with tens of thousands of pages with no issue My next priority is to learn more about the PW user system since eventually this project will have a few admins and I'd like each admin to only be able to manage a particular set of pages and not be able to edit any of the others. Off to the docs I go. Thanks everyone for your replies Any more thoughts are of course more than welcome

So you think it will scale fine with thousands of pages? Does pagination stretch that far?

I'm getting to know Processwire relatively well, and now I have a nice big challenge ahead of me and I'm trying to lay out my plan of attack. One of my peers reckons I should use WordPress Multisite, which I know is definitely a viable option, but I would much prefer to use Processwire. I know it's not a question of "Is it possible?" It definitely is. It's just a question of "What's the better approach?" Here's the situation: I'm setting up a service that will build site pages for multiple clients (aka baby sites) but all under one domain (aka mothership). The baby sites will use folders, not subdomains. Most of the baby sites will be one page only, but some may stretch to three pages *gasp*. And of course each baby site will have a completely unique look - so there'll be as many templates as there are babies and potentially more templates than babies. The mothership will be its own site with its own pages discussing how to become a baby and the benefits of being a baby. So it will look something like this: mothership dot com - with about 4 of its own pages mothership dot com/baby1 mothership dot com/baby2 and so on up to about baby1000 (potentially) Now here's my thought process. NON NEGOTIABLE - Use Processwire NEGOTIABLE: 1. One PW site, each baby is just its own page with child pages where necessary 2. One PW core install, each baby is a separate PW site running from the same core wire. PROS and CONS of the two alternatives as I see them: Alternative 1: PROS - Really easy to install and just create the babies as pages on the main site tree. Easy to update core and modules/plugins CONS - Will it become difficult to maintain as the babies approach the thousands? Will it scale or will it crash? Will it become a future model of the dangers of putting all your eggs (or babies) in one basket? Alternative 2: PROS - Would be nice and easy to maintain from one core, since I only have to update just the one wire folder. Might scale easier since they're different sites, each with just a few pages. Any other advantages? CONS - Don't even know if this is doable? - Would I need to update each site's modules separately? Annoying Your thoughts and recommendations are much appreciated by the mothership and the many babies, and by me of course

Depends on what I'm working on and what phase I'm on in the project. Some of my best work for clients has been done to angry music... LOL

I can't work in silence either... I think I must be empty too!!

Another cool find thank you