Ok, so I'm now in. Umm, it's not speedy
I think this will definitely be a case of divide and conquer or we will all waste a lot of time working on (and waiting for) the same thing. If there is a common interest in forum members producing a pseudo field repair manual I would be happy to contribute my time to assist. It would need some coordination like
@Logsplitter has suggested. Assign system-based tasks to a pool of users to produce topics then share them on the forum, that sort of thing. But this would benefit from a template to extract and populate the content into, especially given the different level of IT skills in our community. A template approach similar to what
@TheDocAUS posted a while back for developing installation guides would be smart and deliver a consistent result.
------------------
Looking at the slow page response rates I think the backend is just not scaled to cope with a moderate volume of concurrent users requesting content pages via a web GUI that sits on top of a database. As someone noted in another thread; if you go back to a previous page it fetches the content again instead of it being cached (stored temporarily) on your device. It seems to be trying to cache something though because it makes requests for more memory allocation. That's bizarre.
If you think this is frustrating for us owners trying to leach tech content imagine the impact we're having on the dealer and agent network trying to run a business!
I appreciate what IA have done here. We're now seeing a subset of what the dealers and agents see (I think our user profiles are heavily locked down). Given the circumstances and timeline I think IA had no other viable option to deliver something quickly and make good on the commitment. Clearly the docs library is not designed for this level of access and activity. Ironically, I saw similar delays watching over the shoulder of my agent recently so it's not all because the cheap seats have been given away to the unwashed (that's us).