The Semantic Language

06 Oct 2016

Semantic UI

Enter Semantic UI, making the HTML/CSS world a better place. Ever tried to make a website with raw HTML/CSS? Thought it was impossible? Well not to worry, with Semantic UI’s many and easy to implement features, web designing becomes an absolute breeze. Check this out! You can turn your website from this

into this!

The Firefox and Chrome column have switched places! And just look at that top navigation bar!

10/10 Would Tell A Friend

Now with that being said, I like it! I’ve had experience with HTML/CSS prior to this class, and I’ve already enjoyed the language. I guess what I like most about HTML is you can actually see what you do. Web designing is a nice break from the usual C/Java programming languages that we mostly do. Semantic UI manages to make the experience much greater in my opinion. And since I knew the basics of HTML beforehand, understanding Semantic UI was pretty effortless to say the least. There is indeed a vast amount of information to go through in order to understand how it works, and it can get pretty overwhelming. Also trying to figure out which variation of classes you need to use for a specific task can also be a little tedious. But after experiencing it for a while I’ve gotten pretty used to the syntax. And after creating/replicating sites over the week, it made me realized how much simpler designing can be with UI Frameworks.

One of the greatest things about it is the fact that class names are closer to English rather than having random strings of words. This makes designing feel natural; saving a lot of time and stress compared to raw HTML/CSS. For example, if you wanted a grid layout with Semantic UI the class would be something like “ui grid”, and then the following column classes to determine how many columns you’d like. That is much easier than using the table tag in raw HTML. I do however have one gripe with Semantic UI when implementing CSS. With the Framework being fairly strict I’ve noticed some CSS elements I try to implement will not work. Also it seems harder to specify exactly what element/tag you want to edit with all the div tags everywhere. Well that could just be me not coding CSS correctly with Semantic, but regardless the pros outweigh my cons. And in return, the end results of using the UI Framework are not disappointing.