Doctor Tyrell

There seems to be a paradigm religion for / (home) page templates / pages. I've created an unpublished page that is a dup of the Home page, and now the "contexts" don't work, so I'm looking at a page full of errors. Twig isn't the problem at all. I've done my best to config the sub-Home page like the main Home page, but the settings don't seem to match due to the paradigm of how the platform handles a root level page. Is that correct? Having built a few platforms in my days, I understand the need to force use cases to save time. My client has been held hostage by a previous group and is in desperate need to get this Processwire site updated. The server database is still not accessible, so I'm unable to grab a copy and open up an alternative website. There are so many modules turned on that don't appear to be being used, I'm cautious about being a new PW developer and trying to simulate what WordPress could bang out in an evening. I'm running 3.0.42. The tutorials seem to be using a previous interface. I guess a general question might be: How does one overhaul an existing PW site without installing a dup?

I'm working on my first ProcessWire website and so far I really like the UI. However, I need to create a page that isn't viewable by the outside public to test new code. I should mention that the previous developer used the TWIG module, so that makes following the tutorials a bit different. I've created a template that matches the previous home page, but I'm unable to add the section title / path. The UI just doesn't have anything available. When I go to the Pages "Add New" (running the latest Processwire) I only get the "Bookmark" option. What's the trick with this?