## Showcase The examples below show changelog-style timelines with rich content, tags, repeated dates, and direct-link anchors. ### Long scrolling content with multiple entries release migration ## Migration preparation Start by documenting the exact scope of the rollout, including the pages, integrations, and deployment windows that are affected by the change. Create a short checklist for the team, then confirm which parts of the rollout can happen in parallel and which ones must stay serialized. - Confirm the affected environments - Capture rollback steps - Note any user-facing communication that must ship together with the release ~~~bash npm run lint npm run test npm run build ~~~ operations rollout ## Incremental rollout Ship the first slice to a smaller audience, watch the error budget, and log any unexpected behavior before widening exposure. If the metrics remain healthy, continue with the second rollout wave and update the changelog entry with the exact time and the observed result. > [!TIP] > Sticky dates and dots are easier to verify when each item contains enough body content to scroll independently. follow-up docs ## Post-release follow-up After the rollout finishes, collect the final metrics, summarize what changed, and add links to the support article, incident notes, or migration guide. This entry is intentionally long enough to help verify the comfortable-layout sticky behavior on later timeline items, not only on the first one. ### Single long entry single sticky-check ## One long entry for sticky checks Use a single-item timeline when you want to confirm that the date and dot still stick correctly even without later entries extending the rail. Repeat enough explanatory content here to create real scroll distance for the item and confirm the left-side metadata remains visible while the body moves. Repeat enough explanatory content here to create real scroll distance for the item and confirm the left-side metadata remains visible while the body moves. Repeat enough explanatory content here to create real scroll distance for the item and confirm the left-side metadata remains visible while the body moves. ### Product updates release permissions ## Site permissions update We simplified inheritance so site-level permissions are now easier to reason about across linked content. improvement search ## Faster site search Readers now get faster results from a local index, followed by remote refinement when more matches arrive. ### Rich markdown inside entries beta rss ## Update blocks with RSS support > [!TIP] > Use tags to label beta or rollout-specific entries. ~~~bash npm run build npm run release ~~~ ### Explicit anchors ux ## Custom icons in hint blocks Use the `anchor` attribute when you want a stable fragment that does not depend on the visible title copy. ### Repeated dates with unique generated anchors improvement ## New year improvements Generated anchors stay unique even if another item reuses the same date and title. fixes ## New year improvements This second entry gets a deduplicated hash suffix automatically.