Make an interactive timeline in HTML and share it as a link

Build one interactive timeline website, check every date and action, then open the actual reader link on a phone.

In short

Put the events in one vertical HTML page, make every event a real button, and show the detail beside the date that opened it.

Check the dates against your source, test both a successful action and an empty input, then share the reader link instead of the editing address.

NOS Team built a fictional interactive timeline website for the Northwind Radio Archive. It contains five invented station events. A reader can open any event or enter an exact year. We opened the page at phone width, expanded the 1938 event, searched for 1938, and submitted the year finder empty. The success and error states were both visible on the public page.

How do you make an interactive timeline website?

Finish the reading experience before adding more decoration. The useful sequence is short:

  1. List the source events. Give each item a date, title, and explanation. Mark a date as approximate or disputed when the source does.
  2. Use a vertical order. Oldest to newest is easier to scan on a narrow screen than a wide strip that hides later events.
  3. Make each event a button. The title should still make sense before the detail opens, and the expanded state should be visible to assistive technology.
  4. Add one way to find an event. Our example accepts an exact year and explains what to do when the field is empty.
  5. Test the complete file. Open an event, try the finder, make it fail on purpose, and read the page at phone width.
  6. Create the reader link. Open that address separately and repeat the important actions.
NOS Code view containing the complete fictional radio archive timeline
The complete fictional timeline is kept in one HTML document, with its preview beside the code the code area.
NOS View showing the fictional Northwind Radio Archive timeline on a desktop screen
View shows the title, exact-year finder, and the first timeline events in one vertical column.

What data should each timeline event contain?

Keep the visible row compact: date and title first, explanation after the reader opens it. In the fictional archive, the 1938 row is “Evening story hour begins.” Opening it reveals the invented note about short plays recorded after a ferry shift. The open counter changes from zero to one, so the reader can see that the action worked.

Public desktop page with the fictional 1938 radio archive event expanded
Tapping the 1938 event reveals its explanation and changes the counter to one opened event.

Use the same fields for every item. If one row contains a location, source note, or category, either provide that field consistently or explain why it appears only there. Do not infer a precise date from a vague source just to make the page look complete.

The original version of this guide used an Ancient Rome example and warned that a confident-looking date can still be wrong. That warning remains useful. Compare each date and the order with a source you trust before sharing the page. If a date is traditional, approximate, or debated, say so in the event text.

How do you test an interactive timeline in HTML?

Test the result rather than the appearance alone. For this page, a successful exact-year search had to do three things together: confirm the year in the message, open the matching event, and move the highlight to the 1938 marker. The public page did all three.

Public timeline after a successful search for the fictional 1938 event
A successful year search opens the matching event, highlights its marker, and confirms the year above the list.

Then test a failure that a real reader can trigger. We pressed Find with no year entered. The page displayed “Enter a year before choosing Find.” It did not pretend that the first event was a match, and the open counter stayed at zero.

Public timeline showing the empty-year validation message
The empty field produces a specific instruction while the timeline remains usable.

Also check keyboard focus, readable labels, and the narrow layout. Each timeline item in this example is a button rather than a clickable container with no name. The page includes a phone viewport setting, and its content stays in one column at 390 pixels wide. If an interaction does nothing, repair that action before publishing. A polished line and decorative markers do not compensate for a button that cannot open its event.

How do you turn the HTML timeline into a shareable page?

Put the finished HTML in NOS, check it in View, and open Share. The panel for this example states that anyone with the link can read the page without signing in and cannot edit it. Copy that reader address. Do not send the workspace editing address.

NOS Share panel for the fictional interactive timeline
The Share panel separates the reader link from workspace access and editing.
Public NOS page showing the fictional interactive timeline on a desktop screen
The reader address opens the revised timeline on a desktop screen without showing an editing control.

The public page keeps the interactions from the HTML. Opening an event changes that visitor’s current page state. It does not rewrite the source timeline. To make a correction permanent for later readers, edit the existing source page and save it.

Yes, when you edit the existing NOS page. We opened normal Edit mode on this example, selected the introductory sentence, changed “invented” to “fictional,” and chose Done. The page remained in the same workspace document. The original reader address then showed the revised sentence.

Normal NOS Edit mode open on the original fictional timeline
Edit mode before the introductory sentence was changed.
NOS View showing the revised introduction on the same timeline page
The saved View uses “fictional moments” on the existing page.

This is the important difference between an on-page interaction and a source edit. A visitor can open an event or run a search for their current visit. The owner changes the shared version by editing and saving the existing page.

What should you ask an AI chat to make?

Describe the content and the behavior in plain language. Ask for one complete HTML file, a vertical timeline, real buttons for events, a visible expanded state, an exact-year finder, a clear empty-input message, phone-sized text, and no outside images or fonts. Supply the event data yourself. Tell the AI not to invent missing dates and to mark unresolved facts for review.

Check that the response includes the complete closing markup and that every event from your source appears once. If the page depends on an outside file, it is no longer the self-contained example requested here. The complete fictional Northwind example is preserved beside this local draft for later integration; it is not yet a live article download.

When not to do this

  • Do not use a static public timeline as a private student record, client log, or place for confidential archive data.
  • Do not use this single-page pattern when many editors need approvals, simultaneous changes, or a database of submissions.
  • Do not publish disputed history as a precise fact. Keep the uncertainty with the event and cite the source in the finished page.
  • Do not replace the authoritative project schedule with a reading copy. For dependencies and owners, keep the source tracker and use the timeline as a review view.

Using NOS for an interactive timeline

NOS Workspace held the complete fictional HTML, rendered its event and finder controls in View, created a reader address in Share, and saved a text revision made in Edit. The same reader address displayed that revision afterward. Check the current pricing page for plan details; this guide does not state a price.

For a simpler roadmap that stays vertical on phones, read the HTML timeline template guide. If intervals and a movable time scale matter, compare the read-only vis-timeline handoff guide. For the phone sizing rule, see the viewport meta tag guide. When the file is ready, turn the HTML into a reader link.

Questions people ask

Can I make an interactive timeline in HTML without writing the code myself?

Yes. Give an AI chat your checked event data and ask for one complete HTML file with a vertical list, buttons, an expanded state, phone sizing, and clear empty-input handling. Review every date and test the result before sharing it.

What makes an HTML timeline interactive?

A reader action must cause a useful, visible change. In the tested example, an event button reveals its explanation, while an exact-year search opens and highlights the matching event.

Why should I test an empty year field?

It verifies that the page guides the reader instead of failing silently or selecting an unrelated event. The tested page kept the timeline available and showed a specific instruction.

Do readers need a NOS account to open the timeline?

The Share panel captured for this example says that anyone with the reader link can read the page without signing in and cannot edit it.

Will the same link show a corrected timeline?

Yes, when the owner edits and saves the existing NOS page. In this test, the original reader address showed the revised introductory sentence after the edit.

Keep reading