It would be great to set limits on how much leave is scheduled at once or per quarter. My company says you should ask a manager if you book more than 25% of leave per quarter, so it would be good to know the max I can book without having to ask for permission.
Delays got us to this month. Other delays got us to this week. Weather issues delayed it from earlier this week to Christmas. Once you are spooled up for launch, unwinding all of that just to avoid a holiday is not worth it.
Feels like this is not really a constructive critique of OPS argument. Indeed, it is merely them ensuring they can gain reach on the platforms they are critiquing, as opposed to screaming into the void as a Web 1.0 holdout.
Look, I don't like mowing the lawn. I think long grass looks nice.
It isn't hypocritical of me to mow my lawn to avoid fines while still advocating for elimination of the grass ordinances in my city.
To directly address your point: the motivation of web 2.0 sites is to get a bunch of money by making the content hard to read without first looking at a bunch of ads, and futher to disallow a reading experience uninterrupted by adds every 30-60s. The web page in question did not show me any ads.
My question to you is: how do you not see the difference?
I honestly believe there is lots of potential for making people realize this is a position one can believe, hold and live. The bullying from those who care more about some future humans I don't care about is getting out of hand. McDonalds paper straws literally tear the flesh from my lips after sucking the moisture out of them and I am fed up.
Meanwhile, the planet gets hotter and many more people die during heatwaves than 20 years ago. Are you sure your McDonalds experience is more important than preventing more and more people from ceasing to breathe?
I, like most developers, got swept up in the gatsby/Netlify/contentful hype and have been building marketing sites that way for a few years now (mostly for Saas and startups).
The problems with this approach are many. First, getting set up is a giant pain in the ass. And not just the fact that you have to code everything from scratch, it’s the build process headaches, fixing the shitty SEO defaults of the static site generator, fighting over whatever hot CSS framework to use(its 2021 so tailwind now!!), etc. Then hooking the site up to a headless CMS is another big nightmare—-and then training your team how to use it is another.
And that’s just the beginning. Guess what happens when your team(or you) wants to update the marketing site (happens all the time)? You have to go through the nightmare all over again, fix some inevitable build process errors, re-learn how everything works, re-hook up contentful to the new content models, retrain the team again, etc.
Contrast this to the Webflow approach. I built the entire site in a day and haven’t had to touch the marketing site since. Our designer owns it completely now and has already done 2 complete redesigns in the time it would take me to do a small update the old way.
Our copywriter logs directly into Webflow when he wants to change the copy, the designer builds new landing pages for marketing initiatives in a day, and I never get bugged by the marketing team to “update this small thing” since they own it now.
Honestly, I now think the entire static site ecosystem is designed for developers to set up a personal blog using whatever front-end framework they think is “cool” at the time and never add content to it.
I would guess 98% of gatsby/Hugo/etc sites have less than 10 posts on them. And of those sites, there’s a 78% chance the only post is “how I rebuilt this site in Gatsby”
I'm not in the target market (as I find coding easier than learning a new UI) but it's something like this:
- Select a starter template (free or paid)
- Customize text and css, add any elements, the UI is what you would expect from Photoshop or Unity
- Add forms / payment forms
- Publish on a xxxx.webflow.com domain or on a custom domain (for money) - pay extra if you are using e-commerce features
I guess the goal is to shift the market from developers who know how to code to developers who know how to use a UI (similar to what Unity did for game developers).
I'd put Wix, squarespace, etc. in a different category. They are classic sandboxed site builders, you can only do as much as they allow you to.
Webflow is like a modern version of Frontpage/Dreamweaver that actually spits out modern, semantic HTML and sane CSS. You start from scratch and can build anything with it. It's actually hard to use if you don't understand how HTML/CSS works, because the UI is basically just a faster way to do front-end code.
Unsubscribe should definitely be part of this. Or at least a way to stop the emails from sending after a user has unsubbed, otherwise we enter dodgy GDPR complaint territory. Maybe a dealbreaker even. Cool product otherwise! Will keep an eye out for a chance to try it.
We use Neue Haas Grotesk for our design system. and I never knew it had such a history behind it. TIL! Don't know how to say this articulately but I've always thought of it as Helvetica's beatnik cousin.
