Skip to content

Adding minor getting started clarifications #2798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Feb 11, 2019

Conversation

jceipek
Copy link
Contributor

@jceipek jceipek commented Feb 7, 2019

I'm just trying out webpack and the installation and environment variables sections threw me off a bit. Hopefully these minor changes will help others avoid my confusion.

  1. The installation section explains that you need to install the cli for webpack 4 but could be clearer that this is in addition to the webpack package. I added "also".

  2. The environment variables section does not make clear that webpack's environment variables are separate from the environment variables I might set in bash, fish, zsh, etc... I added a tip to that effect.

To disambiguate in your `webpack.config.js` between [development](/guides/development) and [production builds](/guides/production) you may use environment variables.
To disambiguate in your `webpack.config.js` between [development](/guides/development) and [production builds](/guides/production) you may use "environment variables".

T> webpack's environment variables are different from the [environment variables](https://en.wikipedia.org/wiki/Environment_variable) you might be used to from the shell where you're running webpack
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think that quoting them before and putting war here is correct, can you remove the quotes above.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was aiming to use quotations to indicate uncommon usage (see https://style.mla.org/quotes-when-nothing-is-being-quoted/), but I'm fine with getting rid of them.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes i understand, but it looked weird when i read through that version of the page, same term with different styling in sibling paragraphs... Another thing here is that we are doing an assumption in the docs. Recently we'd received many PRs removing such statements. Can we get rid of you might be .... and just state the facts

Copy link
Contributor Author

@jceipek jceipek Feb 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed. I understand the rationale (for example, this commit is fantastic: be90987), but in this case, I think it might be slightly worse, since the sentence is referring to a concept unrelated to webpack. My use of the phrase "you might be used to from" was intended to cause readers unfamiliar with the idea of environment variables and operating system shells to disregard the tip. Now such a reader needs to confront their own level of understanding with the concept of shells and environment variables (i.e. it's making the assumption that they know what a shell is).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On a related note, the writing contribution guide makes no mention of writing style. It would be great if a maintainer could edit it to provide examples of phrasing that would or would not be appropriate, based on the design goals of the documentation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good point! that is tbd soon

@EugeneHlushko EugeneHlushko merged commit 278854a into webpack:master Feb 11, 2019
@EugeneHlushko
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants