We're time traveling back to 1997 today, when WISYWIG editors were all the rage. In the decades since, web technology has clawed its way from that primitive state with semantic HTML that made accessibility possible and let content drive appearance rather than vice-versa. Then Figma blew it all up. - ThreadSky

spavel.bsky.social • 21 days ago

We're time traveling back to 1997 today, when WISYWIG editors were all the rage. In the decades since, web technology has clawed its way from that primitive state with semantic HTML that made accessibility possible and let content drive appearance rather than vice-versa.

Then Figma blew it all up.

Comments

areoff.bsky.social•21 days ago

My issue with being a designer who has the misfortune of working in UI design is encapsulated perfectly in the quote about pictures of websites. It’s something I’ve often said to people about my hatred of how we have to work in this industry.

whitep4nth3r.com•21 days ago

Oh snap. I took it back to 1995.

https://bsky.app/profile/whitep4nth3r.com/post/3loqjmik53s2p

wheelyweb.bsky.social•20 days ago

I was there and I definitely been there and done that. All of that.

spavel.bsky.social•20 days ago

I love it whenever the community overcomes our differences to come at some bullshit as a united front

spavel.bsky.social•21 days ago

Thanks to @bell.bz @heydonworks.com @lapope.bsky.social @andreasmoller.dk @kevinpowell.co and everyone else who either isn't on bsky or whose names I can't find

russ.amodernremedy.com•20 days ago

Figma Elementor

amentler.bsky.social•21 days ago

Yes right but wysiwyg not wisywig.

aendra.com•21 days ago

I'm screaming inside from that dropcap example.

spavel.bsky.social•21 days ago

It's so impressively bad

bcgreenwitch.bsky.social•21 days ago

Although I agree with a lot of this, the problem with the "content model first" approach is that it expects or wants a static content model. This is like trying to get a static schema from Day 1 - ain't gonna happen. You need *a* content model but also some hypotheses in how it will stay or change.

stevebromley.bsky.social•21 days ago

@r4isstatic.com lots here I think you’d agree with, if you’re not subscribed already!

r4isstatic.com•20 days ago

Yes, and yes I am! 😁

dontinnovate.bsky.social•21 days ago

Is WISYWIG a clever play on WYSIWYG?

spavel.bsky.social•21 days ago

No, I was just using only 3% of my power to write this post

radiofreezerg.bsky.social•21 days ago

Me, in 2004, slicing the psd to export as html: there's gotta be a better way

Professionals over the subsequent decade: you bet your ass there is

Me, in the present, addressing my agency: yeah it's sure a pretty picture, but what are the chances it stays this pretty when there's content?

spavel.bsky.social•21 days ago

As a: user
I want to: go to the website
So that: I can see it

wheelyweb.bsky.social•21 days ago

You joke but I’ve read entire documents in the not too distant past that did exactly that.
As a user I want the {feature name} so that I can use the {feature name}

ptolemarch.bsky.social•20 days ago

As a Product Owner I want the Development Team to create the Feature

radiofreezerg.bsky.social•21 days ago

Damn, that makes so much sense. I thought it was so that you could look at a bold sentence against a full-fold animated background with parallax.

coconnor8.bsky.social•21 days ago

Began my career decades ago as a document indexer. Technologists have been failing to make semantics unnecessary the entire time

caspianievers.bsky.social•21 days ago

Enjoyed reading that.

chromaticnova.com•20 days ago

WYSIWYG isn’t automatically bad, and Figma hasn’t blown anything up yet if nobody uses it or they fix their issues.

They should absolutely be called out though, to ensure that they ARE fixing issues.

andrewhinton.bsky.social•21 days ago

cc @carrieh.bsky.social who gets a deserved mention

Comments

Posting Rules

Reply