Markus GrafandClaude
d36a18d28b
Initialize minimal Hugo site structure with Bootstrap 5.3.2 integration for markusgraf.ch conversion. Implements OpenSpec proposal add-minimal-hugo-site. Features: - Hugo project structure with standard directories - Base layout template (baseof.html) with Bootstrap 5.3.2 via CDN - Homepage (index.html) and single page (single.html) templates - Reusable partials: header, footer, navigation - Responsive Bootstrap grid layout - Mobile-first design with semantic HTML5 - Valid HTML output with basic accessibility features - Taxonomies disabled for minimal site (see docs/TAXONOMIES.md) Documentation: - IMPLEMENTATION_SUMMARY.md - Complete implementation guide - docs/TAXONOMIES.md - Guide for re-enabling categories/tags - static/README.md - Guide for placing static assets Configuration: - hugo.toml configured for markusgraf.ch - .gitignore for Hugo build artifacts All 24 tasks from OpenSpec proposal completed successfully. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
---
|
|
name: OpenSpec: Apply
|
|
description: Implement an approved OpenSpec change and keep tasks in sync.
|
|
category: OpenSpec
|
|
tags: [openspec, apply]
|
|
---
|
|
<!-- OPENSPEC:START -->
|
|
**Guardrails**
|
|
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
|
|
- Keep changes tightly scoped to the requested outcome.
|
|
- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
|
|
|
|
**Steps**
|
|
Track these steps as TODOs and complete them one by one.
|
|
1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
|
|
2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
|
|
3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
|
|
4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
|
|
5. Reference `openspec list` or `openspec show <item>` when additional context is required.
|
|
|
|
**Reference**
|
|
- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
|
|
<!-- OPENSPEC:END -->
|