Timeline FAQ Block for React

Add an entry at the top of RELEASES at the start of the file: an id, the version as it's written ("v4.3"), a one-line summary and the answer, one to three sentences. Give latest: true to the newest entry only, and take it off the one before. OPEN_RELEASE is the first entry's id, so the newest release is the one that's open on load. Keep about six: older releases belong on a changelog page.

Each row draws its own hairline segment down the start side, with CSS: the first starts at its dot and the last stops at its own, and the segment grows with the row when an answer opens, so the rail is always one line. The version column and the rail sit at fixed offsets from the row's padding, and the answer is indented to line up under the question. Dots and versions are decoration: the version is read as part of each question.

Yes. The Accordion takes hiddenUntilFound, so every closed answer stays in the markup as hidden="until-found" and the browser's find in page opens the one that holds a match.

Each release is a button inside its own h3 under the section's h2, so a screen reader's headings list shows every release, and the button says whether it's expanded. Its name is the question, the Latest badge where there is one, and the summary. Enter or Space opens and closes a row. Tab moves from release to release.

Add multiple to the Accordion to let several stay open.

The rail stays one line however many are open.

Below sm the version column is hidden, the dots stay on the rail at the start, and the question wraps beside them with its Latest badge and summary under it. Every version still appears in its question, and nothing scrolls sideways at 320 pixels.