> For the complete documentation index, see [llms.txt](https://docs.eralis.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eralis.live/readme.md). # Eralis Welcome to your team’s developer platform **Turn complex information into a timeline you can actually explore.** Eralis is a visual workspace for organizing events, eras, people, places, sources, and relationships around a project. Instead of keeping research scattered across notes, you can structure it and inspect the same material through multiple views. ## What you can do * Build projects around chronological events and eras. * Maintain a library of entities and sources alongside your timeline. * Switch between **Timeline**, **Cards**, **Calendar**, **Map**, and **Graph** views. * Use the built-in planner for project tasks and deadlines. * Keep version snapshots of edits and restore earlier project states. * Schedule published timelines to open and close at specific times. * Export project data in supported formats. ## Start here Visit **Documentation** for the product guide, **Help Center** for common questions, **Changelog** for implementation status, and **API Reference** for the technical architecture and data model. > Eralis is actively being developed. Features documented as *planned* are roadmap items and are not presented as currently available. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eralis.live/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.