chore: add Community contributions directory (#1749)

* chore: create community space for demo apps etc

* chore: add changeset

---------

Co-authored-by: Sumit Saurabh <sumitm4pro@192.168.1.9>

Author: sumitsaurabh927

.changeset/stale-foxes-rest.md

@@ -0,0 +1,17 @@
+---
+"@compiler/demo-next": patch
+"@replexica/integration-directus": patch
+"replexica": patch
+"@replexica/sdk": patch
+"lingo.dev": patch
+"@lingo.dev/_compiler": patch
+"@lingo.dev/_locales": patch
+"@lingo.dev/_logging": patch
+"@lingo.dev/compiler": patch
+"@lingo.dev/_react": patch
+"@lingo.dev/_sdk": patch
+"@lingo.dev/_spec": patch
+"docs": patch
+---
+
+create a new space for community contributions like demo apps etc

community/README.md

@@ -0,0 +1,42 @@
+# Lingo.dev Community Contributions
+
+Welcome to the official community space of Lingo.dev!
+
+This directory is a dedicated space for community-driven projects, demo applications, and integrations that showcase what can be built with Lingo.dev.
+
+**Note:** The code in this directory is for examples and educational purposes. It exists separately from the core Lingo.dev product source code. If you want to contribute to the core product (like the CLI, compiler etc), you can go through our or open new one.
+
+## 📂 What belongs here?
+
+We encourage you to submit projects that help others learn and build. Ideal contributions include:
+
+* **Demo Apps:** Full-stack or frontend applications (e.g., React, Next.js) demonstrating specific Lingo.dev features.
+* **Integrations:** Scripts or plugins that connect Lingo.dev with other tools in your stack.
+* **Starters/Boilerplates:** Minimal setups to help new users get up and running quickly.
+* **Tutorial Code:** Source code companion files for blogs or video tutorials.
+
+## 🚀 How to Contribute
+
+We love seeing what you build! To contribute to this directory:
+
+1. **Fork & Branch:** Fork the repository and create a new branch for your contribution.
+2. **Create a Directory:** Inside `community/`, create a new folder for your project. Please use `kebab-case` for naming (e.g., `community/react-todo-demo`).
+3. **Add Documentation:** Every contribution **must** have its own `README.md` inside its folder explaining:
+    * What the project does.
+    * Prerequisites (e.g., Node version, API keys).
+    * How to run it locally.
+4. **Submit a PR:** Open a Pull Request targeting the `main` branch. Please tag your PR with `community-submission` so our team can spot it easily.
+5. Don't forget to add a changeset in your PRs as mentioned in our [contributor's guide](https://github.com/lingodotdev/lingo.dev/blob/main/CONTRIBUTING.md).
+
+## 💬 Join the Discussion
+
+If you have an idea for a contribution but aren't sure where to start, or if you want to show off your work:
+
+* **Discord:** Join our [Discord server](https://lingo.dev/go/discord) to interact with our fellow community members.
+* **Issues:** You can also open a GitHub Issue with the tag `community-submission-idea` to discuss potential contributions.
+
+## ⚖️ License & Disclaimer
+
+Code in the `community/` directory is contributed by the community. While the Lingo.dev team reviews submissions, these projects are maintained by their respective authors.
+
+By contributing, you agree that your code will be licensed under the same terms as the repository.