Spec: Project overall system
This project is a reusable CV website template and a central reference project for product, architecture, delivery, and operations work.
What it is
- a product and reference system around a CV website on shared hosting
- a project made of app, config spec, public docs, work framework, and recurring flows
- a public project surface that explains project purpose, system boundaries, and flows
What it is not
- not only a docs or Jira project
- not a single repository
- not a showcase without real delivery, operations, and quality logic
Why
- the website template should be practical and reusable
- the project should document how product, architecture, and delivery work fit together in one continuous example
- the public docs should make systems, flows, and decisions legible
Structure
- app system
- pipeline spec system
- docs system
- Jira system
- GitHub and PR system
tagebuch- AI/skill framework
atlassian-tools
Readers and usage
- organisational readers find project purpose, boundaries, and key flows
- technical readers find system shape, interfaces, and operations model
- implementation-focused readers find repos, rules, work docs, and evidence
Interfaces
- public site via GitHub Pages
- app code and PRs on GitHub
- Jira as the non-public work source with a public docs trace
tagebuchas raw provenance
Current state and target picture
- Current state:
- project identity is spread across several pages and repos
- Target picture:
- a clear project map under
specs/
- a clear project map under
Parent systems
- no higher project system inside this docs layer
Child systems
- App system
- Pipeline spec system
- Docs system
- Jira system
- GitHub and PR system
tagebuch- AI/skill framework
atlassian-tools
Related systems
Sources
- Start page
- Getting started / quickstart
- AI project map
lebenslauf-web-vorlage/README.mdpipeline-config-spec-php/README.de.md