The .editorconfig Generator builds the file that keeps whitespace and encoding consistent across editors. Set the rules for [*] and a couple of common per-file overrides.
It runs in the page and remembers your choices in your own browser.
No. Only the properties you set appear, so editors fall back to their own defaults for the rest.
It stops EditorConfig from looking in parent directories, so this file wins. Leave it on for a repository root.
The generator covers the common ones; add extra sections by hand.
No. The file is built in your browser.