Release - Document v4 (Migration Guide and Feature Additions)

[TheLarkInn]

Hey docs team and all of our beloved contributors!!!!

We are getting close to merge webpack/webpack#next (v4) into master soon and we have drafted a WIP change log and this means we can start laying the ground work and documentation for our migration guide and other changes!

Listed is the link to the changelog:

https://github.com/webpack/webpack/wiki/Changelog-WIP

I'd give you ownership to break up the work however you see fit! Let me know if the core team can help in any way!!!

🔥🔥Lots of exciting changes!🔥🔥

[reergymerej]

I've got a PR in core that modifies a new feature (sideEffects in package.json) and I'd like to make the sister change in the docs. Can anyone point me in the right direction?

[skipjack]

Hmmm, maybe in the API section somewhere? Also target your PR to the next branch.

[reergymerej]

Thanks, @skipjack. I searched the next branch and didn't see anything. I may be the first to add it.

[skipjack]

From #1795...

Create an upgrade path section with clearly defined, individual pages:

• Upgrade from v1 to v2
• Upgrade from v2 to v3
• Upgrade from v3 to v4

Each page should include any script helpers, and examples particular to it's version of the upgrade.

[skipjack]

I like the note from from #1795 though in terms of actual wording/implementation, I think we should create a "Migrating" group under Guides and title the articles simply v1 - v2, v2 - v3, etc. (or 1.x.x to 2.x.x).

[TheLarkInn]

Here is the first issue with a set of migration diffs. I think this is something we can run with?

#1706

[TheLarkInn]

@skipjack, I've been starting to make a bunch of videos that are going to hopefully be embeddable into our documentation. I'm not sure where I can start to organize them. Would it work best to dump into a standalone issue?

[TheLarkInn]

I like the note from from #1795 though in terms of actual wording/implementation, I think we should create a "Migrating" group under Guides and title the articles simply v1 - v2, v2 - v3, etc. (or 1.x.x to 2.x.x).

Has this already landed in next branch? If not, I will create an issue so that first time contributor can tackle just this work (creating the group).