Leaderboard

May I recommend two very valuable articles from A list apart? http://alistapart.com/article/pricing-strategy-for-creatives http://alistapart.com/column/pricing-the-web

45mb is too huge. for ace to work you only need https://github.com/ajaxorg/ace-builds/blob/master/src/ace.js which 625kb (337 when minified) and a few modes that are loaded on demand.

Now it is possible to uninstall the PageLinkAbstractor" (if using PW 2.6 and newer, this is a good idea) without ending with broken internal links. Please follow those hints on GitHub - there is a useful code snippet by Ryan Cramer: https://github.com/ryancramerdesign/ProcessWire/issues/1283 In my cases the provided script did not catch every single link, but most of them - the few remaining could be searched for with a 404 Link Checker Tool and then repaired manually.

Create a Settings page and add these fields to it.

I think this is your limiting factor here. I have built something similar as part of a wider, integrated intranet system however if your time is short you can't beat using some pre-existing software. Nothing will beat ProcessWire if you are likely to want to introduce functionality not available in some other system as ProcessWire is one of the few platforms where you can change your mind about something or come up with crazy new ideas and it not be a problem to make larger changes, but if you're likely to only need a normal WIKI type system then you probably won't replicate all the functionality you want in just a few weeks. That said, I hate that MediaWiki seems to be the main option out there (there are others, but they all come with their own maintenance issues too) as it's a bloated piece of software (so slow and resource hungry for what it does) on an out of date codebase in my opinion. I would love to have the time and money to develop something in PW as coupled with ProCache you'd be onto a winner and have something infinitely more customisable if a lot simpler, but it would be a project that would take several months at least I would think to cover everything (well, the basics) of what something like MediaWiki can do. Not sure where my train of thought is going, but I guess if you're really tight on time, you should probably invest that in installing, skinning and getting to grips with something that already exists. If the project is longer-term overall (as in you'll be looking after this system for years), then this buys you time to develop something as a version 2 and does you a favour in a way as you'll know what the client does and doesn't use in the system you've installed so you know where to focus your efforts in a custom-built system. Hope that's of some help anyway.

I have done something like this half a year ago. I made an intranet for a company with 200 employees. There are no problems I heard of so far. It has a full text search, a searchable image repository with thousands of photos, every user has his own profile with his portrait... Most important thing was: every download of this intranet (PDF, Word, Excel, image files and so on...) is a page. I have build a small multi file importer which allows to upload many files at once, which leads to creation of the according amount of pages with these files attached. I did this to give each file more properties (think of it as an" asset management" - every file can have properties like view rights, tags, relations, descriptions, authors etc.). To assign this download pages to their parent "content pages" (the page the visitor sees in frontend view) I did use page tables very much. I think it works very good and I enjoyed it to develop and customize.

It's always as a project gets big you'll have to take care. No matter what CMS. In case of images: a. you can now in 2.6 delete variations for a image right in the backend. But that doesn't work for batch processing a whole site's images. b. you can write a script to delete all variations through API, but that as soon as there's 1000's of pages involved you have to take care of memory, script time etc. Bit this if you own ListerPro (which I recommend all PW users should buy anyway) you can use and build an custom action that batches all your pages (or the ones you filtered) to remove variations. It's built with scalability in mind so it scales for millions of pages (just would take a very long time). c. you can also use the API when using $page->image->removeVariations() to delete and force new generation of variations. Then use a template var to toggle that globally in your template. Usually a custom $config var would be best as it allows also modules to read it. This works fine when building a site and you want to experiment to get the best options. Maybe not always suited but something like: $config->forceNewVariation = true; The always use a code like this where you generate thumbs or sizes. $img = $page->image; if($config->forceNewVariations) $img->removeVariations(); $img = $img->size(100, 100, $options); Of course this doesn't work well if you're live and have 1000 of pages. As you'd have to view all pages again to trigger new creation WHILE the setting is true. Just a few ideas.