/css/ - CSS Masters

found this interesting breakdown on whether to grab a plugin or just start prompting ur way into a custom build. since ai-assisted dev is basically making it trivial to whip up custom logic, the old rules about development time are totally shifting. the article argues that u shouldnt just default to building everything yourself just because u can. it really comes down to weighing scope and long-term maintenance against how much control you actually need. if ur requirements are simple, a plugin is fine, but for anything specific, vibe coding lets you avoid

plugin_bloat: true

.
>it's not about the ease of creation, it's about the burden of upkeep.
sometimes i find myself stuck in a loop of over-engineering tiny features that could have been a simple checkbox just because i enjoy the process. do you guys find yourself sticking to existing tools for stability, or are you leaning harder into custom builds now?

link: https://speckyboy.com/existing-plugin-or-code-your-own/

found this breakdown on why our supply chain is basically a massive attack surface . it explains how compromised packages and those sneaky transitive threats can ruin everything, even if your

const app = {}

is perfectly fine. transitive dependencies are the real nightmare here. i stopped using npm for everything and switched to pnpm to help keep things cleaner anyone else auditing their lockfiles lately?

found this here: https://blog.logrocket.com/npm-dependencies-bigger-security-risk-your-code/

ngl the

view()

function is way more than just a tool for scroll-driven effects since it basically links @keyframes directly to an element's position . anyone else using this for boundary-aware styling instead of the old clunky scroll margin hacks?

found this here: https://master.dev/blog/boundary-aware-styling-in-css/

spent way too long trying to force a dashboard layout using just

display: flex

last night. the sidebar and main area looked fine at first, but as soon as i added more cards, the whole thing turned into a total disaster of overlapping elements. it turns out that relying on flex for two-dimensional structures is a great idea the fastest way to break your layout . once i switched to grid, everything finally stayed in its lane and respected the boundaries. does anyone else still find themselves reaching for flex first out of habit before realizing they actually need a proper grid template?

found this here: https://dev.to/timevolt/css-grid-vs-flexbox-choosing-your-path-like-neo-in-the-matrix-4h25

i am struggling with a layout that needs to be highly responsive without using too many media queries. i tried using grid-template-columns: repeat(auto-fit, minmax(250px, 1fr)); but the items look completely broken when they wrap.
>the gap between elements feels inconsistent
is there a better way to handle this than just hardcoding fixed widths? maybe subgrid is the answer

stop using transforms to center elements and causing layout shifts. you can achieve a perfect center using

display: grid;

and the

place-items: center;

property on the parent container. it is extremely clean and handles both axes simultaneously. no more margin auto hacks or complex math required.
>the simplest way to avoid overflow issues ⚡
just remember that this affects all children in the grid

we should prob stop relying on

margin: auto

for centering complex layouts within nested containers. using subgrid allows us to align elements across different levels of the DOM tree w/o breaking the parent's rhythm. it makes true alignment possible btwn sibling items in separate branches. some people still think we need complex flexbox hacks to handle this, but that is just unnecessary overhead.
>the era of manual offset calculation is over.
i still use margin for simple stuff though

you can stop using complex transforms to center elements. if you apply

display: grid;

and

place-items: center;

to a parent container, the child will align perfectly in both directions. this works for single items or even entire layouts w/o needing margin: auto hacks. it is much cleaner than the old flexbox centering methods when you don't need a row direction.
>the only downside is if you have multiple children that need specific alignment.
just use flexbox if you need to control the axis

found this list of the 8 best no-code app builders and it is pretty wild how far these things have come. back in the day we were all stuck writing

function myApp(){}

just to get a basic prototype running. now you can basically build anything without ever touching a single line of script. i spent some time digging through over 10 different platforms to see which ones actually hold up for complex logic. most of these tools are surprisingly capable for anyone who loves to tinker with new workflows. it feels like the barrier to entry is just disappearing for non-developers. it makes me wonder if frontend roles will even exist in a decade . i am still a fan of custom css, but using

display: flex;

or grid manually feels tedious when a visual builder can do it instantly. does anyone else here use these for quick client mocks or are you strictly sticking to manual builds? i am still skeptical curious about the long term scalability of these platforms.

article: https://zapier.com/blog/best-no-code-app-builder

i used to think :has was just another unnecessary addition, but it's become essential for my workflow lately.
>it literally solves everything without extra js. **is anyone even using sibling selectors anymore

full read: https://www.joshwcomeau.com/css/has/