CODE website developer guide
This guide explains the shared application behind CODE Magazine, CODE Group, CODE Staffing, and related sites. Start here when onboarding or deciding where to implement a change. The implementation was inspected on November 4, 2026; update the relevant topic with each behavior change rather than treating this as a frozen snapshot.
Read the guide
| Topic | What it explains |
|---|---|
| Getting started | SDK, configuration, running, and tests |
| Architecture and request flow | Project structure, startup, MVC, and service boundaries |
| Sites, routes, and navigation | Deployment modes, public URLs, JSON menus, and dynamic services |
| Presentation and content | Razor layout, styles, hero headers, content patterns, and reader UI |
| Feature map | Where to find magazine, events, consulting, staffing, and other features |
| Accounts and browser components | Authentication, My CODE, Vue, API calls, and antiforgery |
| Services, images, and caching | Thessaly integration, attachments, image conversion, and cache lifetimes |
| Metadata and discoverability | Sharing previews, canonical URLs, sitemap, and tracking |
| Verification and troubleshooting | Focused checks, operational limits, and diagnostic entry points |
| Maintaining this guide | Required update workflow, URL compatibility, and publishing |
Navigation and source conventions
Links between documentation topics use the explicit public slugs in docs/toc.json. For local reading, open the corresponding Markdown files under Docs / Developer in the root solution. Inline code paths are relative to the repository root. Each topic ends with direct Azure DevOps source-browser links; repository access is required.
The docs are source files, not a deployed documentation site. Lorekeeper hosting must serve topic routes, relative assets, and Mermaid diagrams. The existing article design specification includes desktop and mobile reference images; those are design references, not evidence of the current running UI.
For screenshots of the running 2027 application, see Presentation and content and the account password dialog. The images are stored in Developer/images and their captions record capture conditions and state.
Working principles
Keep one application with configuration-selected deployments and overlapping features. Reuse the shared controllers, views, helpers, styles, and service contracts. Preserve public routes and content anchors. Verify the active controller/view/import chain before editing a similarly named legacy file. Changes to shared views and scripts can affect every deployment and both style generations.