Skip to content

feat(history): series page shows the stories first, then the dynasty - #160

Merged
devudilip merged 1 commit into
mainfrom
feat/history-series-page-stories-first
Oct 16, 2026
Merged

devudilip merged 1 commit into
mainfrom
feat/history-series-page-stories-first

Conversation

@devudilip

Copy link
Copy Markdown
Owner

On a series page the dynasty essay filled the first screen and the story cards sat below it, so a reader could miss that stories exist.

Change

  • Series header, then a jump row with two chips: ಕಥೆಗಳು (with the count) and ಈ ರಾಜವಂಶ, both anchors on the same page.
  • The story grid comes next, then the dynasty section (intro, rulers, dating, sources) below it. Both stay fully visible; nothing is collapsed.
  • In the ruler list, a ruler who has a published story shows a small cover card linking to it, so the dynasty text also leads into the stories as more are added per dynasty.
  • One new string, ಈ ಪುಟದಲ್ಲಿ / On this page, as the jump row's label.

Verified in the dev preview on desktop and at phone width (Badami and Kalyani pages).

Gates

typecheck, test (821), build, check:bundle pass.

The dynasty text filled the first screen and the story cards sat below
it, so readers could miss that stories exist. Now the series header is
followed by a jump row (ಕಥೆಗಳು with the count, ಈ ರಾಜವಂಶ), then the story
grid, then the dynasty section. Each ruler who has a story gets a small
cover card in the ruler list, so the dynasty page also leads to the
stories as more are added per dynasty.

Signed-off-by: Devu Dilip <devu.dilip@gmail.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying sirigannada with  Cloudflare Pages  Cloudflare Pages

Latest commit: ea6dacf
Status: ✅  Deploy successful!
Preview URL: https://668ce08d.sirigannada.pages.dev
Branch Preview URL: https://feat-history-series-page-sto.sirigannada.pages.dev

View logs

@devudilip
devudilip merged commit 2a44866 into main Oct 16, 2026
4 checks passed
@devudilip
devudilip deleted the feat/history-series-page-stories-first branch October 16, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant