bootScore — the Boot­strap-based Word­Press starter theme — can only be designed via CSS, PHP, and JS pro­gram­ming: If you want to fash­ion your web­site, you need to pro­gram. bootScore inte­grates Boot­strap tech­ni­cal­ly and leaves the vis­i­ble details to the pro­gram­ming web design­ers. And by default, it deliv­ers some­times blurred fea­tured images. Is it an unavoid­able task to fix that after­ward? […]

In the case of Fan­cy Images, we show our read­er first a tiny image. And on her request — wants to say: click — also a larg­er ver­sion. For imple­ment­ing this fea­ture, I ini­tial­ly put the URL to the uploaded image in the href-attribute of the fan­cy link and in the src attribute of the img tag. That slows down our site. We should fas­ten our fan­cy images: […]

I love sci­en­tif­ic writ­ing. Last night, I could­n’t hold back any­more. I need foot­notes on Word­Press that I can eas­i­ly apply to my posts with a good result! So, I replaced Easy Foot­notes with Foot­notes Made Easy. Too sys­tem­at­i­cal­ly unat­trac­tive was the result of Easy Foot­notes for me: […]

Fan­cy bitmaps are the one thing, scal­able pic­tures the oth­er. Word­Press does not like Scal­able Vec­tor Graph­ics by default: SVGs con­sist of XML code. If loaded, it can — at least in prin­ci­ple — inject mali­cious code into the sys­tem. Using SVGs in tem­plates, how­ev­er, is not pre­vent­ed by Word­Press. On HTML lev­el, they can be embed­ded — as usu­al — in img tags. That’s the way, also bootScore inte­grates the logos into the file header.php. But for the ambi­tious bootScore user, Fan­cy SVGs need more: […]

Large, promi­nent­ly placed images are eye-catch­ers. Word­Press even has a name for it: Fea­tured Image. The only prob­lem is: Start­ing every post again and again with a ‘fea­tured image’ is tir­ing. Even if our read­er has already decid­ed on an arti­cle, we force her to scroll. It would be bet­ter to give her direct­ly what she wants: the text. Let­ting her decide when she wants to see the big pic­ture by using Fan­cy Box­es is even­tu­al­ly also a mat­ter of read­abil­i­ty: […]

The small­er the screen, the greater the risk that long words destroy the read­ing image. With­out hyphen­ation, it becomes chop­py or fizzy on smart­phones. bootScore-based sites use an embed­ded Respon­sive Design. So, an auto­mat­ed hyphen­ation improves read­abil­i­ty and sup­ports bootScore to rearrange the text ele­ments: […]

Deep­er nest­ed menus are dis­played depend­ing on the size of the device. Stacked sub­menus on larg­er screens are more dif­fi­cult to read: Peo­ple stum­ble over what’s under­neath. Indent­ing menu entries is a good way to improve read­abil­i­ty: […]

Actu­al­ly, I want­ed fan­cy menus with an H‑OVER effect. Exact­ly. But after I crawled into the top­ic, I decid­ed against it. Fol­low­ing Ade­nauer’s apho­rism, What do I care about my gos­sip of yes­ter­day! I banned my idea to enable hov­er menus for bootScore by exter­nal tools. Because the view­point of Boot­strap and bootScore is real­ly rea­son­able. […]

In my ‘pre­vi­ous’ Word­Plus life, I was rather slop­py with my menus. What does that mean? Word­Press knows key­words and cat­e­gories. But what are entries in a deep­er nest­ed menu hav­ing their own sub-entries? They can be regard­ed as cat­e­gories, too — because of their group­ing effect. But they are not what Word­Press means by ‘cat­e­go­ry’. Clean menus deal with them prop­er­ly, with­out mix­ing types and tasks: […]