This project started out as Breeze Components, then it was renamed to Cucumber Components on Sep 4, 2023. Logo was designed by me with Inkscape based on cucumber icons ideas from https://www.flaticon.com/free-icons/cucumber, logo font is Input Mono. Reason for renaming is writing cc-button is a bit easier than breeze-button.

Why build a Web Components collection when there are many battle-tested Web Components collections already?

• A project to dive deep into web accessibility.
• Helps develop a mindset from both component author and component consumer.
• A learning experience and an opportunity to gain a deeper understanding of web components best practices.
• It's fun as you're writing HTML/CSS/JavaScript!

Why go with vanilla Web Components?

• Vanilla Web Components can take you all the way if you're just building components collection to be consumed by other projects.
• A better way to play around web components specs and trying out new ideas.
• Provide a low barrier for entry, making it easier for developers to contribute to component collections.
• Minimize the bundled size of each component.
• "The beauty of zero-dependencies!" (#UseThePlatform).

How to contribute

1. Fork and Clone This Repo.

git clone https://github.com/heybran/cucumber-components.git

2. Install dev dependencies

Web Components dev dependencies

npm install

Docs dependencies

cd docs && npm install

3. Creat a component folder at ./src/components.

Structure:

── password-field
   ├── password-field.css
   ├── password-field.html
   └── password-field.js

4. Add new component to DOCS ./docs/src/components/demo/ComponentPreview.svelte. This is to import the components codes to render them on the documentation.

const components = [
  'button',
  'icon',
  'option',
  'select',
  'spinner',
  'switch',
  'text-field',
  'textarea',
  'tooltip',
  'form-layout',
  'password-field',
  // new component folder name here
];

5. Create new component documentation page at ./docs/src/pages/components/new-component.md. (If new component folder name is 'new-component').

6. Add sidebar link at ./docs/src/config.ts.

e.g.

export const SIDEBAR = [
  { text: "Alert", link: "/components/alert" },
  { text: "Button", link: "/components/button" },
  { text: "Tooltip", link: "/components/tooltip" },
  { text: "Text Field", link: "/components/text-field" },
  { text: "Select", link: "/components/select" },
  { text: "Switch", link: "/components/switch" },
  { text: "Textarea", link: "/components/textarea" },
  { text: "Spinner", link: "/components/spinner" },
  // new component item here
];

7. Run DOCS dev server and visit http://localhost:3000/

At the moment, all testing are done manually on the components you add to the documentation page.

cd docs && npm run dev