Determine if the content is potentially outdated based on the date of the blog posts

[rozsazoltan]

It's misleading when the version number indicates that I'm reading a 4.1 page, but the blog content from 2021 is actually related to version 3. I don't have much of an issue with this, but sometimes I get caught off guard by it. I think it could be easily implemented with a warning message, possibly with a link pointing to the current content.

• init command not available tailwindcss#15791 (reply in thread)

I'm not sure if it's necessary, but I'll leave it as an idea.

[rozsazoltan]

This solution applies exclusively to the Standalone CLI: #2214

[philipp-spiess]

I don't think this is a very big issue -- When you're reading a blog post it does not necessarily feel like it has to be updated to the new API, that's why there's a date on the very top. Blog posts are written to be read closer to when they are published and I don't think I have the expectations that the examples are evergreen.

The Standalone one is a bit special since it is linked from within the docs so I agree that #2213 is something we want to fix 👍