Some pages are incompletely renderred

We have a problem with pages with too many expensive parser function calls.

One more reason to convert those pages to use the content translation feature of the Translate extension... but we desperately need some thought on what we need and want to say, and about which things. It just doesn't make sense to just convert the pages as they are now.

How about collecting all pages that may need reworking, updating, deletion, being moved or replaced into a category so that existing information is kept, and creating a structured collection of the topics that we want to say something about in a sitemap type of page? It would be giving a structure, can spur discussion, and finally become a guide for writers, translators and readers of contents.

Currently, I see as pages to be considered the "Main page", the pages linked to from there, the pages linked to from "Template:ProcessNavigation", and each page "Translating:some-product-name" (plus likely some linked to from them such as "Plural", "Gender" and "Grammar"), then: "CLDR", "Project:General_disclaimer", "Project:About", "Project:Privacy_policy", "Support", "Project:News", "Project:Offline", "Fuzzy", Translating:Why use translatewiki.net.

Also, I suggest to tag explanatory and supportive pages (such as "Plural") with the products, that they apply to - maybe even do negative tagging as well - for instance putting a common icon bar in each of those pages, where non-applicable ones are both grayed and X-ed out.

How about marking and categorizing some pages as outdated, such as Project:Server admin log?