Skip to content

Concepts - Review, Organize, Define Clear Goals #1386

Closed as not planned
Closed as not planned

Description

@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

Activity

  1. TheLarkInn commented on Jul 11, 2017

    @TheLarkInn
    Member

    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.

  2. tanyagray commented on Jul 12, 2017

    @tanyagray
    ContributorAuthor

    @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.

  3. TheLarkInn commented on Jul 12, 2017

    @TheLarkInn
    Member

    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.

  4. TheLarkInn commented on Jul 12, 2017

    @TheLarkInn
    Member

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

  5. shaodahong commented on Jul 12, 2017

    @shaodahong
    Contributor

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

  6. tanyagray commented on Jul 12, 2017

    @tanyagray
    ContributorAuthor

    Documenting issues is a good idea. Will do.

  7. TheLarkInn commented on Jul 16, 2017

    @TheLarkInn
    Member

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

  8. TheDutchCoder commented on Oct 26, 2017

    @TheDutchCoder
    Contributor

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

  9. alexander-akait commented on Sep 11, 2026

    @alexander-akait
    Member

    The concepts section has been reorganized several times since this was opened in 2017 and now has a defined set of pages (Entry Points, Output, Loaders, Plugins, Configuration, Modules, Module Resolution, Module Federation, Targets, Manifest, Under the Hood, Why webpack). Closing this open-ended review; specific gaps are better tracked as their own issues.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions