Skip to main content

Sass

Sass:

Here we are now introducing some other facts about the Sass Css Framework. Sass is the latest framework of css that is trending now very fast and it's professional, mature and powerful grade css version comparing to old versions. The Sass css is adapted by bootstrap also and other framework also so it is going fastly worldwide and many more industries are not moving to Sass.

Basically Sass is the precompiled css version. It is help to load the page fastly then older css versions. Sass can be compiling through Gulp Js, Grunt and other compiler software also. It is latest version but still it is compatible with the all old versions of the css frameworks.

It is working with the dynamic variables like for colors, spacing and different sections containers etc. Like, in this css framework the value of color is described once in variable but the variable can be used multiple time and in many files so if we want to change the color so we just have to change at one place and rest is done via sass. It's replacing everywhere and no need to go at every place where described.

Sass has also working with mathematical functions which are helpful to make dynamic spacing class for multiple screen resolutions. So we can create own our column structure as we need with less efforts in short words we can say we can create our own bootstrap version.

So as per this progress for the Sass in the near future we will see the Sass in each and every developed site and it will be basic requirement for the UI and UX Developers.


Comments

Popular posts from this blog

As a symfony developer what you should take care when symfony standard edition is legacy:

Now  symfony standard edition is legacy . So no need to worry much just go threw article and understand whats new in symfony 4 if standard edition is legacy now. This is the main difference in Symfony 4 from symfony 2 and symfony 3 . Older symfony versions provide by default doctrine, twig, form, validation, profiler, annotations and many other components. But some time user do not want to use it. Suppose what if user do not want to doctrine or twig? Still he has doctrine and twig in his dependency. That makes symfony heavy framework. When starting a new project developers do not like to assemble things manually. So symfony 2 and 3 provides standard edition for developers to start a big project. But was hard to scale down project and decrease dependency if user do not require some packages. Symfony 2 and 3  are big success and in years developers are now aware with composer and dependency injection. So adding/removing a new package is not a big deal. So symfony chose...

3 Node.js Alternatives To WordPress

3 Node.js Alternatives To WordPress As compare to WordPress there is alternative option like Node.js. There are many various latest challengers that have large communities, support themes, plugins and are easy to install on your own server. Here are 3 you might want to checkout. KeystoneJS KeystoneJS is a content management system and framework to build server applications that interact with a database. It is based on the Express framework for Node.js and uses MongoDB for data storage. It represents a CMS alternative for web developers who want to build a data-driven website but don’t want to get into the PHP platform or large systems like WordPress. EnduroJS Enduro.js offers a fast and easy way to build your project, beautiful and simple admin UI and integrated tools to build everything on the server. It works without a database, instead relying on a system of flat files that can be opened directly in a text editor. It is easy to install and can be deployed via Git. ...

Laravel: How to protect .env files?

.env files: If you develop your applications using Laravel, you probably use .env files every day in your development life. We use these files to store the most secret information of our application. Be it database credentials, the application key or any third-party service credentials. So simply put: We do not want anyone to get access to these files! But the truth is: quite a few .env files are accessible. And I don’t mean that they are accessible by some hackers, but by Google. To search for public .env files, all you need to do is google for one of these terms: DB_USERNAME filetype:env DB_PASSWORD filetype:env APP_DEBUG filetype:env Secure your .env files The reason that these .env files are accessible and also get scraped is because of two things: Misconfigured shared hosting The .env file has the wrong access rights Shared hosting If you use shared hosting, please make sure that the root folder of your Laravel application is not accessib...