A foot­er is an area for more off-beat ref­er­ences. They are more off­side inso­far as our read­ers expect to get access to what they came for — direct­ly after a page is loaded, direct­ly on top of it. At the bot­tom — where they first have to scroll — they are look­ing for minor aspects. That’s the log­ic of sub­or­di­na­tion. For the sake of read­er-friend­li­ness, the foot­er is a good place for a sec­ondary sub­or­di­nat­ed menu should: […]

What is impor­tant is in the eye of the behold­er. A lawyer would per­haps include the imprint, the image cred­its, or the data pro­tec­tion con­cept. And not to for­get: the open source com­pli­ance arti­facts. The read­er, on the oth­er hand, would see it dif­fer­ent­ly! She wants con­tent. Enter­tain­ment. Real ‘con­tent’. Not this legal gob­bledy­gook. […]

Search engines don’t like gos­sipy key­word­ing and love well-filled sitemaps. But they detest bro­ken links. So, we should pre­vent our­selves from destroy­ing the giv­en SEO friend­ly behav­ior of bootScore: […]

Hav­ing enabled Font-Awe­some is a nice fea­ture of bootScore. Some­what frus­trat­ed , I have to add that embed­ding ‘own’ HTML code into a WordPress/Gutenberg block via ‘Edit as HTML’ occa­sion­al­ly destroys the type and con­tent of the block : If the code is sus­pect to the Guten­berg edi­tor, it replaces the work already done with an emp­ty HTML block . Annoy­ing if you just want­ed to quick­ly add anoth­er icon from Font Awe­some via <i class="fa-regular fa-square-check"></i>. That must be solved dif­fer­ent­ly, by a bootScore Short­code For Font-Awe­some — for exam­ple: […]

SEO encom­pass­es a lot. One means of Search Engine Opti­miza­tion is the seman­tic tag­ging of sec­tions, which became pos­si­ble with HTML5. In this respect, bootScore and SEO fit well togeth­er: […]

The form of my scope list con­vinced me to talk about Font Awe­some Icons and cus­tom CSS class­es in bootScore, first. A pure HTML list is ugly, in my case: down­right unread­able. No amount of reword­ing or restruc­tur­ing helped. Short­en­ing it was not an option either. It should con­tin­ue to func­tion as a com­plete scope state­ment. So I had to change its appear­ance. […]

That I would have to give up YAML-CSS had quick­ly become clear to me at the begin­ning of the year. What I should replace it with, not. I want­ed to stay with Word­Press. And to recy­cle my old con­tent. So, all I had to do was to replace my old theme. The­o­ret­i­cal­ly. Even­tu­al­ly, I end­ed up migrat­ing to bootScore: […]

Recent­ly I wrote about the ‘expir­ing’ edi­tor Atom. Now I’ve stum­bled upon anoth­er dead horse in my sta­ble: YAML CSS. That has noth­ing to do with YAML ain’t Markup Lan­guage. It’s a mod­u­lar CSS frame­work for tru­ly respon­sive web­sites. For years, it served me faith­ful­ly, first in Typo3, then on Word­Press. And now? […]

The Atom page says: “Atom and all repos­i­to­ries under Atom will be archived on Decem­ber 15, 2022″. The “hack­able text edi­tor for the 21st Cen­tu­ry”, devel­oped by GitHub — “[…] had not had sig­nif­i­cant fea­ture devel­op­ment for the past sev­er­al years” and that GitHub has there­fore “[…] decid­ed to retire Atom” in favor for “Microsoft Visu­al Stu­dio Code”. What a dis­ap­point­ment for an Atom lover like me. So — what now? […]