At the moment the documentation for grouped button-styled radio buttons is located in the "Buttons" component. However, I think it should be placed (or at least referenced) in the "Button Groups" component or the "Forms" component page. What do you think?

Form Radio Checkbox

In the official documentation form page,
in the Radio Checkbox section, there are 2 radio checkbox groups, that selects the first favorite fruit
and second favorite fruit respectively. However, selecting any checkbox will deselect all other checkbox, even in the other group.

The expected result should be that the chec

This is about the Docs.

Overview of the problem

When asking general "how to" questions:

• Please do not open an issue here!

• Instead, ask for help on StackOverflow or in our Gitter channel.

• Read the [CONTRIBUTING document](https://github.com/Dog

Thanks for a great css library.

I spend 2 days for trying to understand why in my vue project leaflet.css file not loaded to my project in test environment while in dev it's OK.

Please add information warning to installation section about purgecss

Also will be good to add note how to add whitelist styles to purgecss

module.exports = {
  plugins: {
    tailwindcss: {},
    'vue-

Is your feature request related to a problem? Please describe.

NES.css doesn't contain layout styles. This puts a burden on developers.
So I think it will be e

The cell input extension is not documented (didnt knew that extension exists until now).
@wenzhixin The extension is also not selectable on the online editor.

Once the content overflows, it would make the sidebar scroll together without this style setting.
Or one has to wrap its content with an extra element and setting the style on this element instead. But it is not so convenient.

BTW, the content now has padding: .4rem .4rem .4rem 4rem; (https://picturepan2.github.io/spectre/dist/spectre-exp.min.css)
Note that padding-left is 4rem, not `.4re

Take the example at https://developer.mozilla.org/en-US/docs/Learn/HTML/Tables/Basics, more specifically the code at https://github.com/mdn/learning-area/blob/master/html/tables/basic/animals-table-fixed.html and point it to this css instead of the provided one.

You get (with the latest Firefox on OSX) what you see in the attached image, which is not correct (Hen and Mare seem to have some

We're not checking the validity of HTML for the demo page. This was noticed in #119.

It would be nice to have something added to check for HTML validity - either something that lints the HTML files, or something that makes the build task fail when HTML isn't valid.

I would be looking for recommendations on how to do this and would be open to any pull request that accomplishes the goal!

Hi,
I started a new AMP project, and as we do not need to reinvent the wheel, I had reduced the original mui.css version to which I had added some lines that I had injected in the "amp-custom" with a size of 35kb (the limit imposed by google is 50kb)
As proposed here : ampproject/amphtml#2851, I think we should build a mui.css lightweight package for the AMP community a

Instead of embedding normalize gutenberg should probably say it's required in the documentation then users could use a newer version of normalize

Would be great if you could create a custom plugin for stylelint that adds support for your custom rules; for example, making font-range a known property for the property-no-unknown rule.

Summary

I'm new to Webpack, but I'm not sure how to get Webpack to "know" where the source files for Shoelace are. I have installed shoelace and the dependencies with Yarn.

My webpack.config.js

module.exports = {
   module: {
     rules: [
       {
         test: /\.css$/,
         use: [
           'style-loader',
           { 
               loader: 'css-loader', 
   

I'm trying to build a page that has a sidebar (or both a sidebar and a top appbar / navbar), and none of the Layout examples are helping. I tried mixing and matching the components and I never manage to obtain quite the result that works in the documentation (e.g. the Build Tools page), a simple sidebar on the left with content on the light.

The list looks outdated in today's context so if anyone looking for repositories to contribute for hacktoberfest. Then this might be a good place.

Our main tasks would be

• Add new content which you find useful for yourself while making sure that it isn't already there
• If you think any of the content is already there but is now deprecated then you can help in refactoring that as well. **Pl

To avoid warnings by people who knows nothing about alphabet, I suggest to write grunt-task/small tool wrapped with task, that will sort out all properties in css in alphabetical order.

moreover, we can add indentation check and fix etc.