@javiereguiluz Would it be a good idea to link blog post to new features like this?

They are insightful sometime and they may give more example. They may be outdated too perhaps?

@B-Galati in some posts we link to the related Symfony Docs ... but for unmerged PRs, we very rarely do that because of their uncertainty (will they be merged? will they be replaced by other PRs? etc.)

Sorry I did not explain myself correctly. I meant having links in the doc that would point to the blog post where the feature has been highlighted.

Sounds like a good idea IMO and in both ways:

Blog post -> documentation: Once you remind a feature you heard about thanks to blog posts you have to dig into the documentation to have more information. For this reason, having a link to the documentation in the blog posts could be useful. On the other hand, it can lead to dead links when the documentation move which is definitively not useful at all. Furthermore, as you said @javiereguiluz, documentation is generally not (yet) available online when a blog post is published.

Documentation -> Blog post: Having a link to the blog post from the documentation is also useful: you can sometimes find a bit more information regarding the context of the feature / improvement (the "Why?") instead of "just" having the detailed explanations (the "How?"). The only drawback I can think about may be the readability: too much links to blog posts could be counter productive but it's probably easily avoidable.

That's said, it's just the opinion on someone who don't contribute to the documentation! xD

I disagree with the proposal to link to blog posts. The reason is that blog posts are "volatile" and "out of context" (each post is independent, it doesn't take into account versioning, deprecated features, etc.), while docs are designed to be "perpetual and contextual".

Besides, posts and docs talk about the same/similar things, so we would just create confusion with this duplication.

This PR has been closed because the master has been removed.
Please submit it again against the appropriate branch.