The core idea
A self-hosted workflow still needs a source model, retention rules, backups, and an owner for maintenance. Separate the public reading surface from private configuration and operational records. A cache can support retrieval efficiency, while an archive serves a deliberate preservation policy; do not assume they are the same system.
A workable starting pattern
Begin with a narrow collection and document what must survive. Keep portable records, version the vocabulary, and generate public files from the source. Test a clean restoration before relying on a backup. Review host behavior for nested directories and assets in the actual deployment environment.
The public site may contain article pages and a feed, while source credentials and import logs remain outside the web root. A restoration test should recover the relationships and labels, not just copy HTML files.
What this page does—and does not—offer
TagsFeed does not provide hosting, an installed feed reader, or a managed archive service. The guide describes operational choices for your own environment.
