Survey Of All Posts!
Linking Bootstrap and WordPress to get a responsive design is the task of bootScore, a WP-theme bringing along what the web designer actually does not want to program herself. Instead, she can now rely on an MIT-licensed preliminary work hosted on GitHub. But its ‘standard outfit’ still must be personalized, ‘pimped’ — by the work of a Web Designer? The theme is adapted — so bootScore — by modifying its “[…] .scss, .php, and .js files”. So you can pimp your bootScore easily. Here are my 13 steps from a pure bootScore to my personal ‘homepage’: […]
Without permission, we may not write cookies to the hard disk of our reader. Because it belongs to her, not to us. By accessing our site, she has already implicitly given her consent to store our technically necessary cookies. Because they are technically necessary to read our post. But she must explicitly permit us to save the other cookies on her computer before we are going to do so. Moreover, we must have enabled her to query what these cookies are for before we offer her to answer our request. That’s the meaning if we talk about properly used cookies. […]
Last time it wasn’t hard anymore: Within two days my post about my ‘reset’ because of lacking an ‘inner linking’ and about the ‘right way to be crawled and indexed’ had been processed by Google. Like my revised posts, I had designed it in accordance with the recommendations of YOAST that take into account Google’s ‘unspoken’ specifications — as proclaimed by YOAST. However, by following these rules, I had also given in to the stylistic superiority of Google and YOAST: […]
It’s a while ago, that I wrote about SEO. That should not be a big deal, I thought at that time. In its templates, bootScore thankfully uses semantic HTML tags by default. Thus, it should be sufficient to submit one’s own sitemap to Google & Co. Enriching the pages themselves with additional keywords should be superfluous. A good primary content would be enough. No need for a second text behind the actual one. That’s the way, I thought. Moreover, I saw no reason to talk about internal linking. Rarely has Google so embarrassingly proven me wrong: […]
Often the website operator is told, that Data protection is complex and has to be organized by experts. But what if she doesn’t have the money for that? If it seems somehow nonsensical to shoot at a sparrow blog with the cannon of a paid team of experts? Then — maybe and with the help of Google — she installs some popular WordPress plugins for data privacy and DSGVO and/or cookies — in the hope that all goes well. Or she investigates it in more detail. And in the end, she perhaps gathers rules of thumb, from which at least one well-workable way results. Here are my 3.7 rules of thumb, applied to my own data privacy file: […]
bootstrap and bootScore use SCSS variables — as we know. Grouping fonts is done by variables. And we can define two groups. This is sufficient if we want to use only two font families. But if we want to use extra fonts — for example, a special google font in our menus -, we need to do things differently: […]