A collection of checkbox implementations using different frameworks and approaches.
- Multiple implementation examples:
- Datastar
- React
- Vue.js
- Svelte
- Alpine.js
- Vanilla JavaScript
- Hyperscript
- CSS Only
- jQuery
- Stimulus
- Syntax highlighted collapsible code snippets
- Performance metrics for each implementation
npm install
npm run dev# Run these commands in sequence:
npm run build # Build the project
npm run generate-stats # Generate performance metrics from dist/Bundle sizes and Code Complexity are always measured. Vibe Complexity requires a Gemini API key. Without one, existing Vibe Complexity scores are preserved. To refresh Vibe Complexity, create a .env file with your key:
# Get your key from https://aistudio.google.com/apikey
GEMINI_API_KEY=your_key_here-
Create Framework Files
- Create a new directory in
src/componentswith your framework name - Add two required files:
src/your-framework/your-framework<.tsx/jsx/etc>- The checkbox implementationsrc/your-framework/your-framework-container.astro- The display wrapper
- Create a new directory in
-
Add Framework Logo
-
Add your framework's logo as an SVG file to
src/assets/logos/ -
Name it consistently (e.g.,
your-framework.svg) -
Example logo import in your container:
--- import yourFrameworkLogo from "../../assets/logos/your-framework.svg"; // ... other imports ---
-
-
Update Framework Configuration
-
Add the framework to
src/config/frameworks.ts:export const FRAMEWORKS = { yourFramework: { displayName: "Your Framework", // Name shown in the UI }, // ... existing frameworks };
-
-
Add Framework Integration
-
Install framework dependencies:
npm install @astrojs/your-framework your-framework
-
Update
config/app/astro.tsto add the framework integration:import yourFramework from '@astrojs/your-framework'; export default defineConfig({ integrations: [ // ... existing integrations yourFramework(), ], });
-
-
Update Test Page
-
Modify
src/pages/test/[framework].astroto include your framework:--- import YourFramework from "../../components/your-framework/your-framework"; // ... existing imports --- <div class="framework-container"> {/* Add your framework */} {frameworkId === "yourFramework" && <YourFramework client:only="your-framework" />} {/* ... existing frameworks */} </div>
-
-
Add Framework Stats
-
Update
src/config/stats.tsif your framework needs special handling:SUPPORTED_EXTENSIONS: [ ".tsx", ".jsx", ".astro", ".vue", ".svelte", ".your-extension" // Add if needed ],
-
Generate framework stats:
npm run generate-stats
-
At this point, you could open a PR. For full framework integration, see the Astro Framework Integration Guide. This usually involves modifying the config/app/astro.ts file to add the framework and its configuration.
If you want to generate performance metrics for your new implementation, see the Generate performance metrics section.
- If
generate-statsfails, ensure:- Your GEMINI_API_KEY is valid and properly set in
.env(only if refreshing Vibe Complexity) - You've run
npm run buildbefore runningnpm run generate-stats - Built test routes must not load implementation JavaScript from remote hosts (no jsDelivr/unpkg allowlist)
- You have Node.js 26+ installed
- Your GEMINI_API_KEY is valid and properly set in
- For framework integration issues, check:
- Required dependencies are installed
- Framework is properly configured in config/app/astro.ts
- TypeScript types are updated if needed
- For stats generation issues, verify your implementation file matches the expected extension in
SUPPORTED_EXTENSIONSwithinsrc/config/stats.ts
src/
├── components/
│ ├── react/
│ │ ├── ReactNestedCheckboxes.tsx
│ │ └── ReactContainer.astro
│ ├── alpine/
│ │ ├── alpine.astro
│ │ └── AlpineContainer.astro
│ ├── [other-frameworks]/ # Similar structure for other frameworks
│ │ └── ...
│ └── CodeBlock.astro # Shared code display component
├── layouts/
│ └── Layout.astro # Base layout
└── pages/
└── index.astro # Main page
- Add more frameworks (Angular, Solid.js)
- Add performance comparisons
- Create interactive playground
- Add more complex checkbox scenarios
Each framework implementation is evaluated on three metrics:
- Measured in kibibytes (KiB)
- Calculated from built isolated
/test/{framework}artifacts afternpm run build - Uses a separate build graph for demos, excluding shared gallery controls
- Includes first-party built chunks and inline JavaScript (no remote CDN runtimes)
- Represents normalized gzip-compressed implementation JavaScript above
/test/baseline - Lower scores are better
- Deterministic 0-100 composite of size, logic, reactive, nesting, and vocabulary
- Calculated from the actual implementation source shown on each card
- The
logicaxis reuses Decision Points (branch/template/selector counts) - Higher scores indicate more implementation surface area
- AI-judged implementation complexity on a 0-100 scale
- Uses the same implementation source as Code Complexity
- Requires a Gemini API key to refresh
- Existing Vibe Complexity scores are preserved when no key is available
See METHODOLOGY.md for counting rules, normalization, and reproduction steps.
The metrics are normalized using z-scores to provide relative performance indicators, displayed as colored badges:
- 🟢 Excellent (z-score < -1.5)
- 🟢 Good (z-score < -0.5)
- 🟡 Average (-0.5 ≤ z-score < 0.5)
- 🟠 Below Average (0.5 ≤ z-score < 1.5)
- 🔴 Poor (z-score ≥ 1.5)
The site deploys through Vercel's Git integration when a CI-approved PR merges to main. Only pushed branches named preview/** build a Vercel Preview; every other branch builds nothing.
Live site: www.checkboxes.xyz
Check out the live demo at checkboxes.xyz
This project is licensed under the MIT License - see the LICENSE file for details.
- Node.js 26+
- npm
- A Gemini API key (optional; only needed to refresh Vibe Complexity)