### Example Keymap File Structure Source: https://www.jetbrains.com/help/writerside/shortcuts.html An example XML keymap file defining layouts for Windows, macOS, and Linux, along with actions and their corresponding shortcuts for each layout. ```XML Copy Ctrl+C ⌘ C Ctrl+C Paste Ctrl+V ⌘ V Ctrl+V ``` -------------------------------- ### Example Preview Link Source: https://www.jetbrains.com/help/writerside/preview-and-test-docs.html This is an example of a preview link generated by the Writerside Preview tool. You can modify 'localhost' to your computer's IP address to share the preview. ```text http://localhost:63335/Writerside+Help+Sources/preview/preview-build-and-publish.html ``` -------------------------------- ### Example Tree File Structure Source: https://www.jetbrains.com/help/writerside/instances.html This XML snippet defines a Writerside instance profile, including its ID, name, start page, table of contents elements, and included external elements. ```xml ``` -------------------------------- ### Simple writerside.cfg Example Source: https://www.jetbrains.com/help/writerside/writerside-cfg.html Defines directories for topics and images, and two help instances. This is a basic configuration for a Writerside project. ```XML ``` -------------------------------- ### Example JSON Response for Document Creation (Success) Source: https://www.jetbrains.com/help/writerside/generate-api-reference.html This is an example of a JSON response indicating successful document creation. It typically includes a success message. ```json { "message": "Document created" } ``` -------------------------------- ### Full Kotlin Test Sample Source: https://www.jetbrains.com/help/writerside/code.html Example of a full Kotlin test file content that can be referenced. ```kotlin @Test fun testSum() { val expected = 42 assertEquals(expected, testSample.sum(40, 2)) } @Test fun testMultiply() { val expected = 42 assertEquals(expected, testSample.multiply(21, 2)) } ``` -------------------------------- ### Example XML Topic File Source: https://www.jetbrains.com/help/writerside/topics.html Illustrates the basic structure of an XML topic file in Writerside. ```xml getting-started.topic {...} ``` -------------------------------- ### Sample buildprofiles.xml Configuration Source: https://www.jetbrains.com/help/writerside/buildprofiles-xml.html A comprehensive example of a buildprofiles.xml file, demonstrating various configuration options for variables, shortcuts, footer, and build profiles. ```xml https://www.jetbrains.com/help https://www.jetbrains.com/writerside/download/ Get Writerside true strawberry writerside.svg https://www.jetbrains.com/icon-512.png keymap.xml false https://www.jetbrains.com/help/writerside/ @onwriterside https://resources.jetbrains.com/storage/products/writerside/img/meta/preview.png https://my.company.com/images/ ``` -------------------------------- ### Response Examples for Document Creation Source: https://www.jetbrains.com/help/writerside/generate-a-single-api-endpoint-reference.html These are example responses for a document creation API endpoint, illustrating a successful creation (201) and a bad request (400). ```json { "message": "Document created" } ``` ```json { "message": "Bad Request" } ``` -------------------------------- ### Serve Built Help Website Locally Source: https://www.jetbrains.com/help/writerside/local-build.html Use the http-server command to serve the unpacked help website archive from a local directory. Ensure http-server is installed first. ```bash http-server ~/my-help ``` -------------------------------- ### Basic JSON Data Diagram Example Source: https://www.jetbrains.com/help/writerside/plantuml-diagrams.html Illustrates the basic syntax for visualizing JSON data with PlantUML. The PlantUML documentation provides detailed examples for JSON diagrams. ```plantuml @startjson {...} ``` ``` -------------------------------- ### Run Sample Search Service JAR Source: https://www.jetbrains.com/help/writerside/custom-search-service.html Command to execute the provided JAR file, starting the custom search service without any pre-configured search indexes. ```shell java -jar writerside-search-1.0.jar run ``` -------------------------------- ### Example buildprofiles.xml Structure Source: https://www.jetbrains.com/help/writerside/customize-the-look.html This is a basic structure for the buildprofiles.xml file used to configure Writerside output. Create this file in your help module's cfg directory. ```xml cfg/buildprofiles.xml {...} ``` -------------------------------- ### Example Search Service Configuration Source: https://www.jetbrains.com/help/writerside/custom-search-service.html Illustrates the `searchService` and `searchServiceUrl` keys found in the `config.json` file of built artifacts, showing how the custom endpoint is appended with preview-search details. ```json searchService: "custom" searchServiceUrl: "https://my.search/endpoint/preview-search/my-docs/hi" ``` -------------------------------- ### Basic Class Diagram Example Source: https://www.jetbrains.com/help/writerside/plantuml-diagrams.html A minimal example demonstrating the structure for a PlantUML class diagram. For more complex examples, refer to the official PlantUML documentation. ```plantuml @startuml {...} ``` ``` -------------------------------- ### Install Grazie Pro Plugin Source: https://www.jetbrains.com/help/writerside/ai-powered-writing.html Install the Grazie Pro plugin to enable AI-powered writing features in Writerside. Access the IDE settings, navigate to Plugins, and search for Grazie Pro in the Marketplace. ```IDE Settings Ctrl+Alt+0S to open the IDE settings and select Plugins. Switch to the Marketplace tab, search for Grazie Pro, select the plugin, and click Install. ``` -------------------------------- ### Example JSON Response for Document Creation (Bad Request) Source: https://www.jetbrains.com/help/writerside/generate-api-reference.html This is an example of a JSON response for a bad request when creating a document. It indicates an error in the request parameters. ```json { "message": "Bad Request" } ``` -------------------------------- ### Example Markdown Topic File Source: https://www.jetbrains.com/help/writerside/topics.html Illustrates the basic structure of a Markdown topic file in Writerside. ```markdown getting-started.md {...} ``` -------------------------------- ### Environment File for Docker Builder Source: https://www.jetbrains.com/help/writerside/build-with-docker.html Example content for a builder.env file, defining environment variables for the Docker build process. ```env SOURCE_DIR=/opt/sources MODULE_INSTANCE=Writerside/hi OUTPUT_DIR=/opt/sources/output RUNNER=other PDF=PDF.xml ``` -------------------------------- ### Basic Gantt Chart Example Source: https://www.jetbrains.com/help/writerside/plantuml-diagrams.html A simple example of a PlantUML Gantt chart. For advanced features and customization options, refer to the PlantUML Gantt diagram documentation. ```plantuml @startgantt {...} ``` ``` -------------------------------- ### State Diagram Example Source: https://www.jetbrains.com/help/writerside/mermaid-diagrams.html Illustrates system behavior changes based on inputs or user actions. Use for visualizing states and transitions. ```mermaid stateDiagram-v2 [*] --> Draft RR: Ready for review NU: Need updates AC: Apply changes LGTM: All good RP: Ready to publish Draft --> RR RR --> Review Review --> NU NU --> AC AC --> Review Review --> LGTM LGTM --> RP RP --> [*] ``` -------------------------------- ### Git Graph Example Source: https://www.jetbrains.com/help/writerside/mermaid-diagrams.html Visualizes a Git branching flow. Useful for explaining branching strategies to team members or external contributors. ```mermaid gitGraph commit commit branch DOC-123-update-the-doc-A checkout DOC-123-update-the-doc-A commit id: "write the procedure" commit id: "update screenshots" checkout main merge DOC-123-update-the-doc-A commit commit ``` -------------------------------- ### Included Line from Kotlin File Source: https://www.jetbrains.com/help/writerside/code.html Example of a single line included from a Kotlin file using include-lines. ```kotlin val expected = 42 ``` -------------------------------- ### Example PDF Generation Options Source: https://www.jetbrains.com/help/writerside/export-to-pdf.html This XML file defines options for PDF generation, mirroring settings available in the Writerside PDF run configuration dialog. It should be placed in the 'cfg' directory. ```xml cfg/pdf.xml {"pdf": {"coverPage": {"title": "My Documentation", "logo": "logo.png", "description": "A sample description.", "copyright": "Copyright (c) 2024"}, "header": {"text": "Confidential"}, "footer": {"text": "Page {pageNumber} of {totalPages}"}, "tocTitle": "Table of Contents", "orientation": "portrait", "saveTo": "./pdf", "keymap": "default"}} ``` -------------------------------- ### Define Build Group Configuration Source: https://www.jetbrains.com/help/writerside/build-groups.html This XML snippet defines a build group named 'all-user-docs' that includes two documentation instances: 'User Guide' (ug) and 'Client Reference' (cr). Use this file to specify which instances should be built together. ```xml ``` -------------------------------- ### Basic Mind Map Example Source: https://www.jetbrains.com/help/writerside/plantuml-diagrams.html Demonstrates the fundamental structure for creating a PlantUML mind map. The PlantUML website offers extensive examples for mind map diagrams. ```plantuml @startmindmap {...} ``` ``` -------------------------------- ### Footer with Copyright and Social Links Source: https://www.jetbrains.com/help/writerside/customize-the-look.html Example of a footer configuration including a copyright notice and two social media links. ```XML ``` -------------------------------- ### Ordered and Unordered Lists with Nested Items Source: https://www.jetbrains.com/help/writerside/lists.html Demonstrates semantic markup for creating ordered and unordered lists with nested items. Use `type` attribute for list markers and `start` for the starting number of an ordered list. ```xml
  • First item.
  • First indented item.
  • Second indented item.
    •
  • Second item.
  • Third item.
  • Fourth item.
  • Some list item
  • Another list item
  • Yet another list item
  • Indented item
  • Indented item
    •
  • One more item
    • ``` -------------------------------- ### Example Search Query URL Source: https://www.jetbrains.com/help/writerside/custom-search-service.html Demonstrates the structure of a search request URL sent to the custom search service, including path variables and query parameters. ```url https://my.search/endpoint/preview-search/my-docs/hi?isExactSearch=false&maxHits=25&query=hello ``` -------------------------------- ### Show All Elements Source: https://www.jetbrains.com/help/writerside/structural-elements.html Display all structural elements with titles at all levels. Use this to get a comprehensive overview of your project's structure. ```HTML ``` -------------------------------- ### Sequence Diagram Example Source: https://www.jetbrains.com/help/writerside/mermaid-diagrams.html Illustrate a process flow and interactions between participants using a sequence diagram. This is helpful for understanding system processes and step-by-step logic. ```mermaid sequenceDiagram Tech writer -->> Developer: Hi, can you check that I've described everything correctly? Developer -->> Junior developer: Hi, can you, please, help our TW with the task? Developer --x Tech writer: Sure, I've asked Garold to take care of this, it will help him to understand the logic better. Junior developer -->> Developer: No problem! Developer --> Tech writer: Adding you both to a group chat ... Note right of Developer: Adding to the chat. Tech writer --> Junior developer: Hi, Garold! ``` -------------------------------- ### Sample Search Service Console Output Source: https://www.jetbrains.com/help/writerside/custom-search-service.html Expected console output when the sample search service starts without an index, indicating the TFIDF engine is created and index paths are empty. ```text Created controller with engine TFIDF algoliaIndexPath = tfidfIndexPath = ``` -------------------------------- ### Configure Search Endpoint in buildprofiles.xml Source: https://www.jetbrains.com/help/writerside/custom-search-service.html Set the search endpoint in the buildprofiles.xml file to point to the custom search service. This example assumes the service is running on the same machine. ```xml http://127.0.0.1/8080 ``` -------------------------------- ### Set Download Button Title Source: https://www.jetbrains.com/help/writerside/buildprofiles-xml.html Specifies the text for the download button in the header. Defaults to 'Get %instance%', where %instance% is the current product name. ```XML Download Now ``` -------------------------------- ### Apply Element to Specific Help Instances Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html Control the visibility of an element based on help instances using the `instance` attribute. This example shows an element that applies to all instances except 'foo' and 'bar'. ```XML

    This paragraph is for any help instance except "foo" and "bar".

    ``` -------------------------------- ### Defining Instance Groups in XML Source: https://www.jetbrains.com/help/writerside/conditional-content.html Example of an XML file structure for defining instance groups, which can be referenced later for conditional content. ```xml instance-groups.xml {...} ``` -------------------------------- ### Providing JavaScript Request Sample with Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html The tag can be used within a tag to provide custom request examples. The `lang` attribute specifies the language for highlighting, and `title` sets the tab name. ```XML const data = { id: 123, name: "John Doe", email: "john.doe@example.com" }; ``` -------------------------------- ### Configure Keymap File in buildprofiles.xml Source: https://www.jetbrains.com/help/writerside/shortcuts.html Configure the keymap file and desired layouts in buildprofiles.xml to enable the shortcut switcher in the rendered help. ```XML keymap.xml ``` -------------------------------- ### Starting Page Topic Markup Source: https://www.jetbrains.com/help/writerside/section-starting-page.html This is the basic structure for a starting page topic in Writerside. It uses the element to define the content. ```XML {...} ``` -------------------------------- ### Nullable Link Example Source: https://www.jetbrains.com/help/writerside/links-and-references.html Make a link nullable to prevent build failures if the target topic doesn't exist in a specific instance. Writerside will render only the link text in such cases. ```html link text ``` ```markdown [link text](some.topic){nullable="true"} ``` -------------------------------- ### Example TLDR Block Markup Source: https://www.jetbrains.com/help/writerside/tl-dr-blocks.html This markup demonstrates how to create a TLDR block in Writerside, with each fact wrapped in a

    tag. Use this to provide quick facts like shortcuts or configuration paths. ```html

    Shortcut: Ctrl+Space

    Configure: Settings / Preferences | Editor | Code Completion

    ``` -------------------------------- ### Substitution Rule Example Source: https://www.jetbrains.com/help/writerside/style-guides.html Use the 'substitution' block to suggest replacements for specific tokens. This example suggests replacing 'text box' with 'field'. ```yaml extends: substitution message: Consider using '%s' instead of '%s' ignorecase: true level: suggestion swap: text box: field ``` -------------------------------- ### Configure a Help Instance Source: https://www.jetbrains.com/help/writerside/writerside-cfg.html Specify the settings for a help instance, including its source tree, web path, and version. ```XML ``` -------------------------------- ### Conditional Rule Example Source: https://www.jetbrains.com/help/writerside/style-guides.html Use the 'conditional' block to enforce that the presence of one token implies the existence of another. This example requires 'bar' to be present if 'foo' is used. ```yaml extends: conditional message: "'%s' has no period" ignorecase: true first: foo second: bar ``` -------------------------------- ### Existence Rule Example Source: https://www.jetbrains.com/help/writerside/style-guides.html Use the 'existence' block to find and flag tokens you want to avoid, such as wordy phrases. This example targets 'a number of' and 'as a matter of fact'. ```yaml extends: existence message: Don't use '%s' ignorecase: true tokens: - a number of - as a matter of fact ``` -------------------------------- ### Kotlin Hello World Source: https://www.jetbrains.com/help/writerside/markup-reference.html A basic 'Hello, World!' program in Kotlin. This demonstrates the concise syntax for a main function. ```kotlin fun main() { println("Hello, World!") } ``` -------------------------------- ### Occurrence Rule Example Source: https://www.jetbrains.com/help/writerside/style-guides.html Use the 'occurrence' block to limit the number of times a token appears in a specific scope, like a sentence. This example limits commas in a sentence to a maximum of 3. ```yaml extends: occurrence message: "This sentence has more than 3 commas. Consider rephrasing it." scope: sentence ignorecase: false max: 3 token: ',' ``` -------------------------------- ### Example JSON Request Body for Document Creation Source: https://www.jetbrains.com/help/writerside/generate-api-reference.html This is an example of a JSON request body for creating a document, as might be used in an API call. It includes fields for the document's title and content. ```json { "title": "Example Document", "content": "This is some example content for the document." } ``` -------------------------------- ### Configure Version Switcher Source: https://www.jetbrains.com/help/writerside/buildprofiles-xml.html Specify the link to the `help-versions.json` file used by the help website to render the version switcher component. ```XML https://my.documentation.com/help-versions.json ``` -------------------------------- ### Sample .gitlab-ci.yml for GitLab Pages Deployment Source: https://www.jetbrains.com/help/writerside/deploy-docs-to-gitlab-pages.html This CI/CD pipeline configuration triggers on pushes to the `main` branch. It builds, tests, and publishes documentation from a starter project to GitLab Pages. ```yaml .gitlab-ci.yml {...} ``` -------------------------------- ### Define Product Versions in JSON Source: https://www.jetbrains.com/help/writerside/support-multiple-versions.html Create a JSON file that lists available product versions, their relative URLs, and indicates the current version. This file is used by the version switcher. ```json [ {"version":"1.0","url":"/help/1.0/","isCurrent":false}, {"version":"2.0","url":"/help/2.0/","isCurrent":true} ] ``` -------------------------------- ### Code Block After Refactoring Source: https://www.jetbrains.com/help/writerside/code.html Example of a code block representing the 'after' state in a comparison. ```kotlin if (true) doThis() ``` -------------------------------- ### Dockerfile for Building and Serving Documentation Website Source: https://www.jetbrains.com/help/writerside/build-with-docker.html A Dockerfile that uses the Writerside builder to create a documentation website and then serves it using an Apache HTTP server. It includes build arguments for customization. ```dockerfile FROM jetbrains/writerside-builder:2026.04.8711 as build ARG INSTANCE=Writerside/hi RUN mkdir /opt/sources WORKDIR /opt/sources ADD Writerside ./Writerside RUN export DISPLAY=:99 && \ Xvfb :99 & \ /opt/builder/bin/idea.sh helpbuilderinspect --source-dir /opt/sources --product $INSTANCE --runner other --output-dir /opt/wrs-output/ WORKDIR /opt/wrs-output RUN unzip -O UTF-8 webHelpHI2-all.zip -d /opt/wrs-output/unzipped-artifact FROM httpd:2.4 as http-server COPY --from=build /opt/wrs-output/unzipped-artifact/ /usr/local/apache2/htdocs/ ``` -------------------------------- ### Configure Footer with Copyright, Social, and Links Source: https://www.jetbrains.com/help/writerside/customize-the-look.html Use this configuration in `buildprofiles.xml` to set up a custom footer with copyright, social media links, and general links. ```XML
    2000 JetBrains s.r.o. Blog
    ``` -------------------------------- ### Code Block Before Refactoring Source: https://www.jetbrains.com/help/writerside/code.html Example of a code block representing the 'before' state in a comparison. ```kotlin if (true) { doThis() } ``` -------------------------------- ### Included Kotlin Function Source: https://www.jetbrains.com/help/writerside/code.html Example of a function included from a Kotlin file using include-symbol. ```kotlin @Test fun testMultiply() { val expected = 42 assertEquals(expected, testSample.multiply(21, 2)) } ``` -------------------------------- ### Define Product-Specific Variables Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html Use the 'instance' attribute to define variables that apply to specific product help instances. This allows for conditional content rendering. ```XML ``` -------------------------------- ### Run Docker Container with Direct Command Options Source: https://www.jetbrains.com/help/writerside/build-with-docker.html Execute the helpbuilderinspect command directly within a Docker container, providing all options as arguments. Ensure DISPLAY and Xvfb are set up within the same RUN directive. ```bash docker run --rm -v .:/opt/sources \ jetbrains/writerside-builder:2026.04.8711 \ /bin/bash -c " export DISPLAY=:99 && Xvfb :99 & /opt/builder/bin/idea.sh helpbuilderinspect \ --source-dir /opt/sources \ --product Writerside/hi \ --output-dir /opt/sources/output \ --runner other \ -pdf PDF.xml \ " ``` -------------------------------- ### Build Documentation Workflow Source: https://www.jetbrains.com/help/writerside/deploy-docs-to-github-pages.html This workflow triggers on every push to the main branch to build the documentation website. It checks out the repository, generates the website using the Writerside GitHub Action, and uploads the generated archive as a 'docs' artifact. ```yaml name: Build documentation on: push: branches: [ main ] env: INSTANCE: "Writerside/hi" DOCKER_VERSION: "2026.04.8711" jobs: build: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4 - name: Generate documentation website uses: JetBrains/writerside-github-action@v4 with: instance: ${{ env.INSTANCE }} docker_version: ${{ env.DOCKER_VERSION }} - name: Upload artifact uses: actions/upload-artifact@v4 with: name: docs path: "artifacts/*" ``` -------------------------------- ### Define Glossary Terms Source: https://www.jetbrains.com/help/writerside/tooltips.html Create a `glossary.xml` file to define terms and their descriptions. This file should be placed in the `cfg` directory. ```xml Graphical User Interface Hypertext Transfer Protocol ``` -------------------------------- ### Code Block with Collapsed Title Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html Example of setting custom text for a collapsed code block using the `collapsed-title` attribute. ```xml print('This is a collapsed code block.') ``` -------------------------------- ### Multiline Code Block Formatting Source: https://www.jetbrains.com/help/writerside/writerside-code-of-conduct.html Use triple backticks to format multiline code blocks. This is useful for longer code examples. ```text ``` multiline code blocks ``` ``` -------------------------------- ### Set Rule Severity to Error Source: https://www.jetbrains.com/help/writerside/style-guides.html Use the 'level' argument to set a rule's severity. This example marks contractions as an error. ```yaml extends: substitution message: "Use '%s' instead of '%s'." level: error ignorecase: true swap: aren't: are not ``` -------------------------------- ### Java Hello World Source: https://www.jetbrains.com/help/writerside/markup-reference.html A basic 'Hello, World!' program in Java. This is a standard entry point for Java applications. ```java class MyClass { public static void main(String[] args) { System.out.println("Hello, World!"); } } ``` -------------------------------- ### Algolia Search Environment Variables Source: https://www.jetbrains.com/help/writerside/deploy-docs-to-github-pages.html Example environment variables for configuring Algolia search integration within the GitHub Actions workflow. ```yaml ALGOLIA_APP_NAME: 'NLAGB2LZHU' ALGOLIA_INDEX_NAME: 'MY_INDEX' CONFIG_JSON_PRODUCT: 'HI' CONFIG_JSON_VERSION: '1.0' ``` -------------------------------- ### Run Docker Builder Container with Environment File Source: https://www.jetbrains.com/help/writerside/build-with-docker.html Run the Writerside Docker container using an environment file to define build variables. Mounts the current directory as sources. ```bash docker run --rm -v .:/opt/sources --env-file=builder.env \ jetbrains/writerside-builder:2026.04.8711 ``` -------------------------------- ### Link to a Topic Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html Use the `` element to create hyperlinks. This example shows linking to another topic and rendering the topic title as the link text. ```XML ``` -------------------------------- ### Footer with All Possible Elements Source: https://www.jetbrains.com/help/writerside/customize-the-look.html Demonstrates a comprehensive footer configuration including copyright, ICP, multiple social links, and various general links. ```XML
    Product 2000-2023 123456789 Slack community StackOverflow Terms and conditions Code of Conduct
    ``` -------------------------------- ### Build Docker Image Source: https://www.jetbrains.com/help/writerside/build-with-docker.html Command to build a Docker image from a Dockerfile. This image will contain the necessary tools and configurations to build the documentation website. ```bash docker build -t help-website . ``` -------------------------------- ### Create a Primary Link Group Source: https://www.jetbrains.com/help/writerside/semantic-markup-reference.html Organize important topic links using the element, typically found on section starting pages. ```XML Quick start     Hello, World! Do a barrel roll ... ``` -------------------------------- ### GET /users/{id} Source: https://www.jetbrains.com/help/writerside/generate-a-single-api-endpoint-reference.html Retrieves user information by ID. Supports custom response samples for success (200) and error (400) scenarios. ```APIDOC ## GET /users/{id} ### Description Retrieves user information by ID. This endpoint allows for custom response samples to be defined for different HTTP status codes, such as success or error responses. ### Method GET ### Endpoint /users/{id} ### Parameters #### Path Parameters - **id** (integer) - Required - The unique identifier of the user. ### Response #### Success Response (200) - **id** (integer) - The user's ID. - **name** (string) - The user's name. - **email** (string) - The user's email address. #### Response Example (200) ```json { "id": 123, "name": "John Doe", "email": "john.doe@example.com" } ``` #### Error Response (400) - **error** (string) - A message describing the error. #### Response Example (400) ```json { "error": "text" } ``` ``` -------------------------------- ### Specify Artifact Path Source: https://www.jetbrains.com/help/writerside/build-on-teamcity.html Define the artifact path for the build configuration to output a ZIP archive of the help content. ```text helproot => webhelp.zip ``` -------------------------------- ### Configure External Redirects in TOC Element Source: https://www.jetbrains.com/help/writerside/8644.html Example of a TOC element configured for external redirects, requiring specific attributes like 'hidden' and 'accepts-web-file-names'. ```xml