Update _Sidebar.md
chore (wiki): refactoring files for a better reading experience.
Chore: update homepage
Updated CONFIG_SYNTAX_REFERENCE.fr (markdown)
Updated Configuration_Syntax_Reference (markdown)
Chore: Renaming files (tests) to improve the reading experience on the wiki
Add the plugin guide pages PLUGIN_GUIDE / PLUGIN_GUIDE.fr come from the main repository (biface/dcli#89), where they had not changed since v0.4.0: - New "Builtin plugins" section: HelpPlugin, VersionPlugin, ExitPlugin, and the feature-gated SysInfoPlugin, EnvPlugin and ConfigPlugin, with their `implementation` names and feature flags. - Registration examples pass the loaded configuration to plugins through `with_config()`: `CliBuilder::build()` does not, and `system_help` then prints "Help is not available". - The `help` command example declares the `command` argument that `system_help` reads. - The chrom-rs native handler takes `&ParsedArgs` (it used `&HashMap<String, String>`, which has not compiled since v0.6.0) and `DiagnosticsPlugin` is `pub`, as its use from another module requires. Checked by building and running it against the crate. - WASM: arguments cross the boundary as scalars only; repeatable options are left out. - Links point to the wiki pages and docs.rs; DD-021 reads DA-021, and DT-025 is cited for the builtin plugins.
Add configuration reference and REPL directives pages Home and _Sidebar give a bilingual entry point. The configuration syntax reference comes from CONFIG_SYNTAX_REFERENCE.md / .fr.md in the main repository (biface/dcli#79); its REPL directives section becomes a page of its own, REPL_DIRECTIVES / REPL_DIRECTIVES.fr. Content fixes made during the move: - `type:` replaced by `arg_type:` or `option_type:`: the loader has no `type` key and rejected every example (`missing field option_type`). Each complete YAML/JSON example now loads and passes validation. - Fields with a serde default are no longer marked as required: `global_options`, a command's `aliases`, `required`, `arguments` and `options`, an argument's `validation`, an option's `required`. - A command's `required` is described as what it does: a handler must be registered for the command, or building the application fails. - The two bare decision mentions (DD-024, DD-026) become issue links.
Initial Home page