Concepts - Review, Organize, Define Clear Goals

[tanyagray]

The content of the Concepts section needs to be reviewed for the following:

• Overall goals and target audience of the concepts section
• Organisation and structure of key concept areas
• Content - anything missing?

cc @TheLarkInn

[TheLarkInn]

I'll start with the goal(s):

I started writing the Concepts section modeled after some of the talks I had done at conferences prior to. It featured talking about key concepts vs configuration properties that I felt people should be aware of.

GOAL: Give people a clear super-high level overview of how webpack works by teaching them the 4 main pieces that one might use in their configuration. This should give people enough confidence to run with it, understand how to use any loader or any plugin, or leverage any entry or output properties with basic usage.

With that in mind, I'm really happy to have you gauge if you feel we are lacking or needing more information. It is admittedly hard for me to tell whether or not the information is enough to leave people confident.

[tanyagray]

@TheLarkInn would you say the Concepts section is targeted at people who possibly have not used a bundler before? If so I have some re-wording suggestions that I'll do PRs for.

[TheLarkInn]

Yes!! Not only no bundlers, but no understanding of a js module. I picture me circa 2 years ago never seeing module.exports and export default and how grunt just concatenates stuff together.

[TheLarkInn]

Are you wanting to do in one pass or document issues, then that way we can track it? Take step by step etc.

[shaodahong]

@TheLarkInn Webpack base on module, but if no understanding of module, should be suggust to study module, Is this mean?

[tanyagray]

Documenting issues is a good idea. Will do.

[TheLarkInn]

Awesome I just saw that! It's a a great audit. Do you want to tie it to this one?

[TheDutchCoder]

Currently working on #1416 with PR #1673
Thanks for bringing this to our attention @tanyagray 👍