How employee451/postpost works
Project type and purpose
• This is a static-site codebase (“post-post.dk”) built with Telepater (a Deno-based static-site generator).
• It drives a content-rich site: pages are authored in “.vto” templates, augmented with small “.page.js” scripts, plus CSS, images, audio/video assets.
• Continuous build/deploy is handled by a GitHub Actions workflow (.github/workflows/telepater.yml).
File structure
– Top-level config & orchestrator
• _config.ts – main site configuration for Telepater
• _cms.ts – CMS plug-in or data hooks
• deno.json / deno.lock – Deno runtime & dependency locking
• .github/workflows/telepater.yml – CI/CD pipeline
– Source folder (src/)
• _data.yml – global site data (metadata, navigation)
• _components/ – low-level UI components (.vto snippets)
• _includes/ – reusable layouts, page templates, OG-image generators (.vto, .jsx)
• Content directories (kunstnere/, opslag/, musik/, videoer/, etc.) each with ._data.yml and per-item .vto files
• Page controllers: index.page.js, nyt.page.js
• Static assets: images in billeder/, audio in musik/, video in videoer/
– Output staging (implicit): Telepater compiles everything into a dist/ or similar folder (static HTML/CSS/JS).
README
• Confirms: “This is the code for our website – feel free to borrow!”
• No other architecture notes; structure must be inferred from files.
Main components & interactions
a. Components
• Telepater SSG engine (Deno process)
• Configuration layer (_config.ts, _cms.ts, deno.json)
• Global data sources (_data.yml, per-folder data)
• Template layer
– UI components (src/_components/*.vto)
– Layout includes & OG generators (src/_includes/*.vto, .jsx)
• Content layer (page templates .vto, page scripts .page.js)
• Asset library (images, audio, video)
• CI/CD pipeline (GitHub Actions)
• Deployment target (static-hosting service)
b. Relationships & data flow
1. GitHub Actions triggers Telepater build
2. Telepater reads site config + global data
3. It recursively loads content folders, applies templates & page scripts
4. Assets (images/audio/video) are copied or processed
5. Output: static HTML, CSS, JS bundles, plus optimized assets
6. Deployment step pushes output to hosting
c. Architectural patterns & principles
• Static Site Generator (SSG)
• Content-driven design: data YML + templates → pages
• Reusable component-based templating (single-responsibility .vto snippets)
• Build-time data injection (no runtime backend)
d. Key technologies & libraries
• Deno (runtime)
• Telepater (SSG)
• YAML for data
• Custom template engine (.vto) + JSX snippets for OG images
• JavaScript page controllers (.page.js)
• GitHub Actions for CI/CD
– Blue = configuration & data
– Green = templates & components
– Yellow = content files
– Orange = CI/CD workflow
– Gray = final output / hosting