Making the Work Behind 413 News Easier to See

What sits behind a website?

What software is running a website? What does it depend on? And what evidence is there that it could be recovered if something went wrong?

Those questions are guiding the work on my internal app management tools at IglesiasTech. The goal is to make the answers easier to find, without reconstructing them from separate documents each time. We chose 413 News (opens in a new tab) as the first example for bringing software and recovery information together.

I’m building these tools to help me maintain my own sites. The progress is in the management view: it now brings together recorded software details, comparisons with official releases, historical recovery information and the gaps still needing attention.

Starting with questions, not a green light

413 News: the public-facing site that these internal tools help me understand and maintain. Screenshot captured September 29, 2026.

The software view covers the website, the system used to manage its content, the news scraper and the database. Each recorded version stays connected to the component that was checked and when it was observed. That timing matters because this is a collected snapshot, rather than a continuously refreshed view.

One useful distinction is between finding a newer release and deciding to install it. The checks found newer versions of the software, but compatibility had not been tested. No upgrades were carried out as part of this collection work.

The view therefore gives me that comparison without turning it into an upgrade recommendation. Checking whether those releases fit the existing setup remains a separate piece of work.

A backup record needs context

The evidence summary for 413 News in my internal tools. Captured from an isolated copy of the real interface using the saved September 29 observations; this is not live monitoring.

Recovery information raises a similar question: what does the evidence actually cover?

The view brings in historical backup and restore records, while keeping them separate from the latest measurement of the stored package. That package is shared with other sites, so its total size cannot be read as the amount of backup data belonging to 413 News alone.

The history also includes gaps, such as references to media that were already missing. Those limits belong alongside the recovery information. A past restore check and an established recurring backup routine are different things; the latter was not established by this collection.

The wider plan calls for backup schedules, retention and run history to become visible too. For this first version, those are still unanswered parts of the picture.

Making the next questions easier to ask

This version has been deployed and is ready for me to try. Collecting the evidence still takes a person starting the process. Refreshing it from the browser, collecting it continuously and adding broader software and security coverage remain work to do.

My larger aim is a management view where I can understand an app, follow its changes and see where more investigation is needed. The 413 News example is one step toward that aim, with a deliberately limited scope.

For now, the meaningful change is bringing the recorded software and recovery information into the app’s own view. It gives those questions a place to start, while leaving the unanswered ones visible.

Have questions about this work or a project of your own? Get in touch.