update config locations in our docs

Author: Mpdreamz

docs/configure/content-sources.md

@@ -35,7 +35,7 @@ Tagged
 
 This is the default. To get started, follow our [guide](/migration/guide/index.md) to set up the new docs folder structure and CI configuration.
 
-Once setup ensure the repository is added to our `assembler.yml`  under `references`. 
+Once setup ensure the repository is added to our [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml)  under `references`. 
 
 For example say you want to onboard `elastic/my-repository` into the production build:
 
@@ -59,7 +59,7 @@ Once the repository is added, its navigation still needs to be injected into to
 ### Tagged
 
 If you want to have more control over the timing of when your docs go live to production. Configure the repository
-in our `assembler.yml` to have a fixed git reference (typically a branch) deploy the `current` content source to production.
+in our [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) to have a fixed git reference (typically a branch) deploy the `current` content source to production.
 
 ```yaml
 references:
@@ -101,4 +101,4 @@ jobs:
       pull-requests: write
 ```
 
-1. Ensure version branches are built and publish their links ahead of time.
+1. Ensure version branches are built and publish their links ahead of time.

docs/configure/site/content.md

@@ -1,13 +1,13 @@
 # `assembler.yml`
 
-The global navigation is defined in the `assembler.yml` file. This file can roughly be thought of as the V3 equivalent of conf.yaml in the asciidoc build system. This file, which writers own, allows for arbitrary nesting of `docset.yml` and `toc.yml` references. This file will live in the `elastic/docs-content` repository, but will not build or have any influence over the `docs-builder` builds in that repo.
+The global navigation is defined in the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) file. This file can roughly be thought of as the V3 equivalent of conf.yaml in the asciidoc build system. This file, which writers own, allows for arbitrary nesting of `docset.yml` and `toc.yml` references. This file will live in the `elastic/docs-content` repository, but will not build or have any influence over the `docs-builder` builds in that repo.
 
-The global navigation that is defined in `assembler.yml` can be composed of three main resources:
+The global navigation that is defined in [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) can be composed of three main resources:
 1. Local TOC files: toc.yml files that live in the docs-content repository.
 2. External TOC files: A subset of a content set (represented by a toc.yml file) that is external to the docs-content repository.
 3. External content set declarations: An entire docset.yml file that is external to the docs-content repository.
 
-The `assembler.yml` file might look something like this:
+The [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) file might look something like this:
 
 ```yaml
 

docs/configure/site/index.md

@@ -22,8 +22,8 @@ TBD
 In both the AsciiDoctor- and V3-based system, there is site-wide configuration where you list all content sources, where to find those sources, and in what order they should be added to the site.
 
 In the AsciiDoctor system, this all happens in one YAML file in the `/docs` repo. In the V3 system:
-* Content configuration happens in the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/assembler.yml) file in `docs-builder`.
-* Navigation configuration happens in the [`navigation.yml`](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/navigation.yml) file in `docs-builder`.
+* Content configuration happens in the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) file in `docs-builder`.
+* Navigation configuration happens in the [`navigation.yml`](https://github.com/elastic/docs-builder/blob/main/config/navigation.yml) file in `docs-builder`.
 
 [assembler.yml](./content.md)
 

docs/contribute/_snippets/tag-processing.md

@@ -12,10 +12,9 @@ Specifically for versioned products, badges will display differently when the `a
 
   Example: {applies_to}`stack: removed 99.99`
 
-This is computed at build time (there is a docs build every 30 minutes). The documentation team tracks and maintains released versions for these products centrally in [versions.yml](https://github.com/elastic/docs-builder/blob/main/src/Elastic.Documentation.Configuration/versions.yml).
-
+This is computed at build time (there is a docs build every 30 minutes). The documentation team tracks and maintains released versions for these products centrally in [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml). 
 When multiple lifecycle statuses and versions are specified in the sources, several badges are shown.
 
 :::{note}
 Visuals and wording in the output documentation are subject to changes and optimizations.
-:::
+:::

docs/contribute/_snippets/tagged-warning.md

@@ -3,5 +3,5 @@ Some repositories use a [tagged branching strategy](/contribute/branching-strate
 
 For detailed backporting guidance, refer to the example in [Choose the docs branching strategy for a repository](/contribute/branching-strategy.md#workflow-2-tagged).
 
-To determine the published branches for a repository, find the repository in [assembler.yml](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/assembler.yml).
+To determine the published branches for a repository, find the repository in [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml).
 :::

docs/contribute/add-repo.md

@@ -45,7 +45,7 @@ Then, successfully run a docs build on the `main` branch. This is a requirement.
 
 ::::{step} Add the repository to the assembler and navigation configs
 
-Edit the [assembler.yml](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/assembler.yml) file to add the repository. Refer to [assembler.yml](../configure/site/content.md) for more information.
+Edit the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) file to add the repository. Refer to [assembler.yml](../configure/site/content.md) for more information.
 
 For example, to add the `elastic/yadda-docs` repository:
 
@@ -58,7 +58,7 @@ references:
 In this file, you can optionally specify custom branches to deploy docs from, depending on your preferred [branching strategy](branching-strategy.md). You might want to change your branching strategy so you can have more control over when content added for a specific release is published.
 :::
 
-Then, edit the [navigation.yml](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/navigation.yml) file to add the repository to the navigation.
+Then, edit the [`navigation.yml`](https://github.com/elastic/docs-builder/blob/main/config/navigation.yml) file to add the repository to the navigation.
 
 For example, to add the `elastic/yadda-docs` repository under **Reference**:
 

docs/contribute/branching-strategy.md

@@ -39,7 +39,7 @@ After it has been established that a repository should publish from a version br
 
 1. [Add new triggers to the `docs-build` CI integration](/configure/content-sources.md#ci-configuration). Merge these changes to `main` or `master` and the intended version branches.
 2. Open a PR to trigger the CI integration and confirm that the docs build.
-3. Open a PR updating the [docs assembler file](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/assembler.yml):  
+3. Open a PR updating the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml):  
    * Specify which is the `current` branch for the repository. This branch is the branch from which docs are deployed to production at [elastic.co/docs](http://elastic.co/docs).  
    * Specify which is the `next` branch for the repository. The branch defined as `next` publishes docs internally to [staging-website.elastic.co/docs](http://staging-website.elastic.co/docs)  
      * Setting this branch to the next version branch in line is a good practice to preview docs change for an upcoming version.  
@@ -60,10 +60,10 @@ When you publish from specific version branches, you need to bump the version br
 
 Add an action as part of that repo’s release process for the release manager to update this same assembler file and bump the `current` branch with each release, as appropriate. The `next` branch also needs to be bumped if it is not set to `main`. 
 
-When these releases happen, create a PR against the [assembler file](https://github.com/elastic/docs-builder/blob/main/src/tooling/docs-assembler/assembler.yml) that defines the new `current` branch, to merge on release day.
+When these releases happen, create a PR against the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) that defines the new `current` branch, to merge on release day.
 
 :::{tip}
-Regardless of the branching strategy, you also need to update the current version in [versions.yml](https://github.com/elastic/docs-builder/blob/main/src/Elastic.Documentation.Configuration/versions.yml) as part of your release process. This version number is used in documentation variables and drives our [dynamic version badge logic](/contribute/cumulative-docs.md#how-do-these-tags-behave-in-the-output).
+Regardless of the branching strategy, you also need to update the current version in [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml) as part of your release process. This version number is used in documentation variables and drives our [dynamic version badge logic](/contribute/cumulative-docs.md#how-do-these-tags-behave-in-the-output).
 :::
 
 
@@ -123,7 +123,7 @@ The changes must then be backported to their relevant version branches, and no f
 
 For example, in a situation where 9.0, 9.1, and 9.2 are already released, and the 9.3 branch has already been cut:
 
-* The branch set as `current` in the [docs assembler](https://github.com/elastic/docs-builder/blob/625e75b35841be938a8df76a62deeee811ba52d4/src/tooling/docs-assembler/assembler.yml#L70) is 9.2.  
+* The branch set as `current` in the [`assembler.yml`](https://github.com/elastic/docs-builder/blob/main/config/assembler.yml) is 9.2.  
 * The branch set as `next` (where the content development first happens), is `main`.  
 * 9.4 changes are only done on the `main` branch.  
 * 9.3 changes are done on the `main` branch and backported to the 9.3 branch.  

docs/contribute/cumulative-docs.md

@@ -31,7 +31,7 @@ This tagging system is mandatory for all of the public-facing documentation. We
 
 ## How version awareness works in Docs V3
 
-Docs V3 uses a central version config called [versions.yml](https://github.com/elastic/docs-builder/blob/main/src/Elastic.Documentation.Configuration/versions.yml), which tracks the latest released versions of our products. It also tracks the earliest version of each product documented in the Docs V3 system (the earliest available on elastic.co/docs). 
+Docs V3 uses a central version config called [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml), which tracks the latest released versions of our products. It also tracks the earliest version of each product documented in the Docs V3 system (the earliest available on elastic.co/docs). 
 
 This central version config is used in certain inline version variables, and drives our [dynamic rendering logic](#how-do-these-tags-behave-in-the-output). This logic allows us to label documentation related to unreleased versions as `planned`, continuously release documentation, and document our Serverless and {{stack}} offerings in one place.
 
@@ -142,4 +142,4 @@ We do not do date-based tagging for unversioned products.
 ## How do these tags behave in the output? 
 
 :::{include} /contribute/_snippets/tag-processing.md
-:::
+:::

docs/syntax/version-variables.md

@@ -28,7 +28,7 @@ can be printed in any kind of ways.
 
 ## Available versioning schemes.
 
-This is dictated by the [versions.yml](https://github.com/elastic/docs-builder/blob/main/src/Elastic.Documentation.Configuration/versions.yml) configuration file
+This is dictated by the [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml) configuration file
 
 * `stack`
 * `ece`

src/Elastic.Documentation.Configuration/ConfigurationFileProvider.cs

@@ -34,7 +34,7 @@ public ConfigurationFileProvider(IFileSystem fileSystem)
 
 	private IFileInfo CreateTemporaryConfigurationFile(EmbeddedResource resource)
 	{
-		var fileName = resource.GetResourceName().Split('_').Last();
+		var fileName = string.Join(".", resource.GetResourceName().Split('.')[^2..]);
 		using var stream = GetLocalOrEmbedded(resource);
 		var context = stream.ReadToEnd();
 		var fi = _fileSystem.FileInfo.New(Path.Combine(TemporaryDirectory.FullName, fileName));
@@ -44,12 +44,11 @@ private IFileInfo CreateTemporaryConfigurationFile(EmbeddedResource resource)
 
 	private StreamReader GetLocalOrEmbedded(EmbeddedResource resource)
 	{
-		var fileName = resource.GetResourceName().Split('_').Last();
+		var fileName = string.Join(".", resource.GetResourceName().Split('.')[^2..]);
 		var configPath = GetLocalPath(fileName);
 		if (!_fileSystem.File.Exists(configPath))
 			return GetEmbeddedStream(resource);
-		var stream = resource.GetStream();
-		var reader = new StreamReader(stream, leaveOpen: false);
+		var reader = _fileSystem.File.OpenText(configPath);
 		return reader;
 	}