Like Boot­strap, BootScore only knows menus with a depth of 2. Boot­strap because it wants to in prin­ci­ple. BootScore because it fol­lows its base as strict­ly as pos­si­ble. Lev­el 0 entries are list­ed hor­i­zon­tal­ly in the head­er, and the cor­re­spond­ing lev­el 1 entries are list­ed ver­ti­cal­ly below. Thus, the top-lev­el entries group the entries below them. And menus behave the same way on smart­phones and desktops.We want to talk a about deep­er nest­ed menus, here: […]

Main­tain­ing a Word­Press-based site often means work­ing with two instances — one for devel­op­ment and one for pro­duc­tion. Both have their own domain, a spe­cif­ic URL, used to link one site ele­ment to anoth­er. Man­u­al­ly or auto­mat­i­cal­ly. This implies that a web design­er has to replace this URL pre­fix with the oth­er one in all places if she wants to bring test­ed pages into pro­duc­tion. She can trig­ger this replace­ment in dif­fer­ent ways, man­u­al­ly or with a replace­ment plu­g­in. Here, we describe short­codes in menus — anoth­er method that sim­pli­fies such work sig­nif­i­cant­ly. […]

In the Euro­pean legal area, exploita­tion rights inher­ent­ly belong to the author of a work. She does not have to do any­thing else. In the Amer­i­can legal area, things are dif­fer­ent. There, every work falls into the ‘pub­lic domain’ by default. Only when the author active­ly claims her ‘copy­right’, the work belongs to her. Thus, hav­ing in copy­right line in your foot­er could be help­ful for you: […]

I had set up my old site, fodina.de bilin­gual. With the help of WP-Globus. As nice as this worked for years, at last WP-Globus got lost. Thor­ough­ly! When I edit­ed the Ger­man text, it made the Eng­lish dis­ap­pear. And vice ver­sa. Some­thing like that shall not hap­pen to me again. The restora­tion was com­plex and com­pli­cat­ed. So, while migrat­ing to bootScore, I switched to a sep­a­rat­ed mul­ti­lin­gual­ism — real­ized by two sep­a­rate sites. […]

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: […]