Architecture: boundaries and responsibilities
Assign rule and data ownership before choosing module boundaries.
Open field noteTHE FIELD GUIDES
Project planning.
Practical walkthroughs for learning project planning through examples of behavior, structure, and constraints.
Search within: Project planning
9 field notes
Name the layout you are pointing at
Arrange regions and reading order around the user’s main task.
Open field note
Payment channels, PG, and merchant of record
Link trusted payment evidence to repeat-safe access and clear seller duties.
Open field note
Subscription, one-time payment, or ads?
Connect payer, billing and access to explicit revenue and cost assumptions.
Open field note
Delivery and operations: where it runs, how it recovers
Connect an artifact to its users, checks, recovery path and responsible owner.
Open field note
Requirements: agree on what done means
Turn expected behavior and constraints into observable completion checks before choosing implementation details.
Open field note
Astro, Hugo, Jekyll: three ways to ship HTML
Generate public files ahead of requests when publishing can follow a build.
Open field note
Themes and fonts without fifty shades of almost
Name visual roles so shared colors, type and spacing stay consistent.
Open field note
Language, library, framework, engine
Compare tools by responsibility, required output and maintenance cost.
Open field note