News article
Long-form reading. One column at the reading size, headings a reader navigates by, and almost no furniture — an article is typography before it is components.
What it is made of
Less than any other page in the system. An article leans on the foundations — the reading size, the column, the vertical rhythm — and reaches for a component only where prose cannot do the job.
GdBreadcrumb— where this sits, because an article is usually arrived at from outsideGdChip+ date + read time — the same metadata row the index uses, so the two agree--gd-text-readingover--gd-size-reading— 18px in a 700px column, roughly 78 characters- Two heading levels, and nothing else
The page
Where apartments are code assessable in Riverton
The zone decides almost everything. In Riverton's centre zones a block of apartments is assessed against a written rulebook — no public notice, no neighbours' submissions. Three streets away the same building is a different kind of decision entirely.
If you are looking at apartments or townhouses in Riverton, the single biggest thing separating a straightforward application from a hard one is not the design, the budget or the builder. It is the zone the land sits in, and it is knowable before you make an offer.
What code assessable actually means
In the centre zones and the higher-density residential zones, a multiple dwelling is code assessable. Council assesses the design against outcomes that are written down in advance, and if the proposal meets them it must be approved. There is no public notice and no submission period.
That is not the same as automatic, and it is worth being precise about the difference. Code assessment still involves judgement — on articulation, on setbacks, on how a building meets the street. What it removes is the possibility of being refused for reasons nobody wrote down first.
Where it changes
In the low density residential and character residential zones, the same building is impact assessable. A public notice goes up, anyone can lodge a submission, and the assessment weighs the whole planning scheme rather than a list of outcomes. That is a different kind of decision, and it takes a different amount of time and money to reach.
The practical consequence is that two sites a few hundred metres apart can carry the same price and completely different odds. The zone is public, the pathway is published, and the difference is the thing worth checking first.
Page-level rules
- Set prose at the reading size, not the interface one.
--gd-text-bodyis 13.5px, for a paragraph read in a glance beside the thing it explains. An article is read for minutes. That one substitution is most of what separates an article from a long panel. - The column is
--gd-size-reading. 700px at 18px is about 78 characters. Widening the column without growing the type makes the line longer and the page worse — which is exactly how a page ends up feeling compressed. - The standfirst is not the first paragraph. It summarises, it sits a step above the prose, and it must still make sense if the reader stops there.
- Two heading levels, and no more. A reader navigates an article by scanning headings. A third level is a table of contents pretending to be prose.
- One image is
priority, and it is the hero. It is the Largest Contentful Paint element on nearly every article, so it loads eagerly while every figure below it stays lazy. Marking more than one is the same as marking none. - Figures break the measure; prose never does. The column is set for reading, so an image held to it is not respectful, it is small.
GdFigure widewidens symmetrically and keeps the page on one axis. - Furniture only where prose cannot do the job. A table because four rows beat a sentence describing four rows; a figure because it shows something words cannot. Anything else is the interface leaking into the reading.
- The metadata row matches the index's. Same chip, same date format, same order — two surfaces describing one article differently is how a reader loses track of which one they are on.