If you do this just once, you are forced to continue to do so from there on out, or lose the changes if you ever do recompile your Sass. While you certainly could just go in and edit a CSS file after the fact, it would not be advisable to do so unless you just absolutely didn't have access to the original Sass files. You usually check the Sass files along with other development files into version control if you are working with other developers on the project that way they can pull the Sass files down as well and edit those to compile the CSS. When you decide to use it in a project, it is a part of the development process, not the production side. It looks like you have to learn it for this new job anyway, so just embrace it and the opportunity to learn something new. Yes, I do miss being able to update immediately on the fly, but that's the only negative I've found, and it's worth it to me. I use it for all my projects, and having to write in vanilla CSS becomes a bit annoying now. The bigger the project, the more useful Sass becomes. But Sass is what most big companies are using - what Bootstrap and Foundation run on. If you're fine with CSS, you don't have to change. scss no problem.įorgive my ignorance, but what's the big deal? It seems it wont save that much more time, exspecially when just using a WYSIWYG like Stylizer. Not entirely positive, but highly likely that you can, since I use Brackets, which is by Adobe, and it recognizes. You'll be compiling through the command line, either with Ruby, Gulp or Grunt. Reading the above articles, you'll see how it doesn't matter in the slightest what you use to write your Sass - plain notepad would work just as well as Sublime, Atom, Brackets, or Dreamweaver. It's the tradeoff for all the benefits you get with Sass. I'm not sure exactly what you're referring to here with project, but you wouldn't be able to update on the fly like you're used to with CSS. You should probably be using Version Control (Git) to have your code at hand no matter where you are. Technically you could, but that's not common practice - it's a workaround. No reason other than it came with CS and is there)įirst of all, here's a guide I wrote to using Sass, and also guides for Sass with Gulp and Sass with Grunt, so these articles alone should answer your questions. (Edit: I dont use Dreamweaver's WYSIWYG, just the coding part. scss? Can I use it's code highlighting abilities for Sass?įorgive my ignorance, but what's the big deal? It seems it wont save that much more time, especially when just using a WYSIWYG like Stylizer.Īny advice is much appreciated! Many thanks in advance! css which I can then just upload to my server?ĭoes Dreamweaver detect. Can I do something similar with Dreamweaver and Sass?Ĭan I code something in Sass and have it just spit out a. What text editors can you use with Sass and how do they save to the shared host server? If I have to code outside the CMS I use Dreamweaver and use its FTP to upload the files. What exactly is a 'project'? Does that lock me to using one machine? Can I jump on, say, my mums PC and update a CSS doc real quick, or would I have to install Sass and download the project? What if you need to update the CSS of a site later, on perhaps another computer? Is it common practice to have a separate CSS file that overrides the Sass file? I've watched a few tutorials, but they seem to jump right ahead into the actual coding part of it. It has version control, text editors and allows me to jump on and continue working from any other computer.īut now I've got a contract at a place that uses Sass. I usually code everything - HTML, JS, CSS - within my go to CMS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |