References about things I learn about Web Technologies

HTML5 and CSS3 can accomplish a lot of things we may be used to do with heavier tools.

I'd like to remind myself that thare is no need of external tools to do the following:

HTML5

Life is a lot easier with the new html tags

<progress>
a progress bar ready to use
<input pattern="REGEX">
how could it be easier?
<date>
a very neat calendar input without any effort

CSS3

Flexboxes

Flexbox will save us a ton of time. It is simple and elegant and does not demand any framework.

Guide to flexbox
at CSS-tricks
CSS Flexible Box Layout Model
at W3
CSS Flex Properties
Scotch.io

Templating Languages

Haml

A ruby templating language: haml.info

    %article
      %section.introduction
        %h1 Haml is clean
        %p It uses indentation to close tags.
        %p= content.dynamically.inserted
    

Twig

A PHP templating language. twig.symfony.com

    <article>
      <section class="introduction">
        <h1>Twig is HTML</h1>
        <p>With powerful features such as variables, conditions and loops</p>
        <p>Use your variables in {{ myvar }} double brackets</p>
      </section>
    </article>
    

CSS extension languages

Sass

CSS with superpowers: https://sass-lang.com/

Frameworks

I am not really a framework lover. I get suspicious that using them may deprive me of learning the proper way of doing things. I've been proven wrong several times now and I should be less averse to learn and use frameworks.

I've read that the difference between a framework and a library is that the framework calls your code, while your code calls the library. The fact is that the framework makes several decisions for you. You get a almost ready to use application by simply installing it. This is usually a good thing. The framework's author is usually a much better programmer than I am and usually there is a great community of developers helping him.

There are simply tons of frameworks available out there and it would be terribly difficult to properly analyse each of them and make a right decision. You'd have probably spend more time studying all of them than you would building your application from scratch. I guess that's why people go usually for the famous ones.

I don't really see a great difference between a framework and a CMS. I see a CMS as a framework that comes with a pre-built example. Here is a list of some popular frameworks:

Downside

The thing is the framework needs to deal with much bigger problems than I do. Thus, when using a framework to build a simple application I end up with a complex application to maintain.

Another issue is that when working with a framework you need to learn it's way of doing things. You can't simply add a button, you need to learn how the framework does it and do that way. This will lower the programmer's productivity unless he is very familiar with the framework.

Information Architecture

Design

It seems to be an universal truth that the knowledge is corrupted as it spreads. Minimalistc design is no exception. I am simply not a designer and therefore the least ammount of design I try to do the better. This is not necessarily true for a good designer, though.

It seems that most websites are built by non designers and that is the main reason why the minimalistic design helps so much. If you want a nice design, though, the answer is not a white background, the answer is to hire a good designer.

Accessibility

It is amazing that many tools consider that an image with an alt text, whatever it is, is better than an image without an alt text. This requirement introduced the practice of creating useless alt texts with the sole end of being compliant with such tools. Although it is surely important to use alt texts, it should not be done without carelessly.

Icon Fonts are not accessible
Final nail in the Icon Fonts Coffin