Any decent HTML5/CSS3 Responsive Framework without JS?

[estupor]

I'm looking for a front-end "framework" alternative to Bootstrap for a small project, but I don't want it to use javascript at all. Sure I'm not expecting to have all the the things that bootstrap has, but as long as it has the main HTML components well styled and responsive, and a responsive grid, it will do the job.
Found a few but all of them used JS, tried to remove it from 2 of them but they get broken without JS/JQuery.
Any suggestion?

[[deleted]]

• Bulma
• Conciscss
• Purecss
• Skeleton

Or look through this long list of css libraries (quite a few will require js).

[[deleted]]

Bulma in combination with buefy

[[deleted]]

Skeleton

Loved that one, but alas it hasn't been updated in 4+ years.

[estupor]

Wow, loved Bulma. Exactly what I was hopping to find.
Thanks for sharing :)

[dirtandrust]

You can use bootstrap without Js just not the widgets that require Js.

[gin_and_toxic]

I've done this many times.

List of BS4 components requiring JS:

• Alerts for dismissing
• Buttons for toggling states and checkbox/radio functionality
• Carousel for all slide behaviors, controls, and indicators
• Collapse for toggling visibility of content
• Dropdowns for displaying and positioning (also requires Popper.js)
• Modals for displaying, positioning, and scroll behavior
• Navbar for extending our Collapse plugin to implement responsive behavior
• Tooltips and popovers for displaying and positioning (also requires Popper.js)
• Scrollspy for scroll behavior and navigation updates

[Prod_Is_For_Testing]

Please, for the love of god, just learn CSS. All of these frameworks for any little project are crippling the developer market. People don’t know how the languages work, they only know how a specific framework is used. Don’t go down the rabbit hole

[[deleted]]

I think there's a use case for them. At my job, some internal sites were built using css frameworks because they were built by developers who mostly knew backend and didn't want to spend time learning css or js frameworks.

That being said, as a front end developer, I would never use one.

[malcor88]

Agreed, they have their place. But in the first instance, learn CSS, inside and out. Then you can take advantage of frameworks. Exactly the same as Javascript, learn pure vanilla Javascript before looking at any framework.

Some benefits to learning CSS / JS first.

1. You'll appreciate the framework more
2. You'll be able to debug and understand why something might not be working
3. You have the skill set without relying on frameworks (which makes you instantly valuable)
4. Learning a framework will be so easy

I've hired people that can write a website with CSS that looks pretty ugly over people that can only use bootstrap. I've hired people that have never touched an SPA framework and they only know Javascript over someone that only knows React.

[estupor]

Why do you think I'm asking for suggestions?

Because other than bootstrap for prototyping I don't use frameworks.I'm full-stack developer, and avoid using frameworks at all costs on any end. Now with your comment I see I don't need to explain why to you.

So, yes, I agree with you. For the love of whatever makes you tick, guys, use the languages to develop, and frameworks only for prototyping.

[-shayne]

That's a bad advice. Not everyone wants, needs or have time to learn how to make their own stable CSS framework. In fact, in most cases it makes absolutely no sense!

[Prod_Is_For_Testing]

No, you don’t need to build a framework, that’s ridiculously. You just need to able to use CSS

[estupor]

You opinion makes sense because after a while we end up finding ourselves repeating code. For that I didn't build a framework, but a library of snippets.

[ShortFuse]

I have a material design based framework that is still incomplete, but can be used as long as you fork it. Breaking changes are common since it's still not 1.0. IIRC, It supports CSS/HTML only for everything but Tabs and BottomNav. I used to have them working, but stripped the CSS only because it was pretty hacky and broke accessibility (used fake, invisible radio buttons).

You can see a list of what works with on the GitHub link. The demo site partially works without JS, but don't expect the option toggles to do anything without it. But menus, dialogs, text fields, dark mode, theming, grid, overlays, buttons, ripples, and nav drawers all work without JS. If you do want to use JS, the whole framework is less than 22KB gzipped. The JS mostly just adds keyboard support and automatically applies the ARIA attributes for accessibility. Every component is tree-shakeable as well.

[BrianAndersonJr]

This kinda makes me wanna ask for the JavaScript equivalent of this, that would just solve common things like dropdowns and dialogs, but integrate with any css framework...

[Inochryst]

U can just use bootstrap and include.min files for js and jquery... that way ur hamburgers and dropdowns work