Skip to main content

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen, and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying.
Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay.

P.S. Resolved the cache issue with .htaccess file:
FileETag None
Header unset ETag
Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT" 
everything now works a lot livelier.

P.P.S. Why is Blogger's interface so ugly and ancient? I've been working with WP for the last year... soooooo much better...

Popular posts from this blog

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page, you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic…

Yamaha Custom "Z" Tenor Sax YTS82Z

That's it. I have no more excuses. I have to really start playing now...
On Saturday, after several hours of talking and drinking we (Evelyn & I) achieved the state of mutual understanding of the necessity of acquiring a new instrument. Basically, she convinced me, that I need one.
Since "we are not rich, so we can't afford cheap things" attitude was a driving force behind all financial decisions in our family for the last 20+ years, the plan was to go for the gold (no pun intended). I was to start researching the market, going places, and checking out various horns in order to find the one and only I would like to play for the rest of my life.
The candidates were Selmer III Series, Selmer Reference 54, and, may be, pro-level Yamaha, or Yanagisawa, to compare at least - don't I need to know what I want before I spend 4+ kilobucks on something shiny? They don't make Mark VI anymore, that's a shame; however, used one is not an option for me: I like to …

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself).
Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme):

function childtheme_twentyseventeen_fonts_url() {
$replace_original_font = true; // unless you really like Libre Franklin
if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; };
$font_families = array(
//add your Google fonts and weights (400 and 700 are defaults for normal and bold) here:
$query_args = array(
'family' => urlencode( implode( '|', $font_families ) ),
'subset' => urlencode( 'latin,latin-ext' ),
$fonts_url = add_query_arg( $query_args, '' );
wp_enqueue_style( 'twentyseventeen' . $hyph . 'font…