Browser code should own interaction, not the content source. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
When important text and links exist only inside client scripts, the page becomes harder to crawl, test, and maintain.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
Deliver complete HTML first. Use small scripts for filtering, menus, playback, and state that genuinely belongs in the browser.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.