4 ms·

Why is this blog on a sudomain of wpcomstaging.com? Is this actually an official site by fontawsome? If yes, what a pack of clowns. I hope their spam emails ro

• layer8 6mo ago
  The official blog is here: https://blog.fontawesome.com/we-have-a-99-email-reputation-gmail-disagrees/ https://blog.fontawesome.com/we-have-a-99-email-reputation-g...
  • jonas21 6mo ago
    But if you look at the HTML on the official blog, it has the tag: <link rel="canonical" href="https://blogfontawesome.wpcomstaging.com/we-have-a-99-email-reputation-gmail-disagrees/"> So... still a bit of a clown show (and maybe why it got submitted to HN with the wpcomstaging.com subdomain).
• ValentineC 6mo ago
  > Why is this blog on a sudomain of wpcomstaging.com? I find it ironic that they "acquired" Eleventy and are developing Build Awesome Pro [1], but can't bring themselves to dogfood it. They do have an alpha version of Build Awesome Pro, right? [1] https://blog.fontawesome.com/pausing-kickstarter/ https://blog.fontawesome.com/pausing-kickstarter/
  • zachleat 6mo ago
    Howdy y’all! Eleventy maintainer and member of Font Awesome here. Just saw this (I don’t regularly read HN). Looks like someone shared the staging URL for the old FA WordPress blog on HN? I’ve updated the WordPress staging site to redirect to the new Build Awesome/Eleventy version at blog.fontawesome.com so that it doesn’t happen again. Sorry about that! You can read about the 2025 dogfood migration here: https://blog.fontawesome.com/blog-awesome-to-11ty/ https://blog.fontawesome.com/blog-awesome-to-11ty/
    • em-bee 6mo ago
      the staging url wasn't shared, but the published page references the staging url as the canonical url so HN automatically updated the submitted url to that. that reference is what you need to fix.
      • zachleat 6mo ago
        Well, shit. You’re absolutely right! That was 100% my fault and it’s fixed now.