fulldev-ui 0.4.14 → 0.4.16

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,57 +1,12 @@
-name: "Bug report"
-description: Report an issue
-title: '[bug]: '
-labels: ["bug"]
+name: 'Bug report'
+description: Report a bug or issue
+labels: ['bug']
 body:
-  - type: markdown
-    attributes:
-      value: |
-        ### Thanks for taking the time to create a bug report. Please search existing issues before submitting, as the issue may have already been addressed.
-
-  - type: textarea
-    id: bug-description
-    attributes:
-      label: Describe the bug
-      description: A clear and concise description of what the bug is. If you intend to submit a PR for this issue, describe how in the description.
-      placeholder: Bug description
-    validations:
-      required: true
-
-  - type: input
-    id: components-affected
-    attributes:
-      label: Affected component/components/documentation
-      description: Is this feature request relevant to any of the already existing components?
-      placeholder: ex. Button, Input...
-    validations:
-      required: false
-
   - type: textarea
-    id: reproduction
+    id: description
     attributes:
-      label: How to reproduce
-      description:  A step-by-step description of how to reproduce the bug.
-      placeholder: |
-        1. Go to '...'
-        2. Click on '....'
-        3. See error
+      label: Describe the bug or issue
+      description: Be clear and concise. Add logs and/or screenshots if applicable.
+      placeholder: Add your bug or issue description here...
     validations:
       required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Logs
-      description: "Please include browser console and server logs around the time this bug occurred. Optional if provided reproduction. Please try not to insert an image but copy paste the log text."
-      render: bash
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Before submitting
-      description: By submitting this issue, you agree to follow our [Contributing Guidelines](https://github.com/fulldotdev/ui/blob/main/CONTRIBUTING.md).
-      options:
-        - label: I've made research efforts and searched the documentation
-          required: true
-        - label: I've searched for existing issues
-          required: true

package/.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Add your site to our showcase
+    url: https://github.com/fulldotdev/ui/blob/main/CONTRIBUTING.md#showcase
+    about: Add your project to the showcase page and get featured on our website.
   - name: Get Help on Discord
     url: https://discord.gg/tdmUyH2YE4
     about: If you can't get something to work, open a forum post in our Discord server.

package/.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,12 @@
+name: 'Documentation'
+description: Issues and suggestions regarding documentation
+labels: ['docs']
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the issue or suggestion
+      description: Be clear and concise. Add logs and/or screenshots if applicable.
+      placeholder: Add your issue or suggestion description here...
+    validations:
+      required: true

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,39 +1,12 @@
-name: 'Feature request'
-description: Create a feature request for fulldev-ui
-title: '[feat]: '
-labels: ['area: request']
+name: 'Feature'
+description: Propose and discuss improvements
+labels: ['feature']
 body:
-  - type: markdown
-    attributes:
-      value: |
-        ### Thanks for taking the time to create a feature request! Please search existing issues before submitting, as the issue may have already been addressed.
-
   - type: textarea
-    id: feature-description
+    id: description
     attributes:
-      label: Feature description
-      description: Tell us about your feature request
-      placeholder: 'I think this feature would be nice to have because...'
-      value: 'Describe your feature request...'
+      label: Describe the feature
+      description: Be clear and concise. Add logs and/or screenshots if applicable.
+      placeholder: Add your feature description here...
     validations:
       required: true
-
-  - type: input
-    id: components-affected
-    attributes:
-      label: Affected component/components/documentation
-      description: Is this feature request relevant to any of the already existing components?
-      placeholder: ex. Button, Input...
-    validations:
-      required: false
-
-  - type: checkboxes
-    id: terms
-    attributes:
-      label: Before submitting
-      description: By submitting this request, you agree to follow our [Contributing Guidelines](https://github.com/fulldotdev/ui/blob/main/CONTRIBUTING.md).
-      options:
-        - label: I've made research efforts and searched the documentation
-          required: true
-        - label: I've searched for existing issues and PRs
-          required: true

package/.github/ISSUE_TEMPLATE/support.yml

@@ -0,0 +1,12 @@
+name: 'Support'
+description: Ask a question or request help
+labels: ['support']
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe your question or request
+      description: Be clear and concise. Add logs and/or screenshots if applicable.
+      placeholder: Add your question or request description here...
+    validations:
+      required: true

package/.github/pull_request_template.md

@@ -1,19 +1,7 @@
-# Changes/Additions being made
+# Changes/Additions being made and why
 
 Here give examples of the changes you've made in this pull request. Include an itemized list if you can. It'll help the reviewer
 
-## What's the context?
-
-What's the context for the changes? Are there any
-
-## Rationale behind the change or addition
-
-Why did you choose to make these changes? Were there any trade-offs you had to consider?
-
-## Test plan
-
-How do you know the changes are safe to ship to production?
-
 ## Screenshots (optional)
 
 If you made visual changes, what are the before an afters?

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,6 @@
+# Contributor Code of Conduct
+We accept and encourage everyone's contributions. It doesn't matter how you look, how you feel, where you're from, or anything like that. In fact, we won't bring it up, or ask.
+
+We are here to build great software, to learn, to grow, and to help each other. Maybe make some friends along the way.
+
+If you have any questions, please reach out!

package/CONTRIBUTING.md

@@ -55,11 +55,14 @@ The main source directory containing all the core files of the project.
 
 ### Setup
 
-1. Clone the Github repository in your designated folder:
+1. Fork the [repository](https://github.com/fulldotdev/ui) by clicking the fork button on the top right of the repository page.
+
+2. Clone the Github repository in your designated folder:
 
 ```bash
-git clone https://github.com/fulldotdev/ui.git
+git clone https://github.com/your-user-name/ui
 ```
+Ensure the cloned repo is named "ui" or replace "ui" with your fork's name.
 
 2. Enter the folder using `cd ui`.
 
@@ -69,7 +72,7 @@ git clone https://github.com/fulldotdev/ui.git
 git checkout -b my-new-branch
 ```
 
-1. Install the packages using pnpm:
+4. Install the packages using pnpm:
 
 ```bash
 pnpm install
@@ -77,7 +80,7 @@ pnpm install
 
 Make sure to do this in root to make sure you're using the local version of the component package.
 
-1. Run the development server:
+5. Run the development server:
 
 ```bash
 pnpm dev
@@ -85,10 +88,23 @@ pnpm dev
 
 ## Commit & Pull Requests
 
+### Pull Requests
+
+The simplest way to open a pull request with your changes is by using github web, after following the [setup guide](#setup) and commit your changes you have a contribute button at the top of your repo, after clicking that you should be able to make a pull request and go from there.
+
 ### Commit Conduct
 
 For a faster and easier review we advise you to use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary).
 
+## Showcase
+
+Have you used fulldev-ui to build a website? Add it to the showcase!
+
+1. Fork this repository.
+2. Add a screenshot of your site to the `public/showcase/` directory.
+3. Add your site to the `showcase` array at the top of `src/content/pages/overview/showcase.mdx`.
+4. Go to the forked repository on your Github and clicke the 'Contribute` button to make a Pull Request.
+
 ## Community / Contact
 
 Looking to share your work using fulldev-ui, regular talks about it or support join our [discord server](https://discord.gg/tdmUyH2YE4).

package/README.md

@@ -29,3 +29,4 @@ Copyright (c) 2024–present [Fulldev][fulldev]
 [docs]: https://ui.full.dev/
 [fulldev]: https://full.dev/
 [issues]: https://github.com/fulldotdev/ui/issues/
+[discord]: https://discord.gg/vXZqMbadm8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fulldev-ui",
-  "version": "0.4.14",
+  "version": "0.4.16",
   "description": "A component library built for Astro",
   "homepage": "https://ui.full.dev",
   "bugs": "https://github.com/fulldotdev/ui/issues",
@@ -22,6 +22,7 @@
     "build": "astro build",
     "check": "astro check",
     "preview": "astro preview",
+    "build:prod": "astro check && astro build",
     "astro": "astro",
     "test": "astro check && astro build && astro preview --host"
   },
@@ -35,13 +36,13 @@
     "./unocss": "./src/integration/unocss-preset.ts"
   },
   "dependencies": {
-    "@astrojs/mdx": "^3.1.6",
+    "@astrojs/mdx": "^3.1.7",
     "@astrojs/sitemap": "^3.1.6",
     "@astrolib/seo": "1.0.0-beta.6",
     "@iconify-json/tabler": "^1.2.3",
     "@radix-ui/colors": "^3.0.0",
     "@unocss/reset": "^0.62.4",
-    "astro": "^4.15.7",
+    "astro": "^4.15.8",
     "astro-live-code": "^0.0.3",
     "astro-pagefind": "^1.6.0",
     "astro-seo": "^0.8.4",
@@ -51,7 +52,7 @@
     "fs": "0.0.1-security",
     "radash": "^12.1.0",
     "remeda": "2.14.0",
-    "sass": "^1.79.1",
+    "sass": "^1.78.0",
     "tailwindcss": "^3.4.12",
     "typescript": "^5.6.2",
     "unocss": "^0.62.4",
@@ -64,6 +65,6 @@
     "prettier-plugin-astro": "0.14.1",
     "prettier-plugin-astro-organize-imports": "^0.4.9",
     "prettier-plugin-css-order": "^2.1.2",
-    "prettier-plugin-organize-imports": "^4.0.0"
+    "prettier-plugin-organize-imports": "^4.1.0"
   }
 }