> For the complete documentation index, see [llms.txt](https://lewe.gitbook.io/teamcal-neo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lewe.gitbook.io/teamcal-neo/readme.md).

# TeamCal Neo

![](/files/oapgRTLUfDEzOs0WvX9R)

TeamCal Neo is the successor of the popular TeamCal Pro. It is a web-based calendar application written in PHP and MySQL. It’s purpose is the day-based absence management of project teams.

TeamCal Neo’s goal was to keep the successful concept of a day-based calendar while modernizing the code-base and improving the UX with a responsive design. You can view it on any mobile device due to its responsive web design, however, its best viewed on a desktop.

TeamCal Neo supports the customization of holiday types and absence types, thus, its purpose can be altered to any graphical representation of timeline based processes or activities, e.g. a simple project plan or an event management. I have seen many great ideas of how to use TeamCal Pro that can also be done in TeamCal Neo.

The application comes in two flavors:

1. TeamCal Neo Basic (free)
2. TeamCal Neo (subscription)

Check out the [feature comparison](/teamcal-neo/readme/feature-comparison.md).


---

# 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://lewe.gitbook.io/teamcal-neo/readme.md?ask=<question>&goal=<endgoal>
```

`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.