@volpeon

Admin

Wyvern-shaped software developer and hobby vector artist. Also sometimes a fluffy werewolf alien creature (Areon).

Creator of the neofoxes, neocats and other emojis.

Website https://volpeon.ink/

Speaking German, English

Age 30s

Pronouns he / him

Backup Account @volpeon@goto.wyvern.rip

Bonus Content @areon@icy.wyvern.rip

Volpeon

@volpeon@icy.wyvern.rip

@vel DeutschlandGPT

Volpeon

@volpeon@icy.wyvern.rip

↘️ Motivation to work for the remaining 2 hours at 5% and rapidly decreasing

Volpeon

@volpeon@icy.wyvern.rip

If you ever need to construct a true random number generator, just use my fucking space heater

Volpeon

@volpeon@icy.wyvern.rip

Space heater: (does nothing)
20 minutes later, nothing has changed
Space heater: "Oh, I should heat the room up to the sun's surface temperature

Volpeon

@volpeon@icy.wyvern.rip

@flisk Montage sein wie

Volpeon

@volpeon@icy.wyvern.rip

Miss SQL (MS SQL)

Volpeon

@volpeon@icy.wyvern.rip

@nova Cats live the ideal life

Volpeon

@volpeon@icy.wyvern.rip

@dhalucario Because it's a commentary about the mentality that's pretty common here rather than a reply. I also don't want to seem confrontational because they're doing their best and I fully understand that doing something like Bluesky is incredibly hard given that there are dozens of fedi servers and third-party frontends that would have to cooperate.

Volpeon

@volpeon@icy.wyvern.rip

The problem is that these projects aren't easily discoverable and integrated into the user interface, unlike Bluesky. You can't convince me that they're even remotely as usable or convenient as this: (see attachments)

Fedi has a tendency to handwave legitimate usability concerns because a lot of people here are more technically inclined than the average person. It's frustrating because it only blocks the way for better solutions.

RE social.chinwag.org/@FediThing/113469817542409948

Volpeon

@volpeon@icy.wyvern.rip

It's about to be that time again

Volpeon

@volpeon@icy.wyvern.rip

@raccoon @volpeon This one?

Volpeon

@volpeon@icy.wyvern.rip

@sirlan There are 3 parts to it:
- Icons: git.vulpes.one/iro-icons/
- Sass framework: git.vulpes.one/iro-sass/
- Design system: git.vulpes.one/iro-design/

The design system also has Pug templates so I can quickly prototype components.

Don't expect much in terms of commit quality.

Volpeon

@volpeon@icy.wyvern.rip

AAAAAAAAAA MONDAY

Volpeon

@volpeon@icy.wyvern.rip

I'm really happy with my website redesign. I'm getting lots of cool components for future projects out of it, I'm working with a framework that's way more fun (but also more complicated) to use than Hugo, I made a new logo where I used negative space for the first time, I got my mobile UX knowledge up-to-date, and the website looks fucking great.

Volpeon

@volpeon@icy.wyvern.rip

@natty That one comes with an unexpected surprise, by the way: My sticky header stopped following after a while. So if you want the header to work normally, you have to not make the body scrollable but the main element instead. But then other (mostly JS-related) things stop working properly because they operate with the assumption that the root container is scrollable. It's such a mess.

Volpeon

@volpeon@icy.wyvern.rip

@erincandescent The cool thing about position: sticky is that it reserves the space of the element which gets really important when the footer's height isn't static

Volpeon

@volpeon@icy.wyvern.rip

@natty Which is less straightforward than "header { position: sticky; inset-block-start: 0 }", which is what I was talking about.

Volpeon

@volpeon@icy.wyvern.rip

It's a bit silly that we have "position: sticky" in CSS, but there still isn't a straightforward way to have a sticky footer at the bottom of the viewport even when the page content isn't tall enough. You have to use flexbox or grid, I also came across solutions that only worked in Chrome and then stopped working...

Volpeon

@volpeon@icy.wyvern.rip

cc @vel

Volpeon

@volpeon@icy.wyvern.rip

If the logo mlems, it's a good omen

❮ Previous page Next page ❯