Introduction
Welcome to the internal documentation of Letraz. Albeit it’s called internal, it’s open to the public to go in alignment with our motto of transparency. This documentation is a work in progress and will be updated regularly as we develop new processes, APIs and workflows.
Introduction
This is the go-to guide for the Letraz core team to refer to in case of any confusion. This documentation is a work in progress and will be updated regularly as we develop new processes, APIs and workflows. The documentation is divided into multiple sections, each focusing on a different aspect of Letraz. The documentation is open to the public to go in alignment with our motto of transparency.
Refer to these docs whenever in doubt about how to proceed with a task or if you want to know more about the architecture of Letraz. Whenever a new architecture or process is developed, that is added in this documentation itself. If you have any suggestions or want to contribute to the documentation, feel free to open an issue GitHub repository. If you are part of the core team then just ping the team in the Discord server.
Quick links
Links of the resources that are frequently used by the team. Some of the links are public, but some links might contain sensitive information and are only accessible to the core team.
Admin Panel
Manage Letraz and it’s infrastructure. Houses tooling for managing database, aiding development process and much more.
Letraz Frontend Repo
Github repository for the frontend of Letraz. Houses the code for the frontend and the issues for team Letraz Core in Linear.
Letraz Backend Repo
Github repository for the backend of Letraz. Houses the code for the backend, database models and the API endpoints.
Letraz Utils Repo
Github repository for the utility functions used across the Letraz ecosystem. Houses the code for the utility functions, task queue, scrapping and Discord bot.
Additional links
Links of other frequently used third-party services that are used by the team. These services are used for project management, error tracking, analytics and much more. Most of these services are only accessible to the core team.
Linear
Linear is the project management tool used by Letraz. It houses the issues, tasks and the roadmap for Letraz and only accessible to the core team.
Sentry
Sentry is the error tracking tool used by Letraz. It tracks the errors and exceptions that occur in the Letraz ecosystem.
Posthog
Github repository for the backend of Letraz. Houses the code for the backend, database models and the API endpoints.