ruby-ui
diff --git a/‎.dockerignore‎
Lines changed: 60 additions & 0 deletions b/‎.dockerignore‎
Lines changed: 60 additions & 0 deletions
diff --git a/‎.github/CODEOWNERS‎
Lines changed: 1 addition & 1 deletion b/‎.github/CODEOWNERS‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/dependabot.yml‎
Lines changed: 35 additions & 9 deletions b/‎.github/dependabot.yml‎
Lines changed: 35 additions & 9 deletions
diff --git a/‎.github/workflows/ci.yml‎
Lines changed: 70 additions & 15 deletions b/‎.github/workflows/ci.yml‎
Lines changed: 70 additions & 15 deletions
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 44 additions & 40 deletions b/‎CONTRIBUTING.md‎
Lines changed: 44 additions & 40 deletions
@@ -0,0 +1,60 @@
+# Build context for docs/Dockerfile is the monorepo root.
+# See https://docs.docker.com/engine/reference/builder/#dockerignore-file
+
+# Ignore git directory.
+/.git/
+/.gitignore
+
+# Ignore bundler config in either subproject.
+/gem/.bundle
+/docs/.bundle
+
+# Ignore environment files.
+/docs/.env*
+/gem/.env*
+
+# Ignore default key files.
+/docs/config/master.key
+/docs/config/credentials/*.key
+
+# Ignore logs and tempfiles.
+/docs/log/*
+/docs/tmp/*
+!/docs/log/.keep
+!/docs/tmp/.keep
+/docs/tmp/pids/*
+!/docs/tmp/pids/.keep
+
+# Ignore storage (uploaded files in dev and SQLite databases).
+/docs/storage/*
+!/docs/storage/.keep
+/docs/tmp/storage/*
+!/docs/tmp/storage/.keep
+
+# Ignore assets.
+/docs/node_modules/
+/docs/app/assets/builds/*
+!/docs/app/assets/builds/.keep
+/docs/public/assets
+
+# Ignore gem build artifacts.
+/gem/pkg/
+/gem/node_modules/
+/gem/tmp/
+/gem/.ruby-lsp/
+
+# Ignore CI service files.
+/.github
+
+# Ignore Kamal files.
+/docs/config/deploy*.yml
+/docs/.kamal
+
+# Ignore development files.
+/gem/.devcontainer
+/docs/.devcontainer
+
+# Ignore Docker-related files.
+/.dockerignore
+/docs/.dockerignore
+/docs/Dockerfile*
@@ -1 +1 @@
-*       @cirdes
+*       @cirdes @stephannv
@@ -1,12 +1,38 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for more information:
 # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-# https://containers.dev/guide/dependabot
-
 version: 2
 updates:
- - package-ecosystem: "devcontainers"
-   directory: "/"
-   schedule:
-     interval: weekly
+  # Gem
+  - package-ecosystem: "bundler"
+    directory: "/gem"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+
+  # Docs (Rails app)
+  - package-ecosystem: "bundler"
+    directory: "/docs"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+  - package-ecosystem: "npm"
+    directory: "/docs"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+
+  # GitHub Actions (root)
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+    open-pull-requests-limit: 5
+
+  # Devcontainers
+  - package-ecosystem: "devcontainers"
+    directory: "/gem"
+    schedule:
+      interval: weekly
+  - package-ecosystem: "devcontainers"
+    directory: "/docs"
+    schedule:
+      interval: weekly
@@ -1,31 +1,86 @@
 name: CI
 
 on:
+  pull_request:
   push:
     branches:
       - main
-  pull_request:
 
 jobs:
-  build:
-    name: Ruby ${{ matrix.ruby }}
+  gem:
+    name: Gem (Ruby ${{ matrix.ruby }})
     runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: gem
     strategy:
       fail-fast: false
       matrix:
         ruby: ["3.3", "3.4"]
-
     steps:
-    - uses: actions/checkout@v4
-    - name: Set up Ruby
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby }}
-        bundler-cache: true
-        rubygems: latest
+      - uses: actions/checkout@v4
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+          rubygems: latest
+          working-directory: gem
+      - name: Run tests
+        run: bundle exec rake test
+      - name: Run linter
+        run: bundle exec rake standard
 
-    - name: Run tests
-      run: bundle exec rake test
+  docs:
+    name: Docs (Rails)
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: docs
+    steps:
+      - uses: actions/checkout@v6
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          bundler-cache: true
+          working-directory: docs
+      - name: Install pnpm
+        uses: pnpm/action-setup@v5
+        with:
+          version: 10.8.0
+          run_install: false
+      - name: Setup Node
+        uses: actions/setup-node@v6
+        with:
+          node-version-file: docs/.node-version
+          cache: pnpm
+          cache-dependency-path: docs/pnpm-lock.yaml
+      - name: Install dependencies
+        run: pnpm install
+      - name: Lint
+        run: bundle exec standardrb
+      - name: Run tests
+        run: bin/rails db:test:prepare test
 
-    - name: Run linter
-      run: bundle exec rake standard
+  docker-build:
+    name: Docker build (Devcontainer)
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - uses: actions/checkout@v6
+      - name: Login to GitHub Container Registry
+        uses: docker/login-action@v4
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Build and push devcontainer image
+        uses: devcontainers/ci@v0.3
+        with:
+          imageName: ghcr.io/ruby-ui/web-devcontainer
+          cacheFrom: ghcr.io/ruby-ui/web-devcontainer
+          subFolder: docs
+          push: always
@@ -1,62 +1,66 @@
 # Contributing to RubyUI
 
-Thank you for your interest in contributing to RubyUI! This document provides guidelines for contributing to the project.
+Thanks for your interest in contributing! This repository is a monorepo containing two sibling projects:
 
-## Development Setup
+- [`gem/`](gem/) — the `ruby_ui` gem published to rubygems.org.
+- [`docs/`](docs/) — the Rails app that powers https://rubyui.com.
 
-We recommend using the provided devcontainer to set up your development environment. This ensures a consistent environment for all contributors.
+The big advantage of the monorepo: **a single PR can touch both the component and the docs example**. The docs app consumes the local gem via `path: "../gem"`, so any change in `gem/lib/ruby_ui/` is reflected in the running site immediately.
 
-1. Make sure you have Docker
-2. Clone the repository
-3. Open the project in you editor
-4. Select "Reopen in Container" if you are using VSCode or any other method to run the project
-5. The devcontainer will set up everything you need to start developing
+## Development setup
 
-## Contribution Process
+We recommend using the devcontainer for either subproject (each has its own `.devcontainer/`).
 
-1. Fork the repository
-2. Create a new branch for your changes
-3. Make your changes
-4. Run tests to ensure your changes don't break existing functionality: `bundle exec rake test`
-5. Run the linter to ensure consistent code formatting: `bundle exec rake standard`
-6. Submit a Pull Request to the main repository
-
-## Focus Areas
-
-We prioritize:
-- Improving existing components rather than adding new ones
-- Preserving the shadcn look and feel
-- Enhancing documentation
-- Fixing bugs
+```bash
+git clone git@github.com:ruby-ui/ruby_ui.git
+cd ruby_ui
+
+# For gem-only work:
+cd gem
+bundle install
+bundle exec rake
+
+# For docs work:
+cd docs
+bundle install
+pnpm install
+bin/dev
+```
 
-## Code Standards
+## Workflow
 
-We follow Standard Ruby conventions for code style. The CI pipeline runs `standard` to ensure consistent code formatting.
+1. Fork and create a feature branch.
+2. Make your changes:
+   - Component or generator changes → `gem/lib/...`, with tests in `gem/test/...`.
+   - Documentation page changes → `docs/app/views/docs/...` or `docs/app/components/...`.
+   - If a component change affects how it's documented, update **both** in the same PR.
+3. Run the relevant test suites:
+   - `cd gem && bundle exec rake` (tests + standardrb).
+   - `cd docs && bin/rails test` and `bundle exec standardrb`.
+4. Open a Pull Request against `main`. Use the PR template and prefix the title with a category in brackets, e.g. `[Feature] Add new variant to Button`.
 
-## Testing
+## Focus areas
 
-While we don't have specific test coverage requirements, all contributions should include tests for new functionality and ensure existing tests pass.
+We prioritize:
 
-## Documentation
+- Improving existing components rather than adding new ones.
+- Preserving the shadcn look and feel.
+- Enhancing documentation.
+- Fixing bugs.
 
-If your changes include new components, modify how components should be used, or add new behaviors, it is highly recommended to also open a PR on the [ruby-ui/web](https://github.com/ruby-ui/web) repository. This ensures the documentation website stays up-to-date with the latest component changes.
+## Code style
 
-### Installing Documentation Files
+- Ruby: [Standard Ruby](https://github.com/standardrb/standard) — `bundle exec standardrb --fix` to auto-fix.
+- JavaScript: kept minimal; Stimulus controllers live alongside the components they belong to.
 
-RubyUI includes documentation files for each component that can be installed into your Rails application. These files are located at `lib/ruby_ui/{component}/{component}_docs.rb` and provide usage examples for each component.
+## Documentation files
 
-To install the documentation files:
+The gem ships per-component `*_docs.rb` files (rendering examples) under `gem/lib/ruby_ui/<component>/`. Consumers of the gem can install these into their own Rails app with:
 
 ```bash
 bin/rails g ruby_ui:install:docs
 ```
 
-To overwrite existing documentation files:
-
-```bash
-bin/rails g ruby_ui:install:docs --force
-```
-
-This will copy the documentation files to `app/views/docs/` in your Rails application.
+Within this monorepo, the **docs app does not run that generator** — it has its own richer view implementations in `docs/app/views/docs/` and `docs/app/components/docs/`. If you change a component's API, update the relevant view in `docs/app/views/docs/<component>.rb` to keep the documentation site accurate.
 
-Thank you for contributing to make RubyUI better! 
+Thanks for helping make RubyUI better!