Use the description to capture context that does not fit in the structured fields — the goals of the investigation, the regulatory trigger, the methods planned, or any background a colleague would want before opening the Project. Where name is a short label, the description is room to write a paragraph or two. It is optional, so a quick survey may leave it blank while a multi-season excavation might keep a detailed summary here. Because it is plain text and not tied to uniqueness or indexing, you can edit it freely as the project evolves and your understanding of the work deepens.
Technical section
Data model, API, and internals — visible to developers.