{"id":325887,"date":"2020-11-25T07:47:16","date_gmt":"2020-11-25T15:47:16","guid":{"rendered":"https:\/\/css-tricks.com\/?p=325887"},"modified":"2020-11-25T07:47:19","modified_gmt":"2020-11-25T15:47:19","slug":"considerations-for-making-a-css-framework","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/considerations-for-making-a-css-framework\/","title":{"rendered":"Considerations for Making a CSS Framework"},"content":{"rendered":"\n

Around eight months ago, I started building a framework which would eventually go on to become Halfmoon<\/a>. I made a post on this very website<\/a> announcing the launch of the very first version. Halfmoon has been billed as a Bootstrap alternative with a built-in dark mode feature, that is especially good when it comes to building dashboards and tools. All of this still applies to the framework.<\/p>\n\n\n\n

However, today I would like to talk about an area of the framework that is a bit understated. I believe our industry as a whole seriously underestimates the value of customization and user personalization, i.e. users being able to set their own design preferences. Chris has written before about knowing who a design system is made for<\/a>, pointing out a spectrum of flexibility depending on who<\/em> a system is meant to help.<\/p>\n\n\n\n

But it’s more than design systems. Let’s talk about how Halfmoon addresses these issues because they’re important considerations for knowing which framework works best for your specific needs.<\/p>\n\n\n\n\n\n\n\n

\"\"\"\"<\/div>
Dashboard built using Halfmoon<\/figcaption><\/figure>\n\n\n

Who is Halfmoon for?<\/h3>\n\n\n

Before diving in, let’s address an important question: Is Halfmoon the right framework for you? Here’s a list of questions to help you answer that:<\/p>\n\n\n\n