How chaitanyap28/writeupctf works
Project type and purpose
• There are no backend services, databases, or dynamic code. All content is delivered as static HTML and markdown-based write-ups.
• The directory “WriteUps” holds the actual challenge solutions; “v1” and “v2” appear to be versioned snapshots or releases of the site’s frontend.
File structure
• Top-level files:
• CTFs.json – likely a metadata index for challenges.
• index.html – the current site entry point.
• v1/index.html, v2/index.html – historical versions.
• Logo – static asset (image or folder).
• README.md – project description.
• Directory “WriteUps”:
• Subdirectories per CTF event, each containing writeup.md (markdown) and any embedded assets (e.g., tmp1.pdf).
• There are no server configurations (no .env, no package.json, no build scripts). This is pure static content.
README for additional insights
• The README is minimal and simply names the project. No architectural details are provided.
• We deduce that content is maintained by hand and published as HTML.
Elements
• Clear labels:
• “User Browser”
• “Static File Hosting (CDN/Nginx)”
• “Git Repository (WriteUps + site files)”
• “Content Folder” and “Versioned Releases”
• User request → CDN → Serve HTML/CSS
• Git commit → (optional) CI/CD pipeline → CDN
• Yellow for actors (User, Contributor)