Last night we released the very first alpha build of Susy Next. This release is extremely sparse. What we have built is a background ‘engine’ for calculating grid math. There are some rough first steps towards api and syntax, but they are more “proof of concept” experimentation than usable interface.
Last night we released the very first alpha build of Susy Next.
This release is extremely sparse. What we have built is a background ‘engine’ for calculating grid math. There are some rough first steps towards api and syntax, but they are more “proof of concept” experimentation than usable interface.
There is no documentation, no tutorials, barely any user-facing activity
to speak of. You can get some sense of things from the test/
directory, but even that is un-explained.
Feel free to pull it apart, hack on it, and let us know what you think. We still have a long way to go, but we’re very excited about the power and flexibility this engine has to offer.
Check out the susy-next tag on GitHub.
Overflowing content, browser support, and polyfill updates
Anchor positioning is close to Baseline. As more people try it out, they are finding areas where it could be improved, and differences between browsers. Let’s take a look at the current state of anchor positioning.
We don’t have to choose between px and rem for spacing
There are many articles and established CSS best-practices that rely on determining the correct or best units to use. Now that comparison functions are well supported in CSS, we don’t have to choose.
It’s time to stop spreading this out-dated practice
Setting the box-sizing model to border-box is one of the few remaining CSS ‘resets’ used across most projects. But there are two common approaches, and the more popular choice will cause more problems than it solves.