semantica/docs/community.md at abde600a45775ccf3314e624f8b4c0e13c29f4cf

mirror of https://github.com/semantica-agi/semantica.git synced 2026-08-29 04:26:20 +00:00

Files

T

KaifAhmad1 9113ef3428 docs: premium overhaul of all reference pages and core docs

- Rewrote all 26 reference module pages: removed blockquote taglines and
  horizontal rule separators, added "What You Get" bullet summaries,
  added constructor/method parameter tables, expanded thin files
  (graph_store, triplet_store, visualization, provenance) with full API
  coverage, added backend comparison tables and real-world usage patterns
- Renamed Modules tab from "API Reference" and group from "Context &
  Knowledge" to "Context & Intelligence" in docs.json
- Fixed logo: copied "Semantica Logo.png" to web-safe semantica-logo.png
  and updated all 4 references in docs.json
- Improved core docs (index, modules, concepts, quickstart, installation,
  getting-started) with better fonts, bullet points, and complete module
  listings (mcp_server, evals, core, utils previously missing)
- Rewrote community pages (community, community-projects, contributing-guide,
  use-cases, architecture, faq, learning-more, glossary) with heading
  hierarchy fixes, expanded definitions, and better structure
- Fixed markdown linter warnings: MD036 bold-as-heading, MD001 heading
  skips, MD040 missing code fence language, MD032 blank lines around lists

2026-05-23 13:10:09 +05:30

3.5 KiB

Raw Blame History

title, description, icon

title	description	icon
Community	Get help, connect with contributors, and share what you build with Semantica.	users

Semantica is built in the open, with contributions from researchers, engineers, and practitioners across many domains. Whether you're filing a bug, sharing a project, or reviewing a PR — you're part of the ecosystem.

Get Help

File bug reports and feature requests with full context. Ask questions, share ideas, and discuss design decisions. Browse open contributions and submit your own. Report vulnerabilities privately — never in public issues.

Community Guidelines

We follow the Contributor Covenant Code of Conduct. The community is built on four principles:

Respect — treat everyone with kindness and patience, regardless of experience level
Inclusion — welcome all backgrounds, domains, and approaches
Collaboration — work toward better solutions together rather than competing on approaches
Learning — share knowledge openly, ask questions without hesitation, and help others grow

To report unacceptable behavior, open a GitHub issue with the [CoC] prefix. Every report is investigated.

Ways to Contribute

There's no single right way to contribute. Pick the path that fits your skills and time:

Code

Fix open bugs tagged good-first-issue
Add new features or integrations
Improve performance or refactor existing modules

Documentation

Fix typos and improve clarity in guides
Add examples to the API reference
Write domain-specific cookbook notebooks

Testing

Add coverage for untested modules
Reproduce and confirm reported bugs
Improve test reliability across platforms

Community

Answer questions in issues and discussions
Review open pull requests
Share your Semantica projects in GitHub Discussions

See the Contributing Guide for the full development workflow.

Stay Connected

GitHub — source code, releases, and the public roadmap
PyPI — package releases and download stats
Discord — real-time community chat
X / Twitter — announcements and release highlights

3.5 KiB Raw Blame History