github-pages-design

Topics in the source

• GitHub Pages: Design
• Stay inside the Pages boundary
• Read the relevant references
• Establish the visual direction
• Produce an implementable system
• Verify the result

Create a coherent, lightweight visual layer that supports repository content and survives static hosting constraints. Inspect the existing site stack, theme, CSS, assets, screenshots, logos, and documented branding before changing visual direction. Preserve a healthy framework-native theme and its accessible behavior. Prefer small token and component overrides over a replacement design system. Design for documentation, project explanation, code, tables, and navigation—not for an imaginary application dashboard. Keep remote fonts, trackers, scripts, and asset hosts out unless explicitly authorized and reviewed for privacy, reliability, and integrity. Treat exact colors, typefaces, and breakpoints as repository decisions. Do not copy illustrative values as universal requirements. Leave route generation, base-path configuration, framework migration, and deployment ownership with github-pages-create. If visual work exposes a defect in one of those areas, report and hand it off instead of silently changing it. Read references/pages-visual-contract.md before creating or materially changing the Pages visual system. Read references/design-direction-and-redesign.md before choosing a directi

This is an excerpt. Refer to the complete source and its current requirements.