Author here. Thanks for the feedback. Vocabulary helps in my experience, but definitely doesn't make the user or the LLM a great designer. I toned down some of the language on the landing page, as it had sometimes too…
Author here. I ironically spent a lot more time crafting the commands and skill, and not enough time on the landing page. Agree that I overdid it on "editorial look" to match the cheeky domain name. Thank you for the…
Author here, fair feedback. These examples were rushed, and didn't come out great. For this particular one, the concept was 'trustworthy, expensive life sciences company" of sorts, but it's still not a great…
Agreed. Removed.
Should be fixed now. Sorry about that.
poor choice indeed, and I say this as the one who put the example there.. I rushed and tried to make a case of removing the AI slop aesthetics but you're right, got functionally worse. The examples didn't communicate…
Fair feedback. Removed the section for now, will replace with better, real examples.
Author here. Fair. Mentioned this in another reply, but yes, the case study examples were poor, and I shouldn't have shipped those. Ironically I've used these design commands on a production project very effectively,…
Author here. I agree that that wasn't a strong example. I wasn't happy with the outcome of those before/after examples, it was rushed before the launch, and I shouldn't have shipped it. Removed. I mostly use these…
Author here. That's actually great feedback. I accidentally broke the container scroll with a single line CSS change to fix something else, ugh. Should be fixed now.
AMP team member here. Not sure I understand the issue. It's by design that our site is only available via HTTPS. Is there a good reason for why you can't consume the HTTPS version?
We're working on it! We heard this feedback a few times. Our intention is to make mobile the default in DevTools, but we don't want to make the experience worse for people building Desktop sites. So we'll come up with a…
Author of the linked post here. Definitely wasn't our intention to leave Desktop behind. A mobile-only world isn't better than a Desktop-only world. Thus, mobile first. Start with the most common scenario and build your…
...aaand it's fixed. Was a stupid recent spelling mistake.
OP here. It was 4-5 years ago and feels like an eternity. You're right though, "a few" would make more sense! Corrected :)
Thanks for letting me know! Will fix.
OP here. Thanks for the bug report! I'll fix. It's true, haven't used IE in the while, but that wasn't the point of the article. I care deeply about the web as a whole, and all of its evolution.
OP here. I actually agree, and that seems to be Google#s stance right now, from what I've heard (I work for Google but wasn't involved in the technical work on this feature so far). We might need an API that is slightly…
Author here. Thanks for the feedback. Vocabulary helps in my experience, but definitely doesn't make the user or the LLM a great designer. I toned down some of the language on the landing page, as it had sometimes too…
Author here. I ironically spent a lot more time crafting the commands and skill, and not enough time on the landing page. Agree that I overdid it on "editorial look" to match the cheeky domain name. Thank you for the…
Author here, fair feedback. These examples were rushed, and didn't come out great. For this particular one, the concept was 'trustworthy, expensive life sciences company" of sorts, but it's still not a great…
Agreed. Removed.
Should be fixed now. Sorry about that.
poor choice indeed, and I say this as the one who put the example there.. I rushed and tried to make a case of removing the AI slop aesthetics but you're right, got functionally worse. The examples didn't communicate…
Fair feedback. Removed the section for now, will replace with better, real examples.
Author here. Fair. Mentioned this in another reply, but yes, the case study examples were poor, and I shouldn't have shipped those. Ironically I've used these design commands on a production project very effectively,…
Author here. I agree that that wasn't a strong example. I wasn't happy with the outcome of those before/after examples, it was rushed before the launch, and I shouldn't have shipped it. Removed. I mostly use these…
Author here. That's actually great feedback. I accidentally broke the container scroll with a single line CSS change to fix something else, ugh. Should be fixed now.
AMP team member here. Not sure I understand the issue. It's by design that our site is only available via HTTPS. Is there a good reason for why you can't consume the HTTPS version?
We're working on it! We heard this feedback a few times. Our intention is to make mobile the default in DevTools, but we don't want to make the experience worse for people building Desktop sites. So we'll come up with a…
Author of the linked post here. Definitely wasn't our intention to leave Desktop behind. A mobile-only world isn't better than a Desktop-only world. Thus, mobile first. Start with the most common scenario and build your…
...aaand it's fixed. Was a stupid recent spelling mistake.
OP here. It was 4-5 years ago and feels like an eternity. You're right though, "a few" would make more sense! Corrected :)
Thanks for letting me know! Will fix.
OP here. Thanks for the bug report! I'll fix. It's true, haven't used IE in the while, but that wasn't the point of the article. I care deeply about the web as a whole, and all of its evolution.
OP here. I actually agree, and that seems to be Google#s stance right now, from what I've heard (I work for Google but wasn't involved in the technical work on this feature so far). We might need an API that is slightly…