![]() ![]() I still haven’t really settled on something, but decided to divide things out a little bit, like a folder for global elements (e.g. There are so many opinions and approaches and I’m finding myself non-committal. I’m breaking my Sass files up into partials, of course, but I’ve always tortured myself over how to organize the files. The hardest part of any job for me is naming things but that’s sorta what setting up is all about. While it’s not 1:1 with what I’m looking for, I was able to fuss with it a bit and it to be something that works… at least for now. I was tempted to copy his approach because (1) he’s a smart dude and (2) he rolls with a WordPress site as well.īut I remembered editing a post by Ali Alaa in 2018 that has a pretty nice flow. I looked at some projects I’ve worked on where it was used but couldn’t find a configuration that I love. I wasn’t really sure where to start with Gulp. I had been using Grunt on projects, but have been convinced that Gulp is a little faster at compiling assets, despite finding Grunt easier to configure. ![]() That should be a huge performance gain for me since I don’t have to import hundreds of kilobytes just to lay stuff out. For example, buh-bye Foundation! Not because it’s bad or anything, but because I was only using it for the Grid anyway and CSS Grid is more than up for the challenge of replacing it. I’m going a different direction this time around because I plan on having fewer dependencies. It was a wonder back then because it was so simple to configure Sass for writing styles, integrating Foundation for the framework, and compiling everything from JavaScript to images. The last I worked on this site, I heavily relied on CodeKit to handle my development. Now that I have settled on a general look and feel for this site, I’ve been working on setting up my development environment to make it happen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |