Webpack.js.org: Concepts - "Why webpack?" Section

[TheLarkInn]

Linked is one of the best explainers (and is trending on Reddit [or was]) on _why_ bundlers are what someone should use for High Performance web applications (and ergonomics). I'd like to see a "Why webpack". or "Why bundle". section somewhere as a top tier callout to visitors of the page.

This probably represents the final high level gap for general overview and resoning knowledge that we are missing here on the docs site.

Going to label this as a contribution opportunity, however @skipjack @TheDutchCoder if you have a great ideas where this could go, feel free to comment, design that location.

[gezeta-id]

Just so that it is clear: As I said in the original reddit comment, feel free to copy all, parts, pieces, tiny bits or whatever you want from my comment. No attribution needed or anything. If it helps you, great 😄

[TheLarkInn]

Thank you kindly! @gezeta-id

I'd try and twist you to submit a PR for this but you've already done so much. This is a great contribution opportunity too for first timers also.

[skipjack]

So we actually did used to have a page called "Why Webpack?" but I think it was renamed as "Comparison" (which makes sense for what the page contains). I think the best place for @gezeta-id's content would be the index page in __Concepts__. Nice work on that post @gezeta-id and I do think it would be a useful add to the site. Whoever ports that post would have to clean up the grammar and tighten it up as much as possible. That said, I do think the story being told is perfect for the __Concepts__ section.

I'd like to see a "Why webpack". or "Why bundle". section somewhere as a top tier callout to visitors of the page.

The lead-in page of __Concepts__ would be perfect as it's already the first link under __Documentation__ and has a callout on the landing page:

Interested in @jeremenichelli's and @TheDutchCoder's thought as well. Updating the title/labels to reflects my suggestion of the __Concepts__ section but we can change it if we decide there is a better place for it.

[TheDutchCoder]

I, too, love this idea of explaining "why" one would need (or like to use) webpack.

When we redid the guides it was very much beginner focussed (I'm literally a newbie at webpack and helped rewriting them for people like me) and I think this ties into that nicely.

Having it front and center in the navigation is vital as well, as I think a lot of beginners could use the encouragement and explanation it provides. The whole "let's take this one step at a time" approach resonates with me as a beginner, it's excellent!

Webpack is a bit "scary", but as this post illustrates, it really doesn't have to be and you (and probably should) start super small, get familiar with it, and then scale it up.

Anyway, enough rant, I'm 💯 for this idea and great work @gezeta-id !

[MythicalFish]

I bookmarked that comment because it was so good, and now that I want to refer to it again, it's gone! Deleted. :(

Did anyone here save it somewhere per chance?

[gezeta-id]

Oh, sorry, sorry! I forgot to tell you.

The reddit content on that account is usually deleted after a time, so I just moved it _without modification_ to a more _stable_ location: This is the original text as was published in reddit. This is a somewhat cleaner version
The _clean_ version will be kept there for the foreseeable future, the other, unedited one maybe not. Still, let me remind you that you're free to copy it, if you so prefer.

[TheLarkInn]

Thank you for publishing this to keep it accessible!! I think it is a perfect start for our documentation. Just need to figure out how we want to structure the message we send and find out where it would be sent 💯

[chrisdothtml]

This seems more fitting for a post on the Webpack Blog. Could just be linked to where @skipjack screenshotted. Something like:

Struggling to understand webpack? [This blog post] might help.

[sudipt1999]

@TheLarkInn may I work on this ! kindly provide me pointers to begin with !