Something that would be nice is an easier way to handle multisites. Something that could be useful is a sort of namespacing for databases. The default namespace would be just like normal allowing backwards compatability. However something like
// Render your multisite’s primary navigation
pages()->namespace('website2')->get('/')->children->each('<li><a href={url}>{title}</a>');
would be huge. This would allow easy access to the primary database for configurations or anything needed there as well as possibly allowing to set permissions for users to just access to their namespaced database.
The namespacing I'd think could happen one of two ways, one would be table prefixing, the other would be creating a whole new database.
Another advantage of creating a whole new database would be that it would allow us to create a processwire instance in one database, but also have completely custom data in another database that is easily accessed would be nice.
Another thing that is on my wishlist for processwire 4.0 would be sqlite. For me, processwire is a beautiful CMS / CMF because as a developer, if I can adjust my projects around processwire, it becomes a low code tool, great for prototyping. Sqlite would allow me to bring up a processwire instance, create to my hearts content. Then just push this whole new project live. I would think that this would require an additional $db abstraction. It would definitely be harder to make this backwards compatible. Maybe making this some sort of opt in with disclaimers everywhere saying that this breaks backward compatability with 3.0.
