Zum Inhalt springen

Archiv für die Kategorie "English"

The Dangers of Being a Web Developer - Jens Oliver Meiert @ Beyond Tellerrand Düsseldorf 2018

view directly on vimeo

I've been following Jens' output for over a decade now. Not regulary, but every now and then some of his smart observations and thoughts surface in my information stream.
So I was excited to see his name in the speakers list, and his talk about the pros and cons of being a web worker did resonate with me.

So thank you Jens, for reminding me why I am doing this for two decades now. And again, that I am not alone, even though I often feel isolated when working in clients work, feeling like I ...

Eight Years Beyond Tellerrand

This will be a short blog post, because I want to get out some thoughts as quickly as possible, not waiting for that time that never comes in which I sit and craft a well written lengthy text.
Which is why I didn't blog for some years now after I visited Marc Thieles phantastic event, even though I managed to be at least once in a year at one iteration of this very special conference.

So what has changed?

Well, nothing really, it is just that I want to ...

How to Build an Atomic Bomb - Mike Monteiro @ Beyond Tellerrand Düsseldorf 2018

view this directly on vimeo

Wow. It was on the historical date of May 8th, that Mike Monteiro held this intense talk, reminding each and everyone who cared to listen of the conseqences and the possible impacts of the "I'm only doing my job here" mentality.

This talk gave me several goose bumps, having seen "5 came back" only recently, and still seeing this one shot of the inside of a german concentration camp, where right after the allied troops went in, a film team documented not only the unimaginable horror and piles of dead and starving ...

The indieweb privacy challenge (webmentions, silo backfeeds, and the GDPR) - Sebastian Greger

A thorough article on the current challenges, technically and ethically, regarding the use of elsewhere published public data that can be regarded as 'personal data' in the GDPR/DSGVO sense. Data that will be published for example by pulling in likes, shares and comments posted on Twitter here in my blog, as 'reactions' alongside with 'real' comments on my posts.

As Sebastian writes

Just the fact that I can aggregate a “facepile” showcasing everybody who clicked “like” on a tweet of mine does not mean that my motivations for doing so are more important than their right to stay in control

...

The Illusion of Control in Web Design - Aaron Gustafson

Recognizing all of the ways our carefully-crafted experiences can be rendered unusable can be more than a little disheartening. No one likes to spend their time thinking about failure. So don’t. Don’t focus on all of the bad things you can’t control. Focus on what you can control.
Start simply. Code defensively. User-test the heck out of it. Recognize the chaos. Embrace it. And build resilient web experiences that will work no matter what the internet throws at them.alistapart.com

From hexcodes to eyeballs

A great article diving into the maths and physics of colour reception and reproduction.

… an exploration of electromagnetic radiation, optical biology, colorimetry, and display hardware …jamie-wong.com

DWNTLETSIEB* revisited

No, websites do not need to look exactly the same in every browser, but while styling a details/summary element recently, I thought I had found smart way to make the default "open/closed" markers behave visually a bit nicer without resorting to re-invent several wheels and hacking my way with "::before" contents:

.acc-trigger {
list-style-type: none;
}
.acc-trigger .section__heading {
color: #900;
cursor: pointer;
display: inherit;
list-style-type: disclosure-closed;
list-style-position: inside;
}
.acc-item[open] .section__heading {
list-style-type: disclosure-open;
}
.acc-item .content {
margin-left: 1.25em;
}

Problem is: even without looking at another platform, Firefox, Safari and Chrome on my Mac can't find a common ground on how this should be rendered.

Firefox is spot on to my intentions:
A ...

Let there be Web

(to the tune of AC/DC's Let There be Rock):

Let there be TCP/IP
and there was TCP/IP
Let there be HTML
and there was HTML
Let there be CSS
and there was CSS
Let there be JS
and there was JS

Let there be Web

And it came to pass
That the Web was born
All across the land every webmaster
Was blowin' up a storm
And the conference man man got famous
The business man got rich
And in every bar there was a superstar
With a seven year itch
There was fifteen million fingers
Learnin' how to code
And you could hear the fingers tippin'

And this is what they had to say…

LET ...

Syndicate some Blogposts from WordPress to Kirby with the REST API

New year, old problems, new Website -- this was my reasoning during the christmas holidays, and so I decided to completly wipe my "About me" website, making it a simple hub of my diverse activities and interests instead of the old "hey, look how cool experienced I am, come work with me and give me all your money" thing.
I decided to build the site with Kirby, a lovely file based CMS which I have used in the past (for example to drive our Frankfurt Open Device Lab website). Kirby is very flexible, has a stellar documentation, a nice API, and makes zero assumptions on how you want to build your site, and besides being file based, it offers a very customizable backend, if need be.

Now, one of the things I wanted on the new site was a way to display the latest posts from here, my blog, but only those relating to the topics of Design, Webdevelopment and the like.

With a little bit of diving into the WordPress REST API, this turned out to be a fairly simple task for my Kirby-site. Basically this REST API allows me to "get" the infos needed on various objects of my WordPress site, by calling the API's entry points and telling it what I want.