Website log


latest edit:

Sidenotes

Sidenotes are awesome, and after taking a look at Koos Loijesteijn post about them, I figured it would be great to implement them on here, too.

I decided not to, for now, for three main reasons:

  1. They are impossible to be implemented in Markdown, they need a lot of HTML and I don’t have the skills for making a Jekyll plugin to transform footnotes in sidenotes (but it may be a great idea to create one)
  2. I could easily create an {% include sidenotes.html %} where I could pass as arguments both the note content and the word linked to it, but it wouldn’t satisfy me for two reasons:
    1. In the case of printing, it would be a great mess.
    2. On other readers or Markdown parsers outside of Jekyll I’d have a massive chunk of unrendered ugly text
  3. Considered the reasons above, it’s not worth it. I use footnotes very few times (even though I massively over-use parentheses (as I am doing right now)) and with the lovely arrow1 automatically created, it’s painless to use them.

Further reading

Minimalizing

Minimalizing

If my personality was a website (and it is), it would be colorful, full of images, crazy, yet meaningful and emphatic.

The challenge, nevertheless, is not about achieving this goal by stuffing tons of content in a webpage and in its code, but it is rather about finding the perfect equilibrium between what accomplishes the purpose of transmitting the right message to the viewer/reader and what bloats the site and makes the user experience a distracting mess.

I am personally trying to fine-tune this website’s design in order to get to the perfect middle way.
I would love to make this website strictly minimal, by using little or no CSS, no webfonts, few super-tiny images; but, unfortunately, this is not who I am and it would not express my actual character.
On the other hand, I absolutely do not want this website to be a burden more than an enjoyment to navigate: loading times should not be too long and the user experience needs to be smooth and pleasant.

Below, I gather some quotes, links, thoughts and resources about this topic. I log in the [[Website log]] all of the decisions I make about what features this website should or should not have, and why.



Writings

Analytics

+++



Notes concerning search implementation.

Algolia

It is not the best solution in terms of speed and dependance, but it is still valid temporarily. Search functionality is very useful, so it is a trade-off I am willing to accept—temporarily).

Following these instructions the setup is quite simple. What is annoying and long to effectively customize is the front-end CSS, which I eventually decided would be simple to write from scratch by myself.



Typography and layout

Even though I love typography, I am never fully convinced about this website layout and design. My concern is not much about coloring, and typesetting, but about layouting, spacing and positioning. I am trying to understand the core of how layouting works by reading at a tremendously slow pace Richard Rutter’s web typography.

I will be noting below my doubts and, if solved, my conclusions.


Questions

  • Before headings, should break tags or CSS margin be used for separation between sections?
    • <br> spacing pros
      • effective regardless of the client and the styling
      • full control over exceptions for files
    • CSS spaging pros
      • greater flexibility for changes
      • keeping the content document more clean
  • Do quotes from quote tags depend by the language? Which ones should I use?

  1. Lovely arrow test -> ↩

Share

🏗 WIP section 🛠

This section should contain a beautifull graph displaying the relations among this note and all of the others on tommi.space. Unfortunately, showing it requires great coding skills and I am still working on it.

Comments

Webmentions

No webmentions were found.