chore: prepare dashboard for open source

Author: lius-new

.dockerignore

@@ -0,0 +1,7 @@
+node_modules
+dist
+.git
+.github
+.tanstack
+docker-compose*.yml
+*.log

.env.example

@@ -0,0 +1,17 @@
+# Simprint Dashboard example environment
+
+# Dashboard identifier used as the first URL segment.
+# Example access path: https://your-domain.com/{VITE_DASHBOARD_IDENTIFIER}/
+VITE_DASHBOARD_IDENTIFIER=cp-8f2k9m4x
+
+# Console server origin only. The frontend appends /api/v1 automatically.
+# Development example: http://localhost:40043
+VITE_API_BASE_URL=http://localhost:40043
+
+# Optional extension sync service base URL.
+# Development example: http://localhost:8080
+# Bundled Nginx proxy example: /extension-sync
+VITE_EXTENSION_SYNC_BASE_URL=http://localhost:8080
+
+# Runtime port used by the Docker deploy bundle.
+DASHBOARD_PORT=8080

.github/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
+.
+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
+
+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.

.github/CONTRIBUTING.md

@@ -0,0 +1,101 @@
+# Contributing to Shadcn-Admin
+
+Thank you for considering contributing to **shadcn-admin**! Every contribution is valuable, whether it's reporting bugs, suggesting improvements, adding features, or refining README.
+
+## Table of Contents
+
+1. [Getting Started](#getting-started)
+2. [How to Contribute](#how-to-contribute)
+3. [Code Standards](#code-standards)
+4. [Pull Request Guidelines](#pull-request-guidelines)
+5. [Reporting Issues](#reporting-issues)
+6. [Community Guidelines](#community-guidelines)
+
+---
+
+## Getting Started
+
+1. **Fork** the repository.
+2. **Clone** your fork:
+
+   ```bash
+   git clone https://github.com/your-username/shadcn-admin.git
+   ```
+
+3. **Install dependencies:**
+
+   ```bash
+   pnpm install
+   ```
+
+4. **Run the project locally:**
+
+   ```bash
+   pnpm dev
+   ```
+
+5. Create a new branch for your contribution:
+
+   ```bash
+   git checkout -b feature/your-feature
+   ```
+
+---
+
+## How to Contribute
+
+- **Feature Requests:** Open an issue or start a discussion to discuss the feature before implementation.
+- **Bug Fixes:** Provide clear reproduction steps in your issue.
+- **Documentation:** Improvements to the documentation (README) are always appreciated.
+
+> **Note:** Pull Requests adding new features without a prior issue or discussion will **not be accepted**.
+
+---
+
+## Code Standards
+
+- Follow the existing **ESLint** and **Prettier** configurations.
+- Ensure your code is **type-safe** with **TypeScript**.
+- Maintain consistency with the existing code structure.
+
+> **Tips!** Before submitting your changes, run the following commands:
+
+```bash
+pnpm lint && pnpm format && pnpm knip && pnpm build
+```
+
+---
+
+## Pull Request Guidelines
+
+- **Follow the [PR Template](./PULL_REQUEST_TEMPLATE.md):**
+  - Description
+  - Types of changes
+  - Checklist
+  - Further comments
+  - Related Issue
+- Ensure your changes pass **CI checks**.
+- Keep PRs **focused** and **concise**.
+- Reference related issues in your PR description.
+
+---
+
+## Reporting Issues
+
+- Clearly describe the issue.
+- Provide reproduction steps if applicable.
+- Include screenshots or code examples if relevant.
+
+---
+
+## Community Guidelines
+
+- Be respectful and constructive.
+- Follow the [Code of Conduct](./CODE_OF_CONDUCT.md).
+- Stay on topic in discussions.
+
+---
+
+Thank you for helping make **shadcn-admin** better! 🚀
+
+If you have any questions, feel free to reach out via [Discussions](https://github.com/satnaing/shadcn-admin/discussions).

.github/FUNDING.yml

@@ -0,0 +1,14 @@
+github: [satnaing]
+buy_me_a_coffee: satnaing
+
+# patreon: # Replace with a single Patreon username
+# open_collective: # Replace with a single Open Collective username
+# ko_fi: # Replace with a single Ko-fi username
+# tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+# community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+# liberapay: # Replace with a single Liberapay username
+# issuehunt: # Replace with a single IssueHunt username
+# lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+# polar: # Replace with a single Polar username
+# thanks_dev: # Replace with a single thanks.dev username
+# custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Shadcn-Admin Discussions
+    url: https://github.com/satnaing/shadcn-admin/discussions
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/✨-feature-request.md

@@ -0,0 +1,19 @@
+---
+name: "✨ Feature Request"
+about: Suggest an idea for improving Shadcn-Admin
+title: "[Feature Request]: "
+labels: enhancement
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/🐞-bug-report.md

@@ -0,0 +1,27 @@
+---
+name: "\U0001F41E Bug report"
+about: Report a bug or unexpected behavior in Shadcn-Admin
+title: "[BUG]: "
+labels: bug
+assignees: ""
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,27 @@
+## Description
+
+<!-- A clear and concise description of what the pull request does. Include any relevant motivation and background. -->
+
+## Types of changes
+
+<!-- What types of changes does your code introduce to AstroPaper? Put an `x` in the boxes that apply -->
+
+- [ ] Bug Fix (non-breaking change which fixes an issue)
+- [ ] New Feature (non-breaking change which adds functionality)
+- [ ] Others (any other types not listed above)
+
+## Checklist
+
+<!-- Please follow this checklist and put an x in each of the boxes, like this: [x]. You can also fill these out after creating the PR. This is simply a reminder of what we are going to look for before merging your code. -->
+
+- [ ] I have read the [Contributing Guide](https://github.com/satnaing/shadcn-admin/blob/main/.github/CONTRIBUTING.md)
+
+## Further comments
+
+<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
+
+## Related Issue
+
+<!-- If this PR is related to an existing issue, link to it here. -->
+
+Closes: #<!-- Issue number, if applicable -->

.github/workflows/ci.yml

@@ -0,0 +1,41 @@
+name: Continuous Integration
+
+on:
+  push:
+    branches:
+      - main
+
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  install-lint-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Install pnpm
+        run: npm install -g pnpm
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Lint the code
+        run: pnpm lint
+
+      # - name: Analyze unused files and dependencies
+      #   run: pnpm knip
+
+      - name: Run Prettier check
+        run: pnpm format:check
+
+      - name: Build the project
+        run: pnpm build