mwinkler, to webdev avatar

Caused a bug, learned something new. Turned it into a blog article

developerjustin, to wordpress avatar

I’ve been opposed to our team using any kind of build system for our #Wordpress theme work. Wherever possible, we write code and that code “ships” as written. My one exception is WP SCSS, a Wordpress plugin for compiling SCSS to #CSS on the server side. It has options for compression level and mapping, etc. and even conditional compiles to only regenerate styles when the #SCSS directory has been modified.

pablolarah, to webdev avatar
jkohlmann, to webdev avatar

Extremely unimpressed with the ways in which Sass integrations seem like a complete afterthought in 2024. Sass is a beautiful, powerful language, made and maintained by smart, caring people. It’s really sad to see it done dirty like this. #Sass #SCSS #WebDevelopment

bolverkr, to CSS Spanish avatar

¿Alguien conoce o me recomienda un curso que sea de nivel avanzado de SCSS/SASS?

#CSS #SCSS #SASS #FrontEnd

alexstandiford, to CSS avatar

CSS has gotten so, so good over the last few years. So many things that were really difficult to do are now trivial.

adriangadientbruegger, to CSS Afar

Dear #Quarto #rstats users: I’m trying to write my first custom template/ extension. In some examples I looked at there are #css and #scss files.

Can anyone explain me what their purpose and difference is? What should I put in which of them?

Links to tutorials / documentation are highly welcomed!

BryceWrayTX, to CSS avatar

Post >> Variations on styling variables in SSGs • The CSS-or-Sass question about styling variables is a lot simpler to answer when you’re building your site the right way.

#CSS #SCSS #Sass #WebDev #WebDesign #WebDevelopment

itsame_mcl, to Java French

Dans les sujets dont je devrais logiquement pas mal parler par ici, il y'a le #développement #informatique. C'est une passion pour moi depuis l'enfance, et j'ai la chance de pouvoir enfin l'exercer professionnellement depuis un peu plus d'un an, dans le service public (à l'Insee pour être précis). Côté technos, je bosse en full stack sur une appli web avec #Java et #Spring côté back, #SCSS, #VanillaJS et #React côté front. Sur mes projets persos et dans les cours que je donne, c'est #Python 🤓

sebastix, to vuejs avatar

Finishing up the redesign of the navigation on my site I worked out a week ago.

#VueJS #SCSS #WebDev

iamdtms, to random avatar
pezillionaire, to CSS avatar

It's been on my mind that with all the new features of it might be time to migrate away from .

Problem is I'd like to implement the changes as I go. Historically CSS has worked as a subset but with nesting those rules are broken – – which means migrating away from SCSS is now an all-or-nothing proposition.

Has enyone else done this? What are some solutions? I've been looking at as a potential build replacement

mikestreety, to programming avatar

We've had an internal linter for years, which is built on a PHP #symphony framework.

You run the linter you want and append --fix if you want it to resolve issues (if it can)

It lints things like #JS, #SCSS as well as #PHP (via #Rector and #phpstan), #Composer files and even #TYPO3 TypoScript files - all by using the open source libraries available.

It means all our developers can adhere to central linting conventions without having to update local config files.

drupalthoughts, to drupal avatar

i'm updating a #drupal 8 site to 10 and tumbling through some of the changes in #css #scss #sass class conventions, maybe due to the outdated #radix theme? where underscores are now hyphens and various <div> have appeared and disappeared 😬
is there a standard/programmatic way to update the classes at least? 🤔

rolle, to webdev avatar

Doing legacy code... #SCSS #CSS #Coding #WebDev

christian, to CSS avatar

Is there a support group for folks that say they will separate and structure their SASS/SCSS properly, but then just end up writing it all into one file?


#CSS #SCSS #Frontend

nachtfunke, to webdev

I'm trying to once again meaningfully unify how I abstract code in #SCSS and Cascade Layers in #css

Consider a scss library that has lots of folders and barrel files, components/_index.scss. Each component may be its own (nested) layer, but I cannot export them into a single, unified components layer, because I cannot put @layer before @forward/@use.

I could have something like $layer1: 'components' !default; $layer2: 'button' !default and then @forward with(...) it, but that's nasty

michael, to php avatar

After turning up here a couple of weeks or so ago, I figured it's time for an

I'm a full stack web developer, currently working mostly with () and Vanilla and . Still love too.

Outside of that, my main interests are around , , and just learning new stuff.

Husband, father of 2 boys, speaker of and with some basic understanding of

Started running my own instance just for fun, and loving it.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • kavyap
  • DreamBathrooms
  • osvaldo12
  • magazineikmin
  • khanakhh
  • tacticalgear
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • ethstaker
  • Durango
  • normalnudes
  • provamag3
  • ngwrru68w68
  • InstantRegret
  • cubers
  • modclub
  • everett
  • thenastyranch
  • cisconetworking
  • Leos
  • GTA5RPClips
  • tester
  • vwfavf
  • anitta
  • JUstTest
  • All magazines