Back to Blog
Prepros vscode5/8/2023 ![]() ![]() Open the Command Line (CMD) Tip!: Press Windows Key + R and type: CMD, then press Enter. So you need to install Ruby first so Sass can then run on top of it. WTF is Ruby? □ Ruby is the technology or programming language Sass is built on. Edit () - I’ve confirmed that Sass works fine with Ruby 2.3.3 (圆4) at the moment of this edit. Download the Ruby installer: - Look for the version with (圆4) on it. Here we go □! Steps to Installing Ruby Sass on Windows (versions 7/8/10)ġ. So what makes this guide different from aaaaalll other guides out there? It’s different because I’m going to explain it to you the way I would’ve liked to have seen it explained to me back then, when I had no clue about command line crap (and I still don’t to be honest).Ī. Now, here I am showing you how to do it □. Google Fonts Microsoft Teams (this will be used for both in and out-of-class communication) Zoom VS Code Codekit / Prepros Web Server. Well, actually there was this one website (I can’t even find it now anymore) that had a very, very rough list of how to do it, but yet it was the ‘friendliest’ of everything else I came across.Īfter trying to install Sass three times in a span of about 3-4 months, I was finally able to “crack the code”. It will also help you start with WordPress before digging deeper (link below).I remember almost 2 years ago (today being ) I looked all over the web for a simple guide, with simple steps, in “human” language to help me install Sass. While working in WordPress, the Codex will be your best friend. There are a lot of tracks and you have to be somewhat of an autodidact or just enjoy it (like most of us). The track “tracks/beginning-php” on Treehouse starts with the basics of HTML and works up to a soft introduction to PHP. After that would be custom theme development where you build basically everything and make it easily editable on the backend for the client (or yourself). The Codex has good info for starting with a Child Theme - which will get you off the ground with a somewhat custom theme you can build and all of the niceties set up for you. ![]() (this is also where version control comes into play if you can’t fix said broken thing - or don’t know what you changed - git will tell you everything that has been done (code-wise) and is also conveniently integrated with VS Code - some setup required). Google and StackOverflow are (sometimes*) good sources of information.ĭon’t be afraid to break things and always keep backups. It will only add complexity when you are first starting, but is essential. I also recommend looking into git (version control) - that is after you have a foundation in the basics of shell / terminal commands as well as the above. The dev tools section is powerful and can uncover things if something doesn’t work the way you expect it to. Once you’ve gotten things setup I recommend always using the “Inspect Element” option in the right click menu when in Chrome or Firefox. You should start simple and use HTML and CSS to get a foundation in them before branching to libraries and other languages. With that said, I recommend getting up to speed with HTML, CSS/SASS, Javascript, and PHP to start. There are also some bigger names like Zac Gordon (paid) that have good courses in starting a foundation in WordPress. ![]() I use Local, VS Code, PrePros (windows pre-processor), Firefox (dev edition), Chrome, and the shell for git mostly. **Edit: This is not a comprehensive guide. While I think this topic is debatable in the sense that it is all preferential No one developer does things the same (for the most part). ![]()
0 Comments
Read More
Leave a Reply. |