Change documentation files structure

Author: roxblnfk

.vitepress/config.mts

@@ -80,18 +80,18 @@ gtag('config', 'G-VYGDN3X0PR');`],
               text: 'Writing Tests',
               link: '/docs/writing-tests',
               items: [
-                { text: 'Test Attribute', link: '/docs/test-attribute' },
-                { text: 'Naming Conventions', link: '/docs/naming-conventions' },
-                { text: 'Inline Tests', link: '/docs/inline-tests' },
-                { text: 'Data Providers', link: '/docs/data-providers' },
-                { text: 'Lifecycle', link: '/docs/lifecycle' },
+                { text: 'Test Attribute', link: '/docs/plugins/test' },
+                { text: 'Naming Conventions', link: '/docs/plugins/convention' },
+                { text: 'Inline Tests', link: '/docs/plugins/inline' },
+                { text: 'Data Providers', link: '/docs/plugins/data' },
+                { text: 'Lifecycle', link: '/docs/plugins/lifecycle' },
               ],
             },
             {
               text: 'Guide',
               items: [
                 { text: 'CLI Reference', link: '/docs/cli-reference' },
-                { text: 'Filtering', link: '/docs/filtering' },
+                { text: 'Filtering', link: '/docs/plugins/filter' },
               ],
             },
             {
@@ -134,18 +134,18 @@ gtag('config', 'G-VYGDN3X0PR');`],
               text: 'Пишем тесты',
               link: '/ru/docs/writing-tests',
               items: [
-                { text: 'Атрибут Test', link: '/ru/docs/test-attribute' },
-                { text: 'Конвенции именования', link: '/ru/docs/naming-conventions' },
-                { text: 'Встроенные тесты', link: '/ru/docs/inline-tests' },
-                { text: 'Провайдеры данных', link: '/ru/docs/data-providers' },
-                { text: 'Жизненный цикл', link: '/ru/docs/lifecycle' },
+                { text: 'Атрибут Test', link: '/ru/docs/plugins/test' },
+                { text: 'Конвенции именования', link: '/ru/docs/plugins/convention' },
+                { text: 'Встроенные тесты', link: '/ru/docs/plugins/inline' },
+                { text: 'Провайдеры данных', link: '/ru/docs/plugins/data' },
+                { text: 'Жизненный цикл', link: '/ru/docs/plugins/lifecycle' },
               ],
             },
             {
               text: 'Руководство',
               items: [
                 { text: 'CLI справка', link: '/ru/docs/cli-reference' },
-                { text: 'Фильтрация', link: '/ru/docs/filtering' },
+                { text: 'Фильтрация', link: '/ru/docs/plugins/filter' },
               ],
             },
             {

blog/collider.md

@@ -139,7 +139,7 @@ but I want to draw your attention to how quick it is to benchmark something now!
 
 ![Shock](/blog/collider/img-04.png)
 
-Benchmarking right in your code without extra boilerplate. Like [inline tests](/docs/inline-tests.md), but for benchmarks.
+Benchmarking right in your code without extra boilerplate. Like [inline tests](/docs/plugins/inline.md), but for benchmarks.
 
 [Dragon Code](https://github.com/TheDragonCode/benchmark) once showed that benchmarks can be simple and convenient: instead of tons of boilerplate, just call a single class and pass closures for comparison.
 Testo takes this to the next level: from intent to result in just one attribute.

docs/cli-reference.md

@@ -73,7 +73,7 @@ Testo provides three types of filters that can be combined to selectively run te
 - Different type filters use AND logic: `--filter=test1 --suite=Unit` → test1 AND Unit
 - Formula: `AND(OR(filters), OR(paths), OR(suites), type)`
 
-For detailed information about filtering behavior, see [Filtering](/docs/filtering).
+For detailed information about filtering behavior, see [Filtering](plugins/filter.md).
 
 #### `--suite`
 
@@ -148,16 +148,16 @@ testo run --filter=testAuthentication --suite=Unit
 testo run --filter=UserTest --path="tests/Unit"
 ```
 
-**Filter Behavior:** See [Filtering](/docs/filtering) for details.
+**Filter Behavior:** See [Filtering](plugins/filter.md) for details.
 
 #### `--type`
 
 Filter tests by type. If specified, only tests of the matching type are run.
 
 **Possible values:**
 - `test` — regular tests (methods in classes)
-- `inline` — [inline tests](/docs/inline-tests) (tests via `#[TestInline]`)
-- `bench` — benchmarks
+- `inline` — [inline tests](plugins/inline.md) (tests via `#[TestInline]`)
+- `bench` — [benchmarks](plugins/bench.md)
 
 **Examples:**
 ```bash

docs/configuration.md

@@ -89,15 +89,15 @@ Testo is built on [plugins](plugins.md) — they define how tests are discovered
 If the `plugins` array is not specified, Testo uses the default plugin set.
 
 ::: question Which application plugins are enabled by default?
-- [FilterPlugin](filtering.md)
+- [FilterPlugin](plugins/filter.md)
 - TerminalPlugin
 - TeamcityPlugin
 :::
 
 ::: question Which Test Suite plugins are enabled by default?
-- [LifecyclePlugin](lifecycle.md)
-- [InlineTestPlugin](inline-tests.md)
-- [BenchmarkPlugin](benchmarks.md)
+- [LifecyclePlugin](plugins/lifecycle.md)
+- [InlineTestPlugin](plugins/inline.md)
+- [BenchmarkPlugin](plugins/bench.md)
 :::
 
 ### Managing Plugins

docs/getting-started.md

@@ -57,7 +57,7 @@ return new ApplicationConfig(
 );
 ```
 
-In this example we defined two test suites: `Unit` for unit tests located in `tests/Unit`, and `Sources` for [inline tests](inline-tests.md) and [benchmarks](benchmarks.md) right in the project source code, in the `src` folder.
+In this example we defined two test suites: `Unit` for unit tests located in `tests/Unit`, and `Sources` for [inline tests](plugins/inline.md) and [benchmarks](plugins/bench.md) right in the project source code, in the `src` folder.
 
 To learn more about configuration, visit the [Configuration](configuration.md) section.
 

docs/benchmarks.md docs/plugins/bench.mddocs/benchmarks.md renamed to docs/plugins/bench.md

@@ -25,7 +25,7 @@ Inline tests work well for:
 - **Private helper methods** that you want to test without changing visibility
 - **Prototyping** when you need immediate validation without switching context
 
-For larger test suites (10+ cases) or tests that need explanation, consider writing separate tests with [DataProvider](./data-providers).
+For larger test suites (10+ cases) or tests that need explanation, consider writing separate tests with [DataProvider](./plugins/data.md).
 
 ## Configuration