![]() If you want to make a PR to change part of the css source for tachyons, make sure you make the PR on the corresponding module This can be useful if you are using another library or have written some of your own css and want to make sure there are no naming collisions. If you want to check that a class hasn't been redefined or 'mutated' there is a linter to check that all of the classes have only been defined once. If you want to recompile everything from src everytime you save a change - you can run the following command, which will compile and minify the css This will output both minified and unminified versions of the css to the css directory. If you want to just use src as a jumping off point and edit all the code yourself, you can compile all of your wonderful changes by running This will copy over all source files, so if you've modified src/ your changes might will be overwritten but you can use version control (like git!) to undo these changes. If you want to update a tachyons partial, install the desired module version via npm and run the build command again. Uses a series of postcss plugins to compile the source down to vanilla css. Then get copied over to your local src directory and then the tachyons-cli The first time you build tachyons all of the css gets installed via npm, but the modules They aren't dependent on eachother butĪre designed to play well together. Tachyons is available as a series of small self contained css modules. To the minified file in the head of your html file.Ĭurrently the latest version is 4.0.0-beta.35Ĭlone the repo from github and install dependencies through npm. ![]() The quickest and easiest way to start using tachyons is to include a reference The modules are generally pretty small and thus easy to read and grock if you're familiar with css at all. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |