Poster vs. Project Pages — Two Deliverables, Two Purposes
The poster sells the design. The project pages tell its story. They serve different audiences and different evaluative contexts — design each accordingly.
Why they are different
A poster is read at a distance, in competition with fifteen other posters, by a viewer who has approximately 30 seconds to understand its argument before moving on. A project page is read up close, by a viewer who has already decided to engage with the work, in the context of a sequential narrative.
The same image used differently in each deliverable is not redundant — it is appropriate. A hero rendering that fills a quarter of the poster commands attention at pin-up scale. The same image used at a smaller size within a spread, alongside process sketches and diagram evolution, tells a different part of the story. The relationship between the two deliverables is additive: the poster makes the argument, the pages provide the evidence and process that earned the argument.
The poster — what it must do
| Test | What's required |
|---|---|
| 10-foot readability | Title legible; primary image identifiable; overall layout structure comprehensible at pin-up distance |
| 30-second argument | A viewer who stops for 30 seconds should be able to state in one sentence what the design is about |
| Visual hierarchy | One unmistakable entry point; a clear secondary layer; a supporting layer. Three tiers maximum. |
| Image quality | Every image at output resolution; no visible JPEG artifacts; no visible scaling artifacts |
| No redundancy | Each element shows something different. If two images show essentially the same thing, one should be replaced. |
The project pages — what they must do
| Test | What's required |
|---|---|
| Complete narrative arc | Site analysis → concept response → design development → final design → detail. A reader following the pages in sequence should understand how the site's conditions produced the specific design. |
| Process visibility | Sketches, diagram iterations, and early design alternatives show the thinking behind the final work. A portfolio page with only final renders is not a process document. |
| Poster content at appropriate scale | All poster images appear in the pages at sizes that allow the detail that the poster's scale compressed. The viewer should see more here, not less. |
| Consistent visual identity | Typography, palette, and grid consistent with the poster. The two documents should be recognizably from the same designer and the same project. |
| Text as evidence | Design narrative text that describes what was decided and why — not what is visible in the images, which the images already communicate. |
What content lives where
| Content | Poster | Project pages |
|---|---|---|
| Hero perspective rendering | Yes — primary | Yes, with context of adjacent process work |
| Site analysis diagrams | Possibly one if very strong | Yes — central to the design rationale narrative |
| Plan view | Yes — technical reference | Yes, at larger scale with more detail visible |
| Section/elevation | Optional — if it's among your strongest images | Yes — important for spatial quality communication in sequence |
| Evening rendering | Yes if differentiated from daytime | Yes alongside daytime for comparison |
| Early sketches and process work | No | Yes — this is what the project pages are for |
| Precedent images | No | Yes — establishes design references in the narrative |
| Design concept text | Brief — one or two sentences | Extended — full design narrative with analysis connection |
Building them as a system
Build the poster first. It forces you to identify your strongest images and clarify your design argument. Once the poster is complete, build the project pages as the expanded evidence base that supports that argument — adding process, analysis, and development content that the poster's spatial constraints excluded. The project pages should feel like the answer to "how did you get there?" — and the poster should feel like the answer to "what did you make?"
Try this
Write two descriptions of your project: one as if you have 30 seconds and a single page — this is the poster brief. One as if you have ten minutes and eight pages — this is the project pages brief. The content that appears in both descriptions belongs on both deliverables. The content that only fits in the ten-minute version belongs on the project pages. The content that only works in the 30-second version is the poster's headline material. This exercise defines the content hierarchy before layout work begins — which is always the more productive order of operations.