How to get better Writing

Making writing better

Practical experience is the only way to improve. I' ve put your advice into my blog entries and I feel that my writing is getting so much better. When you need to give background information, make sure you do it in small doses. Cause it' not gonna happen overnight, and not just because you want it to. While you can adjust it in the middle of the stream, don't just try to write yourself into a better structure: think about the right structure and then write to it.

Getting better at writing CPSS

Let's not get carried away: writing great written security solutions can be a pain. You' re writing things like div#app. li. items a. You write the same line over and over again. You' re throwing all your source at the end of your files because you just don't give a damn, just let it suck.

My goal today is to make you better at writing them. This is how we are writing good CCSS-codecode. So, let's just start studying how to get better with it. It' about how to spell maintenance friendly and how to organise it. I will use SCSS in my samples.

The SCSS is a preprocessor for enhancing your workflows. It' essentially a subset of CSS: it inserts some pretty neat functions like tags, interleaving, imports and mix-ins. They can have them with SCSS. Key advantage: Re-usability. The base colour is blu. So, you use blues everywhere: the colour of the backgrounds of your buttons, the colour of your titles, the colour of your URL.

BLUES EVERYWHERE. Suddenly you don't like blues anymore. W/o variables: Modify all rows in which you insert your own colour blu. 0099ff; color: $primary-color; fontsize: 5rem; color: blau; color: grün; can this become: fontsize: 5rem; color: bl? You' ll be spending less of your precious computing resources writing sophisticated nested selecctors.

In terms of legibility and serviceability, it is not possible to save the entire source text in one large document. Fortunately for us, SCSS allows us to do this. Allows you to generate part fi les by renaming the fi les with a preceding underscore: Animation. scss, _base. scss, _variables. scss, and so on.

The SCSS is intelligent enough to know that you are speaking of a part when you call it that. This is all we need to know about tags, interleaving, subsets and importing. The SCSS has some other feature like mix-ins, heredity and other directive ( @for, @if,...), but I won't discuss them here.

When your source file is not correctly labeled, it will be difficult to see at a single sight what you are about. It can make our codes more structure, as well as more flexible and re-usable. So how would you construct a basic home? How would you make a windows with your legoes now? They' the parts of a bloc, and they're needed to make our one.

Yes, your HTML document will be overwhelmed, but not worry??it is a small disadvantage in comparison to what BEM can bring you. Become interested and think about what they could have done better. Like always, you have to look, explore and design yourself to become better at what you want. Now, let's see how to organise your own cascade of styles.

That part will really help you to be more prolific, and will allow you to immediately find where you need to change your CSV-script. Put all your overtones in 7 different directories. Imports them all in a master scan that is at the source layer. 7 folders: base: in here, enter all your key.

When I say boiler plate, I mean all the written text you will be writing each and every day you launch a new work. It contains all the elements used to create your pages, such as your pushbuttons, shapes, swipers, pop-ups, etc. Layout: is used to lay out the different parts of your page, i.e. your headers, footers, navigations, sections, your own grids, and more:

Insert all your features together with your variable and mix. Place all non-dependent data in the manufacturer directory. Here you can insert your Font Awesome and bootstrap and such. Here you are importing all your overtones. Simply place all your extrinsic cascading security checks in a single hyperlink placed in a single headers.

You' d like your cascading style to be organised and following the 7-1 template so that you keep the abstract, component, layout and basic subfolders. You' re going to want to have a large directory where you can store all your parts and principal data. so you will have something similar:.... It's up to you.

Mm-hmm. I mean, web browser doesn't actually read ss flies, right? That is our last move, and we will immediately start learning how to build your own version of CSS to CSS. We will use a packet named node-sass, which allows us to build SCS CSFs. We have several possibilities, but we use only two: -w: view a folder or to view a workbook.

This means that node-sasswaits for all changes in your source and when they occur, it will compile it automaticly to CCSS. OUTput style: what will be the issue of your CSV format. We use it to generate your own CSV document. Generate your folder, your index. HTMLland your main.scss files: Insert these script into the packet. json file: .... "watch":

"That' node-sass sass/main. scss css/style. -w css", "build": "<font color="#ffff00">node-sass sass/main. scss css/style. com. CSss --output-style compressed" },.... Insert the hyperlink containing the pointer to your precompiled CSV document into the header of your index. html file: Start run guard when programming and open the index. html-files in your webrowser.

To have your CPM resized, simply run your run buil. To be even more prolific, you can include real-time download instead of manual index refresh. html-files. "That' node-sass sass/main. scss css/style. That''s all. It'', }, .... Well, let's discuss building utilities and, above all, an :autoprefixer.

In fact, when you create a website, you can use new functions that are not fully featured in all web-browsers. Therefore, we need the auto prefixer to make our CSV compatible without add an additional level of sophistication. So, what we will do to create our own craft is ::

Compiles all our SCSS data into one major SCSS data set. Autoprefix our CSV prefixer. Change the buildscript, and include these skripts in the packet. "It was", "Compile.""Node-sass sass/main. scss css/style. ¶ss -w": "scss css/style. css", "prefix": "ªPostcss css/style. ºuse auto-prefixer -o css/style. css,º compress: "Compression of" node-sass css/style. of" of" of " type built":

"Compiling npm-run-all precix compress" ... If you run run runm run build now, your CSV source file will be collapsed and manufacturer preferences have been added! You can now create serviceable, modulary and re-usable written source codes.

Auch interessant

Mehr zum Thema