A long time ago had - left over code - nodes? when I deleted a menu 300-400 of them
On my little sites 3-9 pages no big deal
My big 100+ page site has never been the same since…
Little things that bug me… images randomly disappear - mobile menu doesn’t quite work after nuke and pave etc (see below)
I’m not adverse to starting the website over.
How does one do that? Copy resources folders
Copy old containers over? No?
Should I start fresh from scratch?
Will it solve my problems?
How big are your sites?
What do you think?
Has this happened to you?
Looking for guidance and advice…
(The hundreds ‘nodes’ took shape above the menu as blank svg or other code - my thinking 
is the top code around my menus is corrupted from the nodes - hence the current menu problem now… - so the following containers should be error free?)
These are all guesses from my experience and intuition…
From Gemini:
Your intuition is entirely correct. When a project file suffers a massive structural failure—especially 300–400 orphaned nodes exploding around a critical global element like a navigation menu—the underlying code structure of the project gets mangled. Even after the software attempts to clear those recovered nodes, phantom code, broken XML tags, or corrupted references often remain.
This ghost code is exactly what causes erratic, seemingly disconnected behavior like randomly disappearing images and broken mobile triggers. For a massive 100+ page site that serves as the central hub for your method books and audio files, limping along with a corrupted project file is a major liability.
Here is a breakdown of your questions and the most secure strategy for a rebuild:
Should you start fresh from scratch?
Yes. For a site of this size and importance, a clean foundation is the only way to guarantee long-term stability. Patching a deeply corrupted file usually leads to more hours of frustrating, endless troubleshooting down the road. A “nuke and pave” will absolutely solve the underlying project file corruption.
How to migrate safely (What to copy and what to leave behind)
The goal is to move your content without carrying the “infection” over to the new file.
-
The “Infected” Zone (Do Not Copy): Absolutely do not copy the menu, the header, or any top-level structural containers from the old project. Rebuild your global navigation and header areas completely from scratch in the new file.
-
The Content Containers (Proceed with Caution): Your intuition that the lower containers might be error-free is logical. You can try copying the main body containers (the text and image grids) from the old pages to the new ones. However, test this thoroughly on just one or two pages first. If the new file starts acting sluggish or buggy, abandon this method.
-
Resources (Safe): Do not copy the old resource folder directly over. Instead, re-import your definitive, high-resolution book covers, audio tracks, and PDFs fresh into the new project’s resource manager.
-
Text (Safe): Copying and pasting raw text into newly built containers is the most bulletproof, albeit tedious, method.
So - a restart is in order…
So silly question 
is now the time to restart?
Or wait till some point in the future?
Don’t really want to do this again…
Thoughts?
