docs: update pages

Author: ldez

docs/src/docs/contributing/architecture.mdx

@@ -2,6 +2,7 @@
 title: Architecture
 ---
 
+
 import ResponsiveContainer from "components/ResponsiveContainer";
 
 There are the following `golangci-lint` execution steps:
@@ -94,15 +95,12 @@ func (b LinterBuilder) Build(cfg *config.Config) []*linter.Config {
 		linter.NewConfig(golinters.NewBodyclose()).
 			WithSince("v1.18.0").
 			WithLoadForGoAnalysis().
-			WithPresets(linter.PresetPerformance, linter.PresetBugs).
 			WithURL("https://github.com/timakin/bodyclose"),
 		// ...
 		linter.NewConfig(golinters.NewGovet(govetCfg)).
-			WithEnabledByDefault().
+			WithGroups(config.GroupStandard).
 			WithSince("v1.0.0").
 			WithLoadForGoAnalysis().
-			WithPresets(linter.PresetBugs, linter.PresetMetaLinter).
-			WithAlternativeNames("vet", "vetshadow").
 			WithURL("https://pkg.go.dev/cmd/vet"),
 		// ...
 	}
@@ -160,72 +158,64 @@ type Issue struct {
 	// Source lines of a code with the issue to show
 	SourceLines []string
 
-	// If we know how to fix the issue we can provide replacement lines
-	Replacement *Replacement
-
 	// Pkg is needed for proper caching of linting results
 	Pkg *packages.Package `json:"-"`
 
-	LineRange *Range `json:",omitempty"`
-
 	Pos token.Position
 
+	LineRange *Range `json:",omitempty"`
+
 	// HunkPos is used only when golangci-lint is run over a diff
 	HunkPos int `json:",omitempty"`
 
+	// If we know how to fix the issue we can provide replacement lines
+	SuggestedFixes []analysis.SuggestedFix `json:",omitempty"`
+
 	// If we are expecting a nolint (because this is from nolintlint), record the expected linter
 	ExpectNoLint         bool
 	ExpectedNoLintLinter string
+
+	// ...
 }
 ```
 
 ## Postprocess Issues
 
 We have an abstraction of `result.Processor` to postprocess found issues:
 
-```sh
+<!--
 $ tree -L 1 ./pkg/result/processors/
+-->
+
+```sh
 ./pkg/result/processors/
-./pkg/result/processors/
-├── autogenerated_exclude.go
-├── autogenerated_exclude_test.go
-├── base_rule.go
 ├── cgo.go
 ├── diff.go
-├── exclude.go
-├── exclude_rules.go
-├── exclude_rules_test.go
-├── exclude_test.go
+├── exclusion_generated_file_filter.go
+├── exclusion_generated_file_matcher.go
+├── exclusion_paths.go
+├── exclusion_presets.go
+├── exclusion_rules.go
 ├── filename_unadjuster.go
 ├── fixer.go
 ├── identifier_marker.go
-├── identifier_marker_test.go
+├── invalid_issue.go
 ├── issues.go
 ├── max_from_linter.go
-├── max_from_linter_test.go
 ├── max_per_file_from_linter.go
-├── max_per_file_from_linter_test.go
 ├── max_same_issues.go
-├── max_same_issues_test.go
-├── nolint.go
-├── nolint_test.go
-├── path_prefixer.go
-├── path_prefixer_test.go
+├── nolint_filter.go
+├── path_absoluter.go
 ├── path_prettifier.go
+├── path_relativity.go
 ├── path_shortener.go
 ├── processor.go
-├── processor_test.go
-├── severity_rules.go
-├── severity_rules_test.go
-├── skip_dirs.go
-├── skip_files.go
-├── skip_files_test.go
+├── severity.go
 ├── sort_results.go
-├── sort_results_test.go
 ├── source_code.go
-├── testdata
-├── uniq_by_line.go
-└── uniq_by_line_test.go
+└── uniq_by_line.go
+
+
 ```
 
 The abstraction is simple:
@@ -238,34 +228,26 @@ type Processor interface {
 }
 ```
 
-A processor can hide issues (`nolint`, `exclude`) or change issues (`path_shortener`).
+A processor can hide issues (`nolint`, `exclude`) or change issues (`path_prettifier`).
 
 ## Print Issues
 
 We have an abstraction for printing found issues.
 
-```sh
+<!--
 $ tree -L 1 ./pkg/printers/
+-->
+
+```sh
 ./pkg/printers/
 ├── checkstyle.go
-├── checkstyle_test.go
 ├── codeclimate.go
-├── codeclimate_test.go
-├── github.go
-├── github_test.go
 ├── html.go
-├── html_test.go
 ├── json.go
-├── json_test.go
 ├── junitxml.go
-├── junitxml_test.go
 ├── printer.go
+├── sarif.go
 ├── tab.go
-├── tab_test.go
 ├── teamcity.go
-├── teamcity_test.go
-├── text.go
-└── text_test.go
+└── text.go
 ```
-
-Needed printer is selected by command line option `--out-format`.

docs/src/docs/welcome/faq.mdx

@@ -62,9 +62,10 @@ most linters are not able to perform the analysis,
 and they simply do not produce any reports,
 so it's not possible to skip/ignore `typecheck` errors.
 
-## Why running with `--fast` is slow on the first run?
+## Why running with `--fast-only` can be slow on the first run?
 
-Because the first run caches type information. All subsequent runs will be fast.
+Because the first run caches type information.
+All subsequent runs will be faster.
 Usually this options is used during development on local machine and compilation was already performed.
 
 ## How do you add a custom linter?

docs/src/docs/welcome/install.mdx

@@ -7,8 +7,8 @@ title: "Install"
 Most installations of `golangci-lint` are performed for CI.
 
 It's important to have reproducible CI: don't start to fail all builds at the same time.
-With golangci-lint this can happen if you use option `--enable-all` and a new linter is added
-or even without `--enable-all` when one upstream linter is upgraded.
+With golangci-lint this can happen if you use option `linters.default: all` and a new linter is added
+or even without `linters.default: all` when one upstream linter is upgraded.
 
 **IMPORTANT**: It's highly recommended installing a specific version of golangci-lint available on the [releases page](https://github.com/golangci/golangci-lint/releases).
 

docs/src/docs/welcome/integrations.mdx

@@ -11,11 +11,11 @@ Recommended settings for VS Code are:
 ```json
 "go.lintTool": "golangci-lint",
 "go.lintFlags": [
-  "--fast"
+  "--fast-only"
 ]
 ```
 
-Using it in an editor without `--fast` can freeze your editor.
+Using it in an editor without `--fast-only` can freeze your editor.
 Golangci-lint automatically discovers `.golangci.yml` config for edited file: you don't need to configure it in VS Code settings.
 
 ### Sublime Text

docs/src/docs/welcome/quick-start.mdx

@@ -2,13 +2,15 @@
 title: Quick Start
 ---
 
-To run golangci-lint execute:
+## Linting
+
+To run golangci-lint:
 
 ```sh
 golangci-lint run
 ```
 
-It's an equivalent of executing:
+It's an equivalent of:
 
 ```sh
 golangci-lint run ./...
@@ -39,3 +41,18 @@ golangci-lint run --disable-all -E errcheck
 ```
 
 More information about available linters can be found in the [linters page](/usage/linters/).
+
+## Formatting
+
+To format your code:
+
+```sh
+golangci-lint fmt
+```
+
+You can choose which directories or files to analyze:
+
+```sh
+golangci-lint fmt dir1 dir2/...
+golangci-lint fmt file1.go
+```