# 03 — Postcards by Elle: “morning walks and listening to full albums will save you” - **Source:** https://postcardsbyelle.substack.com/p/morning-walks-and-listening-to-full - **Captured:** 2026-07-11 - **Surface studied:** Complete Substack article at 1440×1000 and 390×844 - **Reading archetype:** Personal essay/newsletter with magazine-like sections and community utilities - **Responsive classification:** Recomposed ## Visual references - [Desktop — full-page overview strip](../assets/references/03-substack-morning-walks/desktop-full.png) - [Desktop — first viewport](../assets/references/03-substack-morning-walks/desktop-hero.png) - [Desktop — readable mid-article viewport](../assets/references/03-substack-morning-walks/desktop-body.png) - [Mobile — full-page overview strip](../assets/references/03-substack-morning-walks/mobile-full.png) - [Mobile — first viewport](../assets/references/03-substack-morning-walks/mobile-hero.png) - [Mobile — readable mid-article viewport](../assets/references/03-substack-morning-walks/mobile-body.png) The full-page files are deliberately used as pacing/anatomy overviews; use the hero and body viewport captures for typographic detail. ## Evidence note - **Observation:** The page was inspected after dismissing the initial subscription overlay. Cookie/ad clutter was removed while the publication bar, subscribe controls, engagement row, table of contents, comments, and related-content utilities were preserved. - **Observation:** Nine article/recommendation images were lazy-loaded. Existing image elements were temporarily switched to eager before the final full-page screenshots so the saved evidence is complete; all image natural widths were then non-zero. - **Inference:** Editorial and accessibility judgments are based on the captured public page, not on the author’s intent or Substack analytics. ## First impression - **Observation:** This is a warm, personal reading room: pale peach surface, brown serif text, a hand-lettered red publication mark, an intimate kitchen photograph, and language that names sections like a piece of music. - **Observation:** The article is long—8,139 audited words—but the first viewport immediately establishes title, premise, social proof, epigraph, first section, and a decisive image. - **Inference:** The design sustains length by alternating memoir, quotation, research/link evidence, personal photography, and “interlude” sections. It feels like correspondence rather than a content-marketing funnel. - **Inference:** Substack’s platform utilities add trust and community, but the initial subscription prompt and dense post-article ecosystem compete with the calm editorial voice. ## Article anatomy, in order 1. **Fixed publication bar.** Publication identity plus search/share-publication, subscribe, and sign-in utilities on desktop; a simplified logo/subscribe/sign-in set on mobile. 2. **Article header.** “POSTCARDS” label, H1, descriptive subtitle, like/comment/restack counts, and share action. 3. **Epigraph.** Oversized drop-cap “I,” italic line, and source attribution, closed by a subtle rule. 4. **Prelude.** Section heading and a full-column domestic kitchen photograph. 5. **Cross-promotion card.** A compact preview of another Postcards entry before the main memoir begins. 6. **Personal narrative.** Long paragraphs about childhood illness, stress, anxiety, and recovery. 7. **Linked prior-essay callout.** A visually distinct quote/link introduces the practice of walking. 8. **Walking chapter.** Explanatory prose, external evidence links, philosophical quotations, and supporting images/screenshots. 9. **Full-album chapter.** A second habit expands the argument; images and screenshots reset visual attention. 10. **Interlude I: reading.** Books and article links become a mini syllabus, including another internal post preview. 11. **Interlude II: watching.** Movie and video-essay recommendations shift into list-like scan mode. 12. **Postlude.** A short personal close and “Springtime” image. 13. **Subscription conversion.** Inline email form and terms/privacy notices. 14. **Community layer.** Engagement summary, comments/restacks tabs, visible comment excerpts, and a link to more comments. 15. **Discovery layer.** “Top / Latest / Discussions” tabs, related publication posts, second email CTA, and the Substack footer. ## Desktop behavior - **Observation:** The article is a centered 728px column within the 1440px page. Its top padding is 32px beneath the fixed 88px publication bar. - **Observation:** Body paragraphs use Spectral at 20px/32px with 20px bottom spacing. Most paragraphs occupy the full 728px; inset linked/callout passages use a 20px left offset and 704px measure. - **Observation:** The title uses Lora at 32px/36px and does not become an oversized billboard. The subtitle is 18px/24px, leaving the image and drop cap to carry more of the opening’s visual drama. - **Observation:** Full-column images are 728px wide; the body also admits narrower images, screenshots, pin embeds, and preview cards without forcing a uniform treatment. - **Observation:** Engagement counts sit as compact pills under the subtitle, while Share is separated at the right edge of the article header. - **Observation:** The complete page measured about 14,235 CSS pixels after media loaded. - **Inference:** A moderate 728px measure and 1.6 body line-height are the foundation. Section names and media do the pacing; the typography itself stays deliberately stable. ## Mobile adaptation - **Observation:** The article becomes a 358px column with 16px side margins and 16px top padding. - **Observation:** The H1 remains 32/36px, so it wraps into three strong lines instead of losing identity. The body changes from 20/32px to 18/28.8px. - **Observation:** Section H3s shift from 27.5/31.9px to 24.75/28.71px. The hierarchy compresses proportionally rather than collapsing to one size. - **Observation:** The fixed header drops from 88px to 57px and removes the desktop search/share-publication icons from the first-view bar. Subscribe and Sign in remain. - **Observation:** Like, comment, restack, and Share reflow into one compact utility row beneath the subtitle; Share is no longer held at the distant desktop edge. - **Observation:** The kitchen image and subsequent media fill the 358px reading width. No desktop side rail survives as a skinny adjacent column. - **Observation:** The full mobile page measured about 17,999 CSS pixels, reflecting additional text wrapping while preserving all sections and community content. - **Inference:** This is a careful re-composition of priorities: identity and conversion stay in the header, article utilities move into the reading flow, and imagery becomes edge-to-edge within the column. ## Typography system - **Observation:** Lora carries the publication/article title and section headings. Spectral carries the essay body. Substack’s system/SF/Arial stacks handle product controls, comments, forms, and recommendation modules. - **Observation:** Desktop body: Spectral 20/32px, weight 400. Mobile body: 18/28.8px. Primary text is `rgb(93, 76, 55)`. - **Observation:** H1 remains Lora 32/36px on both breakpoints. Section headings change from 27.5/31.9px to 24.75/28.71px. - **Observation:** The subtitle is Lora 18/24px in `rgb(134, 132, 128)`. - **Inference:** The three-family split is effective because it separates publication identity, reading voice, and platform mechanics. The UI never asks the essay serif to impersonate a button font. ## Color and imagery - **Observation:** The article background is `#fff7ed`; primary prose is `#5d4c37`; muted text is `#868480`; dark brown controls/accents use values near `#5c400e`; the publication signature adds a vivid red. - **Observation:** Supporting surfaces include a slightly darker warm neutral near `#f0e8df` and dark brown conversion bands near the footer. - **Observation:** The page contains 22 images in the desktop inventory: publication marks, a kitchen hero, story-preview thumbnails, personal/seasonal photographs, screenshots/diagrams, reader avatars, and related-post thumbnails. - **Observation:** Nine images use lazy loading and responsive Substack CDN `srcset` candidates; many resolve to WebP in the browser. - **Inference:** The images feel personal because they change function and scale. A uniform 16:9 “content image” component would flatten the diary/syllabus rhythm. ## Navigation, progress, sharing, and related content - **Observation:** The publication bar is fixed. Search and publication-share are visible on desktop; subscribe and sign-in persist on both breakpoints. - **Observation:** A “Table of Contents” button is present in the accessibility tree. No persistent numerical/linear reading-progress indicator was observed. - **Observation:** Like, comments, restacks, and share appear immediately after the deck and again at the end. Images expose view/restack actions; headings or blocks expose link-copy controls. - **Observation:** The article ends with comments/restacks tabs, related-post tabs, recommendation cards, and a second subscription form. - **Inference:** Orientation is stronger than a bare newsletter because a table of contents exists, but a subtle progress cue could help an 8,000-word page without making it feel like documentation. ## Interaction and motion - **Observation:** Header height/logo transforms use approximately 125ms transitions. Buttons, image controls, and link utilities generally use 250ms color/background/outline/transform transitions. - **Observation:** No entrance animation or scroll-driven content reveal was observed; article content is visible by default. - **Inference:** The functional motion matches the medium. The author’s cadence, not interface choreography, creates the emotional journey. ## Accessibility and performance concerns - **Observation:** The heading inventory includes an empty H1 before the article-title H1, likely from publication branding. Screen-reader users may encounter an unnecessary top-level heading. - **Observation:** All 22 desktop image elements had an `alt` attribute, but seven were empty. Several empty values belonged to meaningful article images rather than clearly decorative assets. - **Observation:** Nine links had neither visible text nor an `aria-label`; many appear to be image wrappers or platform utilities. - **Observation:** Image view/restack controls often measured 32×32px and top-bar controls 40×40px, below a 44×44px touch-target recommendation. - **Observation:** Primary `#5d4c37` text has strong contrast on `#fff7ed`. The muted `#868480` subtitle on that background is approximately 3.5:1 by calculation, below 4.5:1 for 18px regular text. - **Observation:** The initial subscription overlay interrupted the page until dismissed during capture. - **Observation:** Responsive CDN images, WebP negotiation, and lazy loading are positive. The cost is a large platform DOM with comments, recommendations, duplicate subscription surfaces, and many interactive controls loaded alongside the article. - **Inference:** Defer comments/recommendations until near-viewport and darken muted article text. Those two changes would improve both performance and inclusive reading without changing the publication’s look. ## Transferable patterns 1. **Name sections as narrative states.** “Prelude / interlude / postlude” gives a sprawling essay memorable landmarks without sounding like documentation. 2. **Keep the reading voice distinct from the product UI.** Use editorial type for the article and a neutral utility face for controls/forms/comments. 3. **Give the opening multiple hooks.** Title, subtitle, social proof, epigraph, section heading, and one decisive image all appear before dense body copy. 4. **Vary media roles.** Mix full-width photography, narrower screenshots, preview cards, quotations, and lists instead of repeating one image component. 5. **Move community after meaning.** Immediate counts establish life around the post; the actual conversation and related feed wait until the essay concludes. ## What not to copy - Do not copy the warm palette, Lora/Spectral pairing, handwritten logo, or personal-image aesthetic as a generic “editorial” preset. - Do not interrupt first-time readers with a modal subscription ask before they have sampled the article. - Do not accept empty alt text on meaningful photographs or screenshots. - Do not ship 32px image actions or 40px primary bar controls on touch surfaces. - Do not load the entire comments/recommendation ecosystem eagerly when the article is already media-heavy. - Do not let platform modules blur the editorial ending; add a clear visual stop before conversion and community content. ## Implementation notes - Use a `max-width` near 728px for desktop and 16px fluid page gutters on mobile; allow media components to opt into full, inset, or card widths. - Preserve a 1.6 line-height across breakpoints: 20/32px desktop, 18/28.8px mobile is a tested baseline here. - Model article content as semantic blocks: epigraph, section, paragraph run, quotation, image/caption, related-story embed, resource list, postlude. - Use CSS grid/flex areas for header utilities so Share can separate on desktop and join the engagement row on mobile without duplicated markup. - Lazy-load below-fold media with reserved dimensions and `srcset`; keep the first decisive image eager. - Give the table-of-contents control a visible label/state and pair it with a low-noise progress cue for articles of this length. - Separate the editorial endpoint from the platform endpoint: first close the essay, then render subscribe, engagement, comments, and recommendations. ## Evidence limits - Focus order, keyboard operation, screen-reader announcements, and `prefers-reduced-motion` behavior were not exhaustively tested. - Substack supplies much of the shell and can change it independently of the publication; observations are time-bound to 2026-07-11.