Link­ing Boot­strap and Word­Press to get a respon­sive design is the task of bootScore, a WP-theme bring­ing along what the web design­er actu­al­ly does not want to pro­gram her­self. Instead, she can now rely on a MIT-licensed pre­lim­i­nary work host­ed on GitHub. But its ‘stan­dard out­fit’ still must be per­son­al­ized, ‘pimped’ — by the work of a Web Design­er? The theme is adapt­ed — so bootScore — by mod­i­fy­ing its “[…] .scss, .php, and .js files”. Here are my 13 steps from a pure bootScore to a per­son­al ‘home­page’: […]

To speed up deliv­er­abil­i­ty, JavaScript libraries — embed­ded in a web­site — are usu­al­ly com­pressed by delet­ing all white­space, line feeds, and com­ments. They are mini­fied. As a result, they usu­al­ly con­tain only very rudi­men­ta­ry license infor­ma­tion — at least not the license text itself. But all FOSS licens­es require us to ship some com­pli­ance arti­facts with the code — espe­cial­ly the license text. This is the chal­lenge with using JavaScript — in bootScore and else­where […]

Often the web­site oper­a­tor is told, that Data pro­tec­tion is com­plex and has to be orga­nized by experts. But what if she does­n’t have the mon­ey for that? If it seems some­how non­sen­si­cal to shoot at a spar­row blog with the can­non of a paid team of experts? Then — maybe and with the help of Google — she installs some pop­u­lar Word­Press plu­g­ins for pri­va­cy and/or cook­ies — in the hope that all goes well. Or she inves­ti­gates it in more detail. And in the end, she per­haps gath­ers rules of thumb, from which at least one well-work­able way results. Here are my 3.7 rules of thumb: […]

boot­strap and bootScore use SCSS vari­ables — as we know. To group fonts, the file bootstrap/_variables.scss pro­vides the vari­ables $font-family-base, $font-family-sans-serif, $font-family-monospace and $font-family-code. A vari­able $font-family-serif does not exist. If we over­write fam­i­ly-base in our _bscore_variables.scss file, we rede­fine the default. If we want to use a deviant font for our head­ings, we have to rede­fine the vari­ables $headings-font-family and $display-font-family. This is suf­fi­cient if we want to use only two font fam­i­lies. But if we want to use a third font for our menus, we need to do things dif­fer­ent­ly: […]

Choos­ing good fonts is part of the design. With bootScore we can incor­po­rate Google Fonts direct­ly. We are even told how to host them local­ly, thus bypass­ing the men­tion in the pri­va­cy pol­i­cy. Nev­er­the­less, we have to get a lit­tle involved with Boot­strap as well: […]

In bootScore Top­pings, I’ve already offered two slim land­ing pages: mylap-sp1r­p1 and mylap-sp0r­p1. Both show the impor­tant things first: The blog top­ic. And the most recent post. One of them addi­tion­al­ly puts the most recent Sticky Post in front of the oth­er. But if we want to show our read­er the one or oth­er sticky post more dis­creet­ly, it needs anoth­er solu­tion: […]

Until now, the land­ing page mylap.php — as a tem­plate linked to the Word­Press page mylap — also shows only a list of all posts. But our favorite read­er had ‘pre­scribed’ us that she want­ed to see only the most impor­tant on the ini­tial page. And that at a glance. The most impor­tant thing in a blog is prob­a­bly always the most recent post. Plus maybe the most recent ‘sticky post’, that is, the one that the author marked last so that it should always be shown at the top: […]

We need dif­fer­ent side­bars: The tag cloud makes sense only on the side­bar of the search page. There it can short­en the search in the set of arti­cles. On the oth­er pages, it dis­tracts the read­er. Con­verse­ly, the oth­er pages need a ‘more’ but­ton in the side­bar that leads to the sur­vey page. In oth­er words, we need (at least) two dif­fer­ent side­bars: […]

My pages are too full, my pre­ferred read­er says: She con­stant­ly gets some­thing to click on anoth­er arti­cle. She under­stands why. I want­ed to entice her to read on. Like a real news por­tal. But my con­tent was not broad enough. I only want to talk about a few core top­ics. So, too much is just too much. […]