Day 53: In The Mix!

huevon

One of the most powerful features of SCSS is mixins. I mentioned in my last post that CSS preprocessors give writing CSS more of a programming feel and mixins in SCSS are a prime example of that. A prevalent concept in modern programming languages is Don’t repeat yourself (DRY) and mixins are a great way to properly handle code that has to be used in many parts of a project. Mixins are blocks of reusable CSS declarations that can be used though out a project.

Creating and using mixins is a simple process. Mixins are declared by using the @mixin directive, followed by the name of the mixin, and the reusable code is input within curly braces. To use a mixin, one must simply add the @include directive followed by the mixin name to the desired selector and the code defined in the mixin will be included when the SCSS is compiled to CSS. The next level use and creation of mixins is a bit more complex.

Mixins can be used with with more complex programming concepts. For example, arguments can be passed though mixins and default values can be defined for parameters. Conditional statements can also be used with mixins. A mixin can become as complex as the engineer(s) need them to be.

Until next time!

#StayCoding

Day 52: Sassy!

tenor

In the world of Front-End Development , use of a CSS preprocessor is of massive import. Today, there are many CSS preprocessors available for teams and engineers alike to use, such as LESS, Sass, SCSS, and Stylus. It is very common for Front-End Development frameworks, such as Bootstrap and Foundation, to be built using a CSS preprocessor. Preprocessors empower designers and programmers to optimize their CSS utilization by systemizing the process. The benefits of using a CSS preprocessor are many and they are definitely here to stay.

Preprocessors are very beneficial. While many will argue that creating CSS is not technically programming, using a CSS preprocessor gives creating stylesheets a programming feel. In almost all preprocessors selectors can be nested, extending the rules from parent selectors to their children. Reusable variables are also common in preprocessors, which allow for code to be more modular and readable. Like many programming languages, developers can utilize many built-in functions and, if they need a custom solution, create functions of their own. Once the code is processed into CSS, the resulting stylesheet is standardized and easy to read. Above all, CSS preprocessors are more programmer friendly than standard stylesheets.

In my own studies, I have decided to make SCSS my preprocessor of choice. In my opinion, SCSS has syntax more similar to vanilla Javascript, which I really like. Using SCSS has helped me be more efficient writing CSS. I really enjoy using partials, which make my code so much more organized, especially when stylesheets become really long. I also like that pure CSS is valid SCSS, so if I’m in a crunch I can find a way to solve an issue in CSS and it won’t break the rest of my code. I look forward to continue mastering SCSS!

Until next time!

#StayCoding

Day 24: What’s up DOC!

doc.gif

I have taken the past couple of days to brush up my knowledge of html and to familiarize myself with its newest features. In the advent of the web, Hypertext Markup Language, more commonly known as html, was the language used to create web pages. Since then, the web has become vastly more sophisticated, with the creation of CSS and Javascript, among other technologies. As the web has become more advanced, so has html as a markup language.

The most recent iteration of html, html5, has build upon the foundation of its predecessors with both the developers and users in mind. Prior to html5, developers were forced to use the div element very generously. Now, developers can use html elements such as header, article, section, and footer to markup their web content. Not only are these new elements helpful for teams of developers to create and keep html documents organized, but this also helps users who access web pages via accessibility devices. The html5 document declaration is also valid for XHTML.

html5 also includes updated element attributes, embedded video, and animations. Forms, in html5, can now input email, date, telephone number, and time types. All of these attributes can help search engines when they index html pages to assist the users in finding more relevant information to their query. Previously, developers would have to employ a service like Adobe Flash to embed a video into a webpage. With html5 video, Flash and other services are now optional for embedded video for now. Canvas, an html5 feature that requires Javascript, can be used to create vector images in a web application.

Both the web and html have come along way, since their creation. Hypertext markup language 5 can now be combined with CSS to create responsive web pages. The most advanced features of html5 require the use of Javascript, such as Canvas and the  Geolocation API. This is only really scratching the surface of html5 (I will cover more advanced features of html5 in a later blog post).

Not all browsers have transitioned to completely support html5. A browser that does not support it may not recognize html5 elements and the content is ignored. To address this issue, html5 shiv was created. Shiv creates  in Javascript, so that the browser can natively recognize and style. Thanks to Josh Hibbert, I have this awesome Sublime Text 3 html5 shiv snippet.

Until next time!

#StayCoding

Day 0: The First Day Of The Rest Of My Life

meanjs-1024x492

My name is Henessy Ceballos. Today is January 1st, of the year 2018. My goal is to obtain the position of Junior Full Stack Developer by May 15th, of the year 2018, in a rapidly growing company.

I have some practice coding in a couple of languages and I have built various projects, so my goal is to hit the ground running. I will cover fundamentals, but I will power though subjects/topics that I have a strong foundation in. My main study resources will be courses on Udemy, books I have compiled since my interest in the web began, and free tutorials. By the end of the 4 month period, I hope to have deployed apps based on the MEAN Stack, Angular2, React.js, and Meteor. I will also be going over technologies such as git, mocha, Heroku, AWS, and Sublime Text 3.

I will keep a record of my triumphs and my defeats in this blog. This blog will also serve as a log for the amount of time I spend studying/focused on learning each week. My goal is to commit roughly 40 hours a week(~6hrs/day) to my studies, while maintaining my various commitments.

Here is to realizing dreams and the pursuit of happiness. Cheers.

 

#StayCoding