Skip to main content

Documentation Index

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

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

Join thousands of developers building with InsForge. Get help, share your projects, and contribute to the platform.

Community Channels

Discord

Join our Discord server for real-time help, discussions, and community support

GitHub Discussions

Ask questions, share ideas, and discuss features

Twitter/X

Follow for updates, tips, and announcements

LinkedIn

Connect with the team and stay updated on company news

Get Help

Discord Community

Our Discord server is the best place to get real-time help:
  • #general - General discussion and questions
  • #help - Technical support and troubleshooting
  • #showcase - Share your projects built with InsForge
  • #feature-requests - Suggest new features
  • #announcements - Product updates and news

Join Discord

Connect with 1000+ developers

GitHub Issues

Report bugs, request features, or browse existing issues:

Report a Bug

Found a bug? Let us know

Request a Feature

Suggest improvements or new features

Email Support

For direct support, reach out to our team:

Contributing

We welcome contributions from the community! Whether you’re fixing bugs, adding features, or improving documentation, your help is appreciated.

Ways to Contribute

Code Contributions

Submit pull requests for bug fixes, features, or improvements

Documentation

Help improve our docs with corrections, clarifications, or new guides

Bug Reports

Report issues you encounter while using InsForge

Community Support

Help other developers in Discord or GitHub Discussions

Contribution Guidelines

Getting Started

  1. Fork the repository to your GitHub account
  2. Clone your fork locally:
    git clone https://github.com/insforge/insforge.git
    cd insforge
    
  3. Install dependencies:
    • Install Docker and ensure it’s running
    • Install Node.js (LTS version)
  4. Create environment file:
    cp .env.example .env
    
  5. Start the project:
    docker compose up
    

Development Workflow

  1. Create a branch for your changes:
    git checkout -b feat/your-feature-name
    
    Branch naming conventions:
    • feat/ - New features
    • fix/ - Bug fixes
    • docs/ - Documentation changes
    • refactor/ - Code refactoring
    • test/ - Test-related changes
    • chore/ - Build or tooling changes
  2. Make your changes following the code style guidelines
  3. Add tests for your changes
  4. Run tests:
    npm run test:e2e
    
  5. Run linter:
    npm run lint
    
  6. Commit your changes using Conventional Commits:
    git commit -m "feat(scope): description"
    
  7. Push to your fork and open a pull request

Pull Request Guidelines

  • Create a draft PR early to facilitate discussion
  • Reference related issues (e.g., “Closes #123”)
  • Keep PRs focused on a single feature or bug fix
  • Update documentation as needed
  • Ensure all tests pass before requesting review
  • Respond to feedback in a timely manner

View Full Contributing Guide

Read the complete contribution guidelines

Code of Conduct

InsForge is committed to providing a welcoming and inclusive community for everyone.

Our Pledge

We pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Positive behavior includes:
  • Demonstrating empathy and kindness
  • Being respectful of differing opinions and experiences
  • Giving and accepting constructive feedback
  • Accepting responsibility for mistakes and learning from them
  • Focusing on what’s best for the community
Unacceptable behavior includes:
  • Sexualized language or imagery
  • Trolling, insults, or derogatory comments
  • Public or private harassment
  • Publishing others’ private information without permission
  • Other conduct inappropriate in a professional setting

Enforcement

Instances of unacceptable behavior may be reported to tony.chang@insforge.dev. All complaints will be reviewed and investigated promptly and fairly.

Read Full Code of Conduct

View the complete Contributor Covenant Code of Conduct

Community Projects

Explore projects built by the InsForge community.

View Showcase

Browse applications built with InsForge

Share Your Project

Built something with InsForge? We’d love to feature it! To submit your project:
  1. Share it in the #showcase channel on Discord
  2. Open a GitHub Discussion
  3. Tag us on Twitter/X with #BuiltWithInsForge

Recognition

Contributors

Thank you to all our contributors who help make InsForge better!

Star the Project

If you find InsForge useful, consider giving us a star on GitHub!

Star on GitHub

Show your support with a GitHub star

Project Badges

Show that your project is built with InsForge:

Made with InsForge

Made with InsForge Markdown:
[![Made with InsForge](https://insforge.dev/badge-made-with-insforge.svg)](https://insforge.dev)
HTML:
<a href="https://insforge.dev">
  <img
    width="168"
    height="30"
    src="https://insforge.dev/badge-made-with-insforge.svg"
    alt="Made with InsForge"
  />
</a>

Stay Updated

Discord

Join the community

Twitter/X

Follow for updates

GitHub

Star and watch the repo