TechPrognoza
Moving years of static content into a real application without losing any of it.
- Type
- Product
- Industry
- Content / media
- Platform
- Web application
- Role
- Design, build, deploy
What made this hard.
A technology and gaming publication (reviews, news, a wiki section, taxonomies and a full archive) that started life as a Hugo static site and now runs as a Django application with Markdown stored in the database.
Hugo was the right first answer: Markdown authoring, instant builds, near-zero hosting cost. What it couldn't grow into was anything interactive - forms, per-visitor behaviour, editorial workflow, without bolting on a second system.
Migrating meant the content had to survive perfectly. Years of articles carried front matter and custom shortcodes; losing a review box or a taxonomy would have meant re-editing hundreds of pages by hand.
What we built.
- Wrote an importer that reads the original front matter and shortcodes directly, so the existing archive carried over losslessly into Markdown-in-the-database, served by Gunicorn behind Apache.
- Rebuilt the CSS as a layered, numbered architecture: primitives and semantic tokens first, then typography, base, an extracted component library, and section rules. A bridge layer re-points the inherited theme's variables onto the semantic tokens, so a palette change touches exactly one file.
- Emitted a per-section accent colour from the route path, so gaming, tech and wiki areas read as visually distinct from one page-level rule instead of per-page overrides.
- Unified the editorial shortcodes (review info boxes, wiki infoboxes, lore quotes, tip and info boxes) onto one visual system rather than inline styles.
- Self-hosted variable fonts on a modular type scale, and added focus-visible rings across menus, buttons, pagination and cards.
- Built the article page around onward reading: hero context cards, related-post selection with a same-section fallback, and a custom share panel using the Web Share API with a copy-link fallback.
What it runs on.
Chosen to be maintainable for years, not to win an argument on the internet.
- Python
- Django
- Gunicorn
- Apache
- Markdown
- PostgreSQL
- Web Share API
- reCAPTCHA v3
Where it landed.
Added a browser-native text-to-speech article reader, URL aliases for the old Hugo paths, and an llms.txt so AI crawlers get a clean map of the site.
The migration is the transferable part: an importer that understands the old format is almost always cheaper than a content team re-typing the archive.
Need something in this territory? This is Django development work. Start from all services or see pricing.
Related case studies.
Your project
Tell us what you're building. We reply within two business days.