added the contributing + code of conduct + revamped readme to adapt t…

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+ayushbhatt633@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+Poll_EC53MY42FN5NTX3JQNJJIY3LE7U
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing to Pollinations Hive - Hacktoberfest 2025 Edition
+
+Thank you for considering contributing to the Pollinations hive project during Hacktoberfest 2025! This is a flagship project of pollinations where we allot the projects created by the users and pollinations community up for a showcase. We are thrilled to have you join our community and help us enhance this exciting project. Your contributions are vital to improving our project and expanding its capabilities.
+
+## Hacktoberfest 2025 Timeline
+
+Hacktoberfest 2025 officially runs throughout **October 2025**. To have your Pull Requests (PRs) count towards your Hacktoberfest badge, they must be opened between **October 1st and October 31st, 2025**.
+
+## How to Contribute
+
+We have multiple projects under the `pollinations/hive` umbrella, and each project has its own set of issues. To make a meaningful contribution:
+
+
+### 1. Explore Projects and Issues
+
+Before you start, please refer to the main `README.md` file of the `pollinations/hive` repository. It lists all the insights and provides an overview. There are dedicated issues from versatile topics under the repository [Issues](https://github.com/pollinations/hive/issues) section.
+
+**Important for Hacktoberfest:** Look for issues specifically tagged with `hacktoberfest`. Only PRs addressing these tagged issues will be considered for your Hacktoberfest badge. While you are welcome to resolve other issues, they will not count towards the Hacktoberfest event.
+
+### 2. Understand the Issue and Build an MVP
+
+Once you've selected an issue (especially a `hacktoberfest` tagged one), take the time to thoroughly understand its requirements. For code contributions, focus on building a **Minimum Viable Product (MVP)** that addresses the core problem or implements the key feature described in the issue.
+
+### 3. Documentation Contributions
+
+We are in profound need of members who can help enhance our documentation. If you possess experience in data science, machine learning, LLMs (Large Language Models), or Stable Diffusion, your insights will be invaluable. You can contribute by:
+
+- Improving existing documentation to be clearer and more comprehensive.
+- Writing new guides or tutorials that explain complex concepts or workflows.
+- Providing practical examples of how to use different features of pollinations.
+- Creating explanations for the underlying data science and ML principles.
+
+### 4. Code Contributions
+
+If you're interested in coding, we enthusiastically welcome contributions in the following areas:
+
+- **Bug Fixes:** Identifying and resolving issues that hinder the project's functionality.
+- **Feature Enhancements:** Adding new capabilities or improving existing ones.
+- **Code Optimization:** Refactoring and improving the efficiency, readability, and maintainability of the codebase.
+- **New Functionalities:** Developing innovative features that expand the project's scope.
+
+### How to earn the "Pollinations Contributor" badge
+To earn this badge, contributors need to:
+1. Submit at least one meaningful pull request that gets merged into the repository.
+2. Ensure the pull request follows the project's contribution guidelines.
+3. The contribution can be related to bug fixes, feature additions, or documentation improvements.
+
+Once your pull request is merged, you will automatically be issued the badge!
+
+
+## Getting Started
+
+1.  **Fork the Repository**: Click on the "Fork" button at the top right of the repository page to create your own copy of the project under your GitHub account.
+
+2.  **Clone Your Fork**: Clone your forked repository to your local machine. Replace `your-username` with your GitHub username.
+    ```bash
+    git clone https://github.com/your-username/hive.git
+    ```
+
+3.  **Create a Branch for Your Work**: Create a new branch for your specific contribution. It's good practice to name your branch related to the issue you're addressing (e.g., `fix/bug-description` or `feat/new-feature-name`).
+    ```bash
+    git checkout -b my-feature-branch
+    ```
+
+4.  **Make Your Changes**: Implement your changes, focusing on the MVP for the chosen issue.
+
+5.  **Commit Your Changes**: Commit your changes with a clear and descriptive message.
+    ```bash
+    git commit -m "feat: Implement new feature for issue #XYZ"
+    ```
+    (Replace "XYZ" with the actual issue number)
+
+6.  **Push Your Changes**: Push your local branch with your changes to your forked repository on GitHub.
+    ```bash
+    git push origin my-feature-branch
+    ```
+
+7.  **Create a Pull Request (PR)**: Go to the original `pollinations/pollinations/hive` repository on GitHub. You will see an option to create a Pull Request from your recently pushed branch.
+    *   **Crucially:** Link your PR to the original issue it addresses (e.g., "Closes #XYZ" in your PR description).
+    *   Ensure your PR clearly explains the changes you've made and how they resolve the issue.
+
+## Guidelines
+
+-   **Follow Coding Style:** Adhere to the existing coding style and conventions used within the project you are contributing to. Consistency is key!
+-   **Clear Commit Messages:** Write clear, concise, and descriptive commit messages that explain the purpose of your changes.
+-   **Well-Documented Changes:** Ensure your code is well-commented where necessary, and if you're making documentation contributions, strive for clarity and accuracy.
+-   **Test Your Changes:** If applicable, write and run tests to ensure your changes work as expected and don't introduce new bugs.
+
+Thank you for your valuable contributions during Hacktoberfest 2025! Together, we can make the `pollinations/hive` project a powerful and valuable resource for the community. Happy Hacking!

README.md

@@ -1,8 +1,14 @@
 # 🐝 Pollinations Hive
-<!-- Placeholder for deployment simplification changes -->
+
 
 Welcome to Pollinations Hive - a revolutionary repository where AI meets collaborative development! This project showcases a unique approach to software development where applications are created and modified entirely through AI assistance.
 
+## 📢 Hacktoberfest News
+
+- **Hacktoberfest 2025 is here!**  
+  If you're participating, please check out our [Code of Conduct](./CODE_OF_CONDUCT.md) and [Contributing Guidelines](./CONTRIBUTING.md) before submitting your PRs.
+- For event PRs, look for issues tagged with `hacktoberfest` in our [issue tracker](https://github.com/pollinations/hive/issues) and join the community effort!
+
 ## 📱 Available Apps
 
 | App | Source | Last Updated |