50 lines
1.7 KiB
Markdown
50 lines
1.7 KiB
Markdown
# AGENTS.md
|
|
|
|
## Project purpose
|
|
|
|
This repository contains the public website for the Napper application ecosystem.
|
|
|
|
The site includes:
|
|
|
|
- the main `napper.au` landing site;
|
|
- the Hudra product site;
|
|
- the Lildra product site;
|
|
- the Pendra product site;
|
|
- shared legal, privacy, support and ecosystem content.
|
|
|
|
## Source of truth
|
|
|
|
The repository is the source of truth, not individual conversations or AI sessions.
|
|
|
|
When an important architectural, deployment, naming or development decision is made:
|
|
|
|
1. update the appropriate repository documentation;
|
|
2. update this file when the guidance affects AI contributors;
|
|
3. avoid relying on undocumented conversational context.
|
|
|
|
## Working principles
|
|
|
|
- Keep the site simple and maintainable.
|
|
- Prefer conventional web technologies over unnecessary frameworks.
|
|
- Avoid dependencies unless they provide a clear benefit.
|
|
- Preserve accessibility, responsive design and fast page loads.
|
|
- Reuse shared styles and components where practical.
|
|
- Keep each application page focused on what the application does.
|
|
- Do not describe Hudra as a general-purpose editor.
|
|
- Treat Hudra primarily as a presentation and slide-viewing system for QLearn.
|
|
- Do not expose secrets, credentials or server-specific private data.
|
|
- Keep deployment configuration documented and reproducible.
|
|
|
|
## Expected workflow
|
|
|
|
1. Review existing documentation before changing architecture.
|
|
2. Make focused changes.
|
|
3. Test locally where possible.
|
|
4. Update documentation when behaviour or structure changes.
|
|
5. Commit using a clear, descriptive message.
|
|
|
|
## Project structure
|
|
|
|
The final structure will be documented after the existing website is imported and audited.
|
|
|
|
Do not invent a new architecture before inspecting the existing site. |