How paul-hammant/tiny-timeline works
Main components
• Frontend (User Interface): The tiny-timeline.html file which is the entry point shown in the browser/mobile. This component is responsible for rendering the timeline, handling user interaction (like clicking or swiping) and reading timeline configuration (e.g., which timeline to display based on the URL hash).
• Data Sources: The JSON files (spaceflight-milestones.json and womens-rights.json) which contain the events to be displayed. These files provide event data that the HTML/JavaScript code consumes.
• Repository/Version Control: Although not part of runtime, the .gitignore coupled with the repository setup indicates the project is managed via Git.
Relationships and Interactions
• The browser loads tiny-timeline.html.
• The application fetches the JSON data, parses it, and populates the timeline accordingly.
• There is a direct data flow from the JSON files to the browser's timeline presentation logic.
Architectural Patterns & Design Principles
• This is a single-page static application with a clear separation between static content (HTML) and external data (JSON files).
• The design emphasizes minimalism and client-side rendering – all logic is contained within the HTML file.
• It uses progressive enhancement by relying on URL hash navigation, making it easily accessible on both desktops and mobile devices.
Relevant Technologies & Frameworks
• Core: HTML, likely CSS, and JavaScript (though no explicit libraries are mentioned, you may infer vanilla JS or small helper libraries may be used).
• Data Format: JSON for timeline events.
• Web Hosting/Deployment: The project is hosted statically (as seen from the provided GitHub Pages links).
• Optionally, include secondary notes indicating that the URL hash in the browser triggers the selection of the appropriate JSON file.