# Project: [Project name, stated as an outcome]

> A project note for a PARA-organised knowledge system. In PARA, a
> *project* has a clear outcome and a deadline; it lives in Projects until
> it is done and then moves to Archive. Based on the PARA method
> (Projects, Areas, Resources, Archive) described by Tiago Forte, used here
> as a concept. Replace every `[bracketed]` value.

<!--
Guidance: How to use this template
- Name the project as a finished outcome ("Kitchen renovated", "Talk
  delivered at conference"), not an activity ("Kitchen", "Talk").
- If there is no deadline or no end state, it is an Area (ongoing
  responsibility), not a Project. Move it.
- Keep only what helps finish this project here; link to Resources for
  general reference material.
-->

| Field | Value |
|---|---|
| Outcome | [*Example:* Conference talk "Local-first apps" delivered and slides published] |
| Deadline | YYYY-MM-DD |
| Status | [Not started / Active / On hold / Done] |
| Area it serves | [[Area: Career]] |
| Started | YYYY-MM-DD |

## Outcome and definition of done

<!-- Guidance: What will be true when this project is finished? List checks you can tick. -->

The project is done when:

- [ ] [*Example:* Talk delivered on YYYY-MM-DD]
- [ ] [*Example:* Slides and recording linked on my website]
- [ ] [*Example:* Follow-up blog post published]

Why it matters: [*Example:* builds visibility for the open-source project and practises public speaking].

## Next actions

<!-- Guidance: Concrete, physical next steps that start with a verb. Keep the very next one at the top. -->

- [ ] [*Example:* Draft a 10-slide outline (45 min)]
- [ ] [*Example:* Email organisers to confirm AV setup]
- [ ] [*Example:* Rehearse with a timer and record it]
- [ ] [Next action]

## Milestones

| Milestone | Target date | Done |
|---|---|---|
| *Example:* Outline approved by organisers | YYYY-MM-DD | [ ] |
| *Example:* Full draft and demo working | YYYY-MM-DD | [ ] |
| *Example:* Two rehearsals completed | YYYY-MM-DD | [ ] |

## Resources

<!-- Guidance: Links to the notes, files and people this project needs. Reference material that outlives the project belongs in Resources and is linked here. -->

- [[Resource: Local-first software principles]]
- [Link to slide deck file]
- [Contact: organiser name, email]

## Notes and log

<!-- Guidance: Dated working notes, decisions and ideas. Short entries are fine. -->

- YYYY-MM-DD: [*Example:* Organisers prefer live demo; plan offline fallback video.]
- YYYY-MM-DD: [Note]

## Archive criteria

When the outcome checks above are ticked, or the project is cancelled:

1. Record a two-line summary of the result and one lesson learned below.
2. Move reusable material (slides, checklists) into Resources.
3. Set status to Done and move this note to Archive.

Result: [summary]. Lesson: [lesson].

## Standard and licence note

Based on the PARA method (Projects, Areas, Resources, Archive) by Tiago
Forte, referenced as a concept. This template is original text and is not
affiliated with or endorsed by the method's author. Template licence: MIT.