Survey Of All Posts

From ‘Easy’ to ‘Made Easy’: Footnotes on WordPress

/ | Leave a Comment

Last night, I could­n’t hold back any­more: 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. […]

Fancy SVGs

/ | Leave a Comment

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, this method does not work. […]

Fancy Boxes for Fancy Images

/ | Leave a Comment

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. And let her decide for her­self when exact­ly she wants to see the big pic­ture. […]

Divide and Beautify!

/ | Leave a Comment

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. If a bootScore-based site — accord­ing to Respon­sive Design — wants to main­tain read­abil­i­ty by rear­rang­ing the text ele­ments, then it can­not do that with­out auto­mat­ed hyphen­ation. […]

Indent and Beautify!

/ | Leave a Comment

Deep­er nest­ed menus are dis­played depend­ing on the size of the device. Stacked sub­menus on larg­er screens are unfriend­ly for the read­er. Peo­ple stum­ble over what’s under­neath. So let us soft­en the stack­ing a bit. […]

No HOVER menu for bootScore after all?

/ | Leave a Comment

Exact­ly. 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! […]

Keeping Your Menus Clean

/ | Leave a Comment

In my ‘pre­vi­ous’ Word­Plus life, I was rather slop­py with my menus.

Let’s first agree on what we are talk­ing about: Word­Press knows key­words and cat­e­gories. Now we also need a name for the entries in nest­ed menus, which them­selves still have 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’. […]

Deeper Nested Menus

/ | Leave a Comment

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 desk­tops. […]

From dev to prod: Shortcodes in Menus and elsewhere

/ | Leave a Comment

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 woman 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 anoth­er method that sim­pli­fies such work sig­nif­i­cant­ly. […]

To top