Landing Page V2

Author: AttAditya

.github/CODEOWNERS

@@ -0,0 +1,8 @@
+.github/ @AttAditya
+ci/ @AttAditya
+scripts/ @AttAditya
+.gitignore @AttAditya
+dev.sh @AttAditya
+config.sh @AttAditya
+LICENSE @AttAditya
+

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,18 @@
+# Code of Conduct
+
+## Our Standards
+- Be respectful and inclusive
+- Accept constructive feedback
+- Focus on what is best for the community
+
+## Unacceptable Behavior
+- Harassment, trolling, or personal attacks
+- Discrimination of any kind
+- Publishing private information without consent
+
+## Enforcement
+Project maintainers may remove or edit content and take action against contributors who violate these rules.
+
+## Reporting
+Report issues to: [attachment.aditya@gmail.com](mailto:attachment.aditya@gmail.com)
+

.github/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contribution Guidelines
+
+## Prerequisites
+
+This ecosystem relies on the following tools and libraries:
+- Node.js and npm
+
+
+## Getting Started
+
+Contributions to the ecosystem are welcome and encouraged! Here's how you can get started:
+
+- Fork the repository
+- Clone your forked repository
+- Create a new branch
+  - `feat/<feature-name>` for new features
+  - `fix/<issue-name>` for bug fixes
+  - `docs/<topic>` for documentation updates
+- Make your changes
+- Commit your changes
+  - Add a message that explains the commit
+  - Preferably, make small and focused commits
+  - Make as many commits as you need, as long as sensible
+  - Avoid weird messages like "stuff" (it's reserved for [AttAditya](https://github.com/AttAditya) only, since he's the only one maintaining the repository and can understand what "stuff" means since he wrote the code)
+- Push your changes to your forked repository
+- Open a pull request to the main repository
+  - Start with the PR template
+  - Provide a clear description of your changes and the problem they solve
+  - Reference any related issues (e.g., "Fixes `#<issue-number>`")
+  - Be responsive to feedback and make necessary revisions
+- Celebrate your contribution to the ecosystem!
+
+## Development Environment
+
+This project uses a source file `dev.sh` to set up the development environment. To get started, follow these steps:
+
+```sh
+# Clone the repository
+git clone https://github.com/<your-username>/<repository-name>.git
+cd <repository-name>
+
+# Source the development environment
+source dev.sh
+
+# Setup and run
+dev setup
+dev run
+```
+
+### Available Commands
+
+Use the `dev` command to view and understand the available commands. Here are important commands:
+
+- `dev setup`: Sets up the development environment, including installing dependencies and configuring necessary tools.
+- `dev run`: Runs the main application or specific components for testing and development purposes.
+- `dev fmt`: Formats the codebase according to the project's coding standards.
+- `dev build`: Builds the project for production.
+- `dev start`: Starts the project in production mode.
+
+

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: [AttAditya]
+

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,37 @@
+name: Bug Report
+description: Report a bug
+title: "[Bug]: "
+labels: ["bug"]
+
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Tell more about the bug you encountered.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: If you are able to reproduce the bug, please provide the steps to do so.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should have happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / Screenshots
+      description: Please include any relevant logs or screenshots.
+      render: shell
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,6 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Additional Support
+    url: mailto:attachment.aditya@gmail.com
+    about: In case GitHub features are not sufficient, please reach out to directly, happy to help.
+

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,20 @@
+name: Feature Request
+description: Suggest a feature
+title: "[Feature]: "
+labels: ["enhancement"]
+
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Tell more about the feature you'd like to see.
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Is there any additional context or information that would be helpful to know about this feature?
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,25 @@
+# Pull Request Title
+
+## Description
+
+Briefly describe what this PR does and why.
+
+## Changes
+
+- List the main changes made in this PR.
+- This should be summary like bullet points
+
+## Previews
+
+- Not applicable / Screenshots / GIFs / Videos
+
+## Type of Change
+
+- `Fix` / `Feature` / `Refactor` / `Documentation` / `Other` (please describe)
+- `Breaking Change` / `Non-breaking Change`
+
+## Related Issues
+
+- Related Issues: None / #issue_number
+- Related PRs: None / #pr_number
+

.github/SECURITY.md

@@ -0,0 +1,14 @@
+# Security Policy
+
+## Reporting a Vulnerability
+If you discover a security vulnerability, please report it privately.
+
+- Email: [attachment.aditya@gmail.com](mailto:attachment.aditya@gmail.com)
+- Do NOT open a public issue
+
+## Response
+Acknowledgement receipt within a reasonable time and work on a fix.
+
+## Disclosure
+Please allow time to fix the issue before public disclosure.
+

.github/SUPPORT.md

@@ -0,0 +1,13 @@
+# Support
+
+## Getting Help
+- Check the README and docs first
+- Search existing issues
+
+## Ask for Help
+- Open an issue for bugs or feature requests
+  - Only open issues that are not already covered by existing issues
+
+## Response Time
+Maintainers will respond as time permits.
+