Fix narrow article content width #187

Closed
opened 2026-06-22 07:07:15 -05:00 by erik · 2 comments
Owner

Summary

Post detail pages do not use the available article card width. The rendered .post-content is capped at max-w-3xl (768px), while the surrounding article card has substantially more horizontal space available.

Steps to reproduce

  1. Start the Slugkit site locally.
  2. Open http://localhost:3000/posts/decentralized-social-media in Chromium.
  3. Inspect the post detail layout width.

Expected behavior

  • Article content uses the available post/card width appropriately.
  • The post body does not leave excessive unused horizontal space when the viewport has room.

Actual behavior

  • The article card renders around 1120px wide at a 1200px viewport.
  • .post-content is constrained to max-w-3xl / 768px, leaving unused space to the right.

Acceptance criteria

  • Post detail content uses the available article content width at desktop sizes.
  • The layout remains readable and responsive at narrower viewport sizes.
  • Existing public page styling/tests are updated if needed.
## Summary Post detail pages do not use the available article card width. The rendered `.post-content` is capped at `max-w-3xl` (768px), while the surrounding article card has substantially more horizontal space available. ## Steps to reproduce 1. Start the Slugkit site locally. 2. Open `http://localhost:3000/posts/decentralized-social-media` in Chromium. 3. Inspect the post detail layout width. ## Expected behavior - Article content uses the available post/card width appropriately. - The post body does not leave excessive unused horizontal space when the viewport has room. ## Actual behavior - The article card renders around 1120px wide at a 1200px viewport. - `.post-content` is constrained to `max-w-3xl` / 768px, leaving unused space to the right. ## Acceptance criteria - [ ] Post detail content uses the available article content width at desktop sizes. - [ ] The layout remains readable and responsive at narrower viewport sizes. - [ ] Existing public page styling/tests are updated if needed.
erik 2026-06-22 07:07:15 -05:00
Author
Owner

Synced from todu comment by @todu on 2026-06-22T12:17:46.125Z

Closing summary

  • PR #188 was merged to main as merge commit 033b09c with implementation commit bffdfba (fix: expand post detail content width, Task: #task-83b6b57c).
  • Acceptance criteria verified from the merged diff:
    • Post detail content now uses the available article width: template/site/src/templates/public.tsx removed max-w-3xl from the post detail .post-content class.
    • Narrow viewport responsiveness/readability is preserved: the change did not add a fixed width; the content remains constrained by the existing responsive article/page containers and article padding (p-5, sm:p-10).
    • Public page tests were updated: template/site/src/routes/__tests__/public.test.ts asserts the post content class is present without max-w-3xl.

Close gate result: READY.

_Synced from todu comment by @todu on 2026-06-22T12:17:46.125Z_ ### Closing summary - PR #188 was merged to `main` as merge commit `033b09c` with implementation commit `bffdfba` (`fix: expand post detail content width`, `Task: #task-83b6b57c`). - Acceptance criteria verified from the merged diff: - Post detail content now uses the available article width: `template/site/src/templates/public.tsx` removed `max-w-3xl` from the post detail `.post-content` class. - Narrow viewport responsiveness/readability is preserved: the change did not add a fixed width; the content remains constrained by the existing responsive article/page containers and article padding (`p-5`, `sm:p-10`). - Public page tests were updated: `template/site/src/routes/__tests__/public.test.ts` asserts the post content class is present without `max-w-3xl`. Close gate result: READY.
Author
Owner

Synced from todu comment by @todu on 2026-06-22T12:15:28.954Z

Review update

  • PR: #188 is open and reviewed.
  • Result: approved.
  • Verified: diff reviewed against acceptance criteria, local ./scripts/pre-pr.sh passed, and Forgejo Actions run #258 is success.
  • Follow-up: waiting for explicit human merge approval; do not merge yet.
_Synced from todu comment by @todu on 2026-06-22T12:15:28.954Z_ ### Review update - PR: #188 is open and reviewed. - Result: approved. - Verified: diff reviewed against acceptance criteria, local `./scripts/pre-pr.sh` passed, and Forgejo Actions run #258 is `success`. - Follow-up: waiting for explicit human merge approval; do not merge yet.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
erik/slugkit#187
No description provided.