Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/taskian/mintting/llms.txt

Use this file to discover all available pages before exploring further.

Getting started with Mintting takes just a few minutes. Because the project is in early development, the quickest way to engage with it is to clone the repository from GitHub, browse the code, and then open an issue or pull request if you have ideas or find something to improve.

Clone and explore the repository

1

Clone the repository

Clone the Mintting repository to your local machine using Git.
git clone https://github.com/taskian/mintting.git
This creates a mintting/ directory on your machine containing the full project history and all current files.
2

Navigate into the project

Move into the cloned directory to start exploring.
cd mintting
From here you can browse the project structure, read any existing source files, and understand how the project is organized.
3

Explore the project locally

Take a look at what is in the repository. Because Mintting is at an early stage, the structure will continue to evolve, but reviewing the files gives you a clear picture of where the project currently stands.
Check open issues and pull requests on GitHub alongside the local files — they often explain the intent behind work in progress.
4

Open an issue or contribute

If you find a bug, have a question, or want to suggest a direction for the project, open an issue on the GitHub repository. To contribute code or documentation, fork the repository and open a pull request.
Early-stage projects benefit most from clear, specific issue reports. Include as much context as you can when opening an issue.

What to do next

Now that you have the repository locally, here are the most useful places to continue:

Guides overview

Read the high-level overview of Mintting’s concepts and goals.

Usage guide

Learn the typical workflows for working with Mintting.

Open an issue

Report a bug or suggest a feature directly on GitHub.

View the source

Browse the full repository, forks, and contribution history.

Build docs developers (and LLMs) love