KaifAhmad1andClaude Sonnet 4.6
946a1089c8
- Migrate from mint.json to docs.json (Mintlify v4) - Theme: maple, emerald green + near-black dark / cream light palette (#059669 primary, #0A0A0A dark bg, #FAF7F0 light bg) - Typography: Lexend headings, Inter body - 5-tab navigation: Documentation, Quick Start, API Reference, Cookbook, FAQ - Homepage: removed badge stickers, redundant h2, added blockquote tagline, full 27-module reference table with semantica.mcp_server added - quickstart.md: CodeGroup per pipeline step, pattern vs LLM options, AccordionGroup for patterns and troubleshooting - faq.md: full AccordionGroup structure across 5 sections - reference/explorer.md: NEW — FastAPI explorer, Ontology Hub, Distance Intelligence, CLI reference, REST API endpoints - reference/mcp_server.md: NEW — MCP stdio server, 12 tools with I/O examples, 3 resources, Claude Desktop/VS Code/Windsurf/Cline config - docs.json: explorer added to Output group, mcp_server to Utilities group - Chat, feedback (thumbs/suggest/raise), OG/Twitter metadata, search topbar - All reference pages reformatted with Mintlify JSX components Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.7 KiB
title, description, icon
| title | description | icon |
|---|---|---|
| Contributing | How to contribute code, documentation, tests, and community support to Semantica. | code-pull-request |
Contributions of all kinds are welcome — code, documentation, tests, and community support.
Quick Start
# Fork the repo on GitHub, then:
git clone https://github.com/your-username/semantica.git
cd semantica
pip install -e ".[dev]"
pytest
New to the project? Look for good-first-issue labels.
Ways to Contribute
Code
- Fix bugs and resolve open issues
- Implement new features or integrations
- Optimize performance or refactor existing code
Documentation
- Fix typos, improve clarity, add examples
- Write tutorials or domain-specific cookbook notebooks
- Keep the API reference up to date
Testing
- Add coverage for untested modules
- Reproduce and confirm reported bugs
- Improve test reliability
Community
- Answer questions in issues and discussions
- Review pull requests
- Share Semantica in blog posts or talks
Reporting Issues
Bug reports — include: what happened, steps to reproduce, expected behavior, and your environment (Python version, OS, Semantica version).
Feature requests — include: your use case, what you'd like Semantica to do, and how it benefits others.
Pull Request Checklist
Before submitting:
-
Tests pass locally (
pytest) -
New features have documentation with examples
-
Code follows project style (Black, isort, flake8)
-
Commit messages are clear and descriptive
-
No unresolved merge conflicts
Development Setup
git clone https://github.com/your-username/semantica.git
cd semantica
pip install -e ".[dev]"
Code style: Black (formatting), isort (imports), flake8 (linting).
pytest # full test suite
black semantica/ tests/ # format
isort semantica/ tests/ # sort imports
flake8 semantica/ # lint
Code of Conduct
Please follow the Code of Conduct. Be respectful, patient, and constructive. All contributors are recognized in release notes and the GitHub contributors list.