How to Report a Bug or Add a Theme to CSS Bed

Updated

CSS Bed is a gallery of classless CSS themes, and its own page points contributors to the project's GitHub source for both bug reports and new theme submissions. The site does not host a separate contact form or submission portal — the listed path is: "Found a bug? Want to add a theme to the list? See cssbed source on github." So the practical answer is to go through GitHub, not through the website itself.

Where to go

The CSS Bed page links to its source on GitHub under the heading "How do I get this theme?" and repeats the pointer in the bug/contribution line. That repository is the single entry point for:

  • Reporting a bug (broken layout, rendering issue, theme not loading, etc.)
  • Proposing a new theme for the list
  • Asking about an existing theme

The site itself does not list a separate issue tracker, email address, or submission form, so GitHub is the only documented channel.

Reporting a bug

Because the site gives no formal bug template, follow the normal GitHub issue workflow and make the report reproducible:

  1. Open the CSS Bed source repository on GitHub.
  2. Check existing issues first — the problem may already be reported.
  3. Open a new issue and state which theme is affected (use the exact name from the theme list, e.g. awsm.css, pico.css, water.css-dark).
  4. Describe what you expected vs. what happened, and include the browser and version.
  5. If possible, link to a minimal HTML page that reproduces it, since classless themes depend entirely on plain HTML elements.

The theme names shown on the site are the ones to reference: HTML only, awsm.css, bahunya, bamboo, bootstrap, evenbettermotherfucking, holiday.css, kacit, marx, meyer, minicss, mvp.css, no-class, pico.css, sakura, sakura-vader, simple.css, stylize.css, tacit, thebestmotherfucking, tufte, vanillacss, w3c-chocolate, w3c-traditional, water.css-dark, water.css-light, writ, yorha.

Adding a theme to the list

The site frames this as "Want to add a theme to the list?" — again pointing to the GitHub source. There is no published checklist on the page, so the safe approach is to match what CSS Bed already is:

  • Classless: the theme should style plain HTML elements without requiring utility or component classes. The site's own rationale is "No learning curve — use HTML as you would normally."
  • Responsive: CSS Bed states themes are mobile responsive and only need the standard viewport meta tag.
  • Small: the site advertises themes at "Small size (< a few kb)."
  • Broad browser support: listed as a core reason to use classless themes.

Before submitting, verify your theme renders the element types CSS Bed demos on its page: headings, paragraphs, links, form elements (email, text, read-only, disabled inputs, radio buttons, checkboxes), code blocks, blockquotes, preformatted text, tables, and images. If it holds up across those, it fits the gallery's format.

What to confirm before you submit

  • The theme is not already in the list above.
  • It works with HTML alone — no required classes.
  • It stays small and responsive.
  • You can point to the source file so maintainers can review it.

Common sticking points

  • No in-site submission: the website offers no upload or contact mechanism; everything routes through GitHub.
  • No published contribution guidelines on the page: the site only says to see the source, so expect to follow the repository's own conventions once you're there.
  • Naming: themes in the list use short, lowercase-style names, so pick a name that won't collide with the existing set.

If you only want to use a theme, that's a different task — the site's instruction is to paste the theme snippet into your website. Reporting bugs and adding themes both go to the GitHub source.