diff --git a/documentation/1.0/content/concepts/_index.md b/documentation/1.0/content/concepts/_index.md
deleted file mode 100644
index 75f6edb51..000000000
--- a/documentation/1.0/content/concepts/_index.md
+++ /dev/null
@@ -1,154 +0,0 @@
-+++
-title = "About the WKT UI Application"
-date = 2019-02-22T15:27:38-05:00
-weight = 1
-pre = ""
-+++
-
-
-
-### Contents
-
-- [WKT Project File](#wkt-project-file)
-- [Settings Outside the WKT Project File](#settings-outside-the-wkt-project-file)
- - [Environment Variables](#environment-variables)
- - [User Preferences](#user-preferences)
- - [Proxy Configuration](#proxy-configuration)
- - [Logging Configuration](#logging-configuration)
- - [WebLogic Kubernetes Toolkit UI Introduction Configuration](#weblogic-kubernetes-toolkit-ui-introduction-configuration)
- - [External Applications](#external-applications)
- - [Bundled WKT Applications](#bundled-wkt-applications)
-
-
-
-Before giving you the whirlwind tour of the WKT UI application, it is important to know that the application is a native,
-desktop application. It uses native operating system features, such as:
-
-- Native menus - Some of the application's functionality is available _only_ by using the menus.
-- Registering file extensions - The application installer registers the `.wktproj` extension and associates itself
- with that extension. For example, this lets you double-click on the file in the native file browser and
- have the application start and open the selected project.
-- Recent files integration - As you work with `.wktproj` files, the application adds those files to the OS-maintained
- list of recently used files. This causes these files to show up in OS-specific locations to provide shortcuts for
- opening the file with the application. For example, on MacOS, right-clicking on the application icon in the dock will
- display the recently used `.wktproj` files and selecting one will open an application window and load the contents
- of the `.wktproj` file.
-
-### WKT Project File
-What is a `.wktproj` file? Simply put, it is the application's equivalent of an Integrated Development Environment
-(IDE) project file. It stores:
-
-- Metadata about the UI project.
-- Pointers to WDT model-related files used by the project.
-- Form field data that you enter into the application.
-
-There are two ways to create a new project:
-- Explicitly - Use `File` > `New Project` and select the file location and name.
-- Implicitly - Use the application to start working. After you trigger an action that needs a project file, you are
- prompted to select the file location and name.
-
-_Note that the file extension for project files must be `.wktproj`. Otherwise, the application will not recognize the
-file as a project and will not allow it to be opened as a project file._
-
-The WKT UI application uses a one project per window paradigm and most everything you do in the window is
-affected by the project data, either stored directly in the project file or in the WDT model-related files referenced
-by the project. However, there are a few exceptions that are covered in [Settings Outside the WKT Project File](#settings-outside-the-wkt-project-file).
-
-### Settings Outside the WKT Project File
-
-Multiple factors influence the behavior of the WKT UI application in a particular environment. Other than the WKT Project file,
-those include:
-
-- [Environment Variables](#environment-variables) - The application uses the environment it inherits when it is started.
-- [User Preferences](#user-preferences) - The application's user preferences file stores shared, user-level settings that
- transcend project boundaries.
-- [External Applications](#external-applications) - The application or its components depend on an application being available and properly configured.
-- [Bundled WKT Applications](#bundled-wkt-applications) - The application bundles its own copies of WebLogic Deploy Tooling and WebLogic Image Tool.
-
-#### Environment Variables
-Some of the application's behavior is influenced by environment variables it inherits when it is started. Environment
-variables affect the behavior of the WKT UI application when computing default values for application form fields. Some
-examples are:
-
-- `PATH` - Used to locate executables like `docker`, `helm`, and `kubectl`.
-- `JAVA_HOME` - Used as one way to find the directory where the Java Development Kit (JDK) is installed.
-- `ORACLE_HOME` and `MW_HOME` - Used to find the Oracle Fusion Middleware installation directory.
-
-{{% notice note %}}
-On Windows and Linux platforms, this tends to be the user's environment that they have configured to be used when
-they log in. On MacOS, native applications do not inherit the user's login environment. Instead, the application
-inherits the environment configured by the `launchd` daemon process. If you are running on MacOS, then you should keep this in mind
-when the application doesn't behave as you expect.
-{{% /notice %}}
-
-#### User Preferences
-
-The `Preferences` menu lets you configure settings that affect the behavior of the WKT UI application for the user
-across all instances of the application on the machine. These user-visible settings include the following categories:
-
-- [Proxy Configuration](#proxy-configuration)
-- [Logging Configuration](#logging-configuration)
-- WebLogic Kubernetes Toolkit UI [Introduction Configuration](#weblogic-kubernetes-toolkit-ui-introduction-configuration)
-
-Settings are also used to store internally used values that impact the appearance of the application. For example, the
-Window size is stored so that the application will open the window with your last known window size. The list of
-such appearance-related settings will likely grow over time.
-
-##### Proxy Configuration
-
-If the WKT UI application is to be run from an environment where a proxy server is required to access the Internet, then you
-must configure the proxy server settings to allow Internet access. Currently, the UI depends on access to
-`github.com` to access release information and download new releases of the WKT tools and the UI itself. This connectivity
-is used in various places to determine default values for input data (for example, the default image tag to use for installing the
-WebLogic Kubernetes Operator) and providing updated features for the WKT tools bundled with the application, as
-well as updating the WKT UI application itself when a new release becomes available. Depending on the project configuration,
-the application may also require access to other sites, such as Docker Hub and other container registries, Helm chart
-download sites, and cloud-provider sites for authenticating to and accessing remote Kubernetes clusters.
-
-To configure the proxy environment, use the `Preferences` menu to add or update the
-following fields, as needed:
-
-- `HTTPS Proxy URL` - The full URL to the proxy server (for example, http://my-proxy-server.mycompany.com:80).
-- `Bypass Proxy Hosts` - The comma-separated list of DNS or IP patterns that should not go through the proxy.
- For example, a value of `.us.mycompany.com,.emea.mycompany.com,.apac.mycompany.com` will skip the proxy for any
- DNS name that ends in one of the three domain names.
-
-##### Logging Configuration
-
-Using this section, you can configure the logging output level and control the log file directory. The defaults are:
-
-- `File Transport Log Level` - The logging level below which log messages will be discarded. For example, `Debug` messages
- will be discarded if the level is set to `Info`. The default value is `Info`.
-- `Log File Directory` - The directory to which log files are written. The default is the user's temporary directory, as
- defined by the operating system.
-
-##### WebLogic Kubernetes Toolkit UI Introduction Configuration
-
-This setting lets you turn on or off the in-application introductory information being displayed at startup. `Show Introduction` is always
-accessible from the `Help` menu.
-
-#### External Applications
-
-The WKT UI application depends on several external applications for its functionality. As such, it is important to install and
-configure these external applications properly on the local machine on which the application is running.
-
-- `docker` (or `podman`) - Used to create new images and inspect the contents of
- custom base images. The WebLogic Image Tool depends on `docker` (or `podman`) for this functionality. `docker`
- (or `podman`) is also used to log in to and interact with image registries.
-- `kubectl` - Used to get, create, and update configuration objects in your Kubernetes cluster.
- It is critical that the `kubectl` configuration file is properly set up to allow `kubectl` to authenticate to the cluster.
-- `helm` - Used to install the WebLogic Kubernetes Operator and ingress controllers.
-- `openssl` - Used to generate X.509 TLS certificates, should you ask the application to
- generate one for your ingress route(s), only if you ask the application to generate it for you.
-
-#### Bundled WKT Applications
-
-[WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) (WDT) and [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/) (WIT) are bundled with the WKT UI application. These tools are:
-
-- WDT - Used to support discovering a model from an existing domain, prepare the model for a
- particular Kubernetes target type, and is used by the WebLogic Image Tool when creating the domain inside the image.
-- WIT - Used to create a new image for your WebLogic Server domain. It is also used to inspect any
- custom base image that you might specify be used for creating the new image.
-
-Use `Help` > `Check For Updates` periodically to make sure you are using the latest versions of these
-bundled tools.
diff --git a/documentation/1.0/content/developer/_index.md b/documentation/1.0/content/developer/_index.md
deleted file mode 100644
index 110ca6987..000000000
--- a/documentation/1.0/content/developer/_index.md
+++ /dev/null
@@ -1,48 +0,0 @@
-+++
-title = "Developer Guide"
-date = 2019-02-22T15:27:38-05:00
-weight = 4
-pre = ""
-+++
-
-The WebLogic Kubernetes Toolkit UI is a desktop application designed to help WebLogic users move their applications to run in a Kubernetes environment.
-
-### Setting up your development environment
-1. Download and install the latest LTS version of `node.js` from [https://nodejs.org/en/download/](https://nodejs.org/en/download/).
-2. If you rely on a proxy server to reach the Internet, set these five environment variables to configure the proxy correctly:
- ```
- ELECTRON_GET_USE_PROXY=true
- GLOBAL_AGENT_HTTPS_PROXY=
- WKTUI_DEV_PROXY=
- HTTPS_PROXY=
- NO_PROXY=
- ```
-3. Open a command line and run the following command to update the version of `npm` to the latest:
- ```bash
- sudo npm install --global npm
- ```
-4. Set up your global git configuration by running the following commands:
- ```bash
- git config --global user.name ""
- git config --global user.email ""
- git config --global core.ignoreCase false
- ```
- **This last command is critical if you are developing on either Windows or MacOS. Yes, the MacOS file system
- is, by default, case-insensitive!**
-
-5. Clone the git repository on GitHub at [https://github.com/oracle/weblogic-toolkit-ui](https://github.com/oracle/weblogic-toolkit-ui).
-6. Open a command line in the `weblogic-toolkit-ui` directory and run `npm install` to download and install the JavaScript dependencies required by the project.
-7. Open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm run install-tools`.
-8. Open a command line in the `weblogic-toolkit-ui/webui` directory and run `npm start`.
-9. After the server from the previous step is fully running, open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm start`.
-
-### Building a Windows or MacOS installer
-0. Set up your development environment and verify that the application is working properly from it.
-1. Open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm run build`.
-2. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.
-
-### Building a Linux installer
-0. Set up your development environment and verify that the application is working properly from it.
-1. Open a command line in the `weblogic-toolkit-ui/webui` directory and run `npm run build:release`.
-2. From the command line in the `weblogic-toolkit-ui/scripts` directory, run `./devBuildLinuxInstallers.sh`.
-3. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.
diff --git a/documentation/1.0/content/navigate/image.md b/documentation/1.0/content/navigate/image.md
deleted file mode 100644
index d2a2f9fe0..000000000
--- a/documentation/1.0/content/navigate/image.md
+++ /dev/null
@@ -1,205 +0,0 @@
----
-title: "Image"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 3
----
-
-### Contents
-- [Image](#image)
-- [Design View](#design-view)
- - [Target Image Name and Registry Credentials](#target-image-name-and-registr-credentials)
- - [Base Image to Use](#base-image-to-use)
- - [Installers for Building the Image](#installers-for-building-the-image)
- - [Patch Oracle Home](#patch-oracle-home)
- - [WebLogic Deploy Tooling Configuration](#weblogic-deploy-tooling-configuration)
- - [Image Build Configuration](#image-build-configuration)
-- [Code View](#code-view)
-- [Create Image](#create-image)
-- [Push Image](#push-image)
-
-### Image
-The `Image` section helps you build container images for deploying WebLogic-based applications
-in a Kubernetes environment using the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/).
-
-### Design View
-The `Design View` helps you specify the necessary data needed to run the WebLogic Image Tool to build an image for
-running the WebLogic domain with all resources configured and applications deployed. This page is divided into several
-primary panes and a few advanced panes that include:
-
-- [Target Image Name and Registry Credentials](#target-image-name-and-registry-credentials)
-- [Base Image to Use](#base-image-to-use)
-- [Installers for Building the Image](#installers-for-building-the-image)
-- [Patch Oracle Home](#patch-oracle-home)
-- [WebLogic Deploy Tooling Configuration](#weblogic-deploy-tooling-configuration)
-- [Image Build Configuration](#image-build-configuration)
-
-#### Target Image Name and Registry Credentials
-The most important field in this pane is the `Image Tag` field. This is the name to give to the newly created image,
-which must conform to the [image naming standards](https://docs.docker.com/engine/reference/commandline/tag/#extended-description).
-Because most Kubernetes environments will need to pull the image from a container image registry (for example, Docker Hub),
-the newly-created image typically will need to be pushed to the appropriate container image registry. Most registries
-will require authentication as a user with the necessary permissions to push images. As described in the image naming
-standards, the `Image Tag` field typically must include the DNS name of the container image registry prior to the first
-slash (`/`) character. Images not containing a container image registry DNS name are assumed to be using Docker Hub.
-
-After the `Image Tag` field is populated, the application detects the presence of any prepended DNS name and displays the
-value in the `Image Registry Address` field. This field is read-only so the only way to change the DNS name is to change
-the value of the `Image Tag` field. The `Image Registry Push Username`
-and `Image Registry Push Password` fields let you provide the user credentials needed to log in to the container
-image registry prior to pushing the newly-created image. If explicit authentication is not required, then disable the
-`Specify Image Push Credentials` option. If `Specify Image Push Credentials` is enabled, then any attempts to push the
-image will fail unless the `Image Registry Push Username` and `Image Registry Push Password` fields are specified.
-
-#### Base Image to Use
-By default, the WebLogic Image Tool uses an Oracle Linux base image when building the new image. To specify a different
-base image, enable `Use Custom Base Image` and provide the base image's tag in the `Custom Base Image to Use`
-field. Any container image registry address found in the base image tag will be displayed in the read-only
-`Base Image Registry Address` field. If pulling the base image requires authentication, then enable
-`Custom Base Image Pull Requires Login` and provide the necessary credentials in the
-`Custom Base Image Pull Username` and `Custom Base Image Pull Password` fields.
-
-When using a custom base image, the application requires the image to be inspected using the WebLogic Image Tool's
-[Inspect Image](https://oracle.github.io/weblogic-image-tool/userguide/tools/inspect-image/) command. To invoke this inspection, click
-`Inspect Custom Base Image`. This inspection tells the application if Java or the
-Oracle Fusion Middleware software is already installed in the image. If it finds either of these software packages
-installed, then fields in the `Installers for Building the Image` pane will disappear because they are unneeded.
-
-In the current release, the `Patch Oracle Home` pane will disappear if the base image contains an Oracle Fusion
-Middleware installation. The rationale being that the act of patching a base image installation will bloat the size of
-the image. As such, it is better to either create the base image with the latest patches already installed or allow
-the WebLogic Image Tool's multistage build to install and patch the Oracle Fusion Middleware installation while
-minimizing the resulting image size.
-
-#### Installers for Building the Image
-This pane will contain form fields for up to three installers (depending on the base image being used); they are:
-
-- JDK Installer
-- Oracle Fusion Middleware Installer
-- WebLogic Deploy Tooling Installer
-
-When specifying the `JDK Installer`, it is important to remember that this installer will be used to install the JDK inside
-the Linux x64 image being created. Therefore, the `Linux JDK Installer to Use` field should always point to the
-Linux x64 compressed archive installer (for example, `jdk-8u291-linux-x64.tar.gz`). While the value of the `JDK Version` field
-is just a tag associated with the installer used to specify which version of the JDK installer that the WebLogic Image
-Tool should use, the best practice is to set the value to the real version number (for example, `8u291` or `1.8.0_291`).
-
-The `Oracle Fusion Middleware Installer to Use` field must point to an installer that includes a modern version of
-WebLogic Server (12.2.1.3 or later). Use the `Oracle Fusion Middleware Installer Type` field to tell the WebLogic Image
-Tool which installer you are providing. It is important to make sure the type and installer match because installers of
-different types require different fields to be specified during installation. As with the `JDK Version` field mentioned
-previously, the `Oracle Fusion Middleware Version` field is just a tag to associate with the installer but the best
-practice is to set the value to the actual Oracle Fusion Middleware version number (for example, `12.2.1.4.0`).
-
-By default, `Download and Use Latest WebLogic Deploy Tooling Installer` is enabled so that the application will
-automatically download and use the latest, generally-available release in the WebLogic Deploy Tooling
-[GitHub repository](https://github.com/oracle/weblogic-deploy-tooling/releases/). To specify a different installer,
-disable `Download and Use Latest WebLogic Deploy Tooling Installer` and fill out the
-`WebLogic Deploy Tooling Installer to Use` and `WebLogic Deploy Tooling Version` fields appropriately. As with the
-other installers' version number fields, the best practice it to use the actual WebLogic Deploy Tooling version number
-(for example, `1.9.17`). Note that new WDT versions often contain bug fixes or enhancements required to work with the
-latest capabilities, many of which are exposed by this application. As such, using the latest version is strongly
-recommended.
-
-#### Patch Oracle Home
-Oracle strongly recommends patching all Oracle Fusion Middleware installations with the latest Patch Set Updates (PSUs)
-and other recommended patches to ensure that the latest security fixes are applied. This pane configures the WebLogic
-Image Tool to apply the specified patches to the Oracle Home during the image creation process. There are two mechanisms
-for specifying that patches should be applied:
-
-- Radio buttons to specify what patch bundles should be applied.
-- The list of patch numbers to apply.
-
-The patch bundle radio buttons provide three choices:
-
-- `None` - Applies no bundle patches.
-- `Apply Latest PSU Only` - Applies the latest PSU patch but no
- other recommended patches.
-- `Apply All Recommended Patches` - Applies all recommended patches, which always includes
- the latest PSU, in addition to other important fixes.
-
-Use the `Individual Patches to Apply` field to specify individual patch numbers to apply. These patches will be applied
-after any patch bundles specified.
-
-The WKT UI application requires that valid Oracle Support credentials be specified using the `Oracle Support Username` and
-`Oracle Support Password` fields. This allows the WebLogic Image Tool to automatically discover the latest PSU and
-recommended patches and download any patches specified as part of the image creation process.
-
-As a last resort, if no valid Oracle Support credentials are available, the patching process can be skipped by disabling
-the `Apply Patches` option. _To make sure your WebLogic-based applications are
-as secure as possible, this really should be a last resort._
-
-#### WebLogic Deploy Tooling Configuration
-This `Advanced` pane applies only to images using either the "Model in Image" or "Domain in Image" [domain locations]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}).
-
-The `Domain Type` field tells WebLogic Deploy Tooling what type of domain to create. Use the `Domain Home Directory`
-to change the location of the WebLogic domain directory inside the container. The `Model Home Directory` field
-specifies the directory where the WDT model files are stored in the image. Typically, there is no need to override
-these directory locations because the application defaults follow the recommended best practices.
-
-#### Image Build Configuration
-This `Advanced` pane supports altering the default behavior of the WebLogic Image Tool, as well as extending the image
-build process to include custom build steps that might be required by particular applications or environments.
-
-The `JDK/FMW Installation Owner` and `JDK/FMW Installation Group` fields specify the Linux user and group that should
-own the JDK and Oracle Fusion Middleware installation directories. The default values are generally fine for most
-environments. Any images intended to run in an OpenShift environment, where the configured Security Context Constraints
-cause the containers to run as a random user in the `root` group, will require changing the `JDK/FMW Installation Group`
-field from its default value to `root`. For more information, see
-[Managing security context constraints](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html)
-in the OpenShift documentation.
-
-If the base image is expected to change without the image tag changing, then enable `Always Pull Base Image`. With
-this option enabled, the image build process will always pull a new version of the base image to ensure that the latest
-version is being used. Otherwise, the base image will be pulled only if it doesn't already exist in the local machine's
-image cache.
-
-The `Image Build Network Name` field allows an image build to run when the build process needs access to another
-container, such as a database that might be running in a container that is needed while WDT is creating the domain.
-Because the current release doesn't support creating JRF domains during the image build process (that is, for the
-"Domain in Image" domain location), it is unlikely that this field will be needed. However, it is surfaced
-for completeness.
-
-To add custom steps to the image build process, enable `Extend Image Build` and provide the Dockerfile
-containing the additional commands in the `Additional Build Commands File` field. If the specified Dockerfile needs
-additional files to be present in the build context directory, then provide the list of those required files in the
-`Additional Build Files` field.
-
-### Code View
-The `Image` page's `Code View` displays a shell script that you can use as a starting point for automating the image
-creation process.
-
-If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
-that the application is providing a working sample script simply to show how the process might be automated. Before
-using the script, review the script and make any changes necessary for your environment. One typical change that
-would be considered a best practice would be to change the script to accept either command-line arguments or externally
-set environment variables to specify any credentials required by the script to eliminate hard-coding the credentials in
-the script itself. This change is left as an exercise for you because different environments typically will have
-existing standards for securely handling such credentials.
-
-### Create Image
-`Create Image` invokes the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/) to
-create a new container image for running a WebLogic domain in a Kubernetes environment. You can access this action using
-the `Create Image` button on the `Image` page or the `Go` menu.
-
-At a high level, `Create Image` performs the following steps:
-
-1. Validates the input values necessary for running the action based on your selections.
-2. Saves the WKT Project, if needed.
-3. Adds the installers to the WIT cache on the local machine using the WebLogic Image Tool
- [Cache](https://oracle.github.io/weblogic-image-tool/userguide/tools/cache/) command.
-4. Builds the image on the local machine using the WebLogic Image Tool
- [Create](https://oracle.github.io/weblogic-image-tool/userguide/tools/create-image/) command.
-
-### Push Image
-`Push Image` uses the specified Image Builder program to upload (that is, push) the newly-built image
-to the image registry specified by its image tag. You can access it by using the `Push Image` button on the `Image`
-page or `Go` > `Push Image to Registry`.
-
-At a high level, `Push Image` performs the following steps:
-
-1. Validates the input values necessary for running the action based on your selections. This includes making
- sure that an image with the specified `Image Tag` value exists in the local machine's image cache.
-2. Saves the WKT Project, if needed.
-3. Logs in to the container image registry, if specified.
-4. Pushes the image to the container image registry.
diff --git a/documentation/1.0/content/navigate/kubernetes/k8s-client-config.md b/documentation/1.0/content/navigate/kubernetes/k8s-client-config.md
deleted file mode 100644
index 29f1b0e1d..000000000
--- a/documentation/1.0/content/navigate/kubernetes/k8s-client-config.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "Client Configuration"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 1
-description: "Client Configuration helps you get the necessary connectivity to your Kubernetes cluster."
----
-
-
-
-### Contents
-
-- [Client Configuration](#client-configuration)
- - [Authentication with Managed Kubernetes Clusters](#authentication-with-managed-kubernetes-clusters)
- - [Verify Connectivity](#verify-connectivity)
-
-### Client Configuration
-`Client Configuration` helps you get the necessary connectivity to your Kubernetes
-cluster. Use the `Kubernetes Cluster Type` field to select the target Kubernetes cluster type to show instructions for
-configuring `kubectl` to successfully connect to the cluster.
-
-- The `Kubectl Executable to Use` field tells the WKT UI application where to find the correct version of `kubectl` to use.
-- By using the `Kubernetes Client Config File(s)` field, you can specify a different Kubernetes client configuration
-file instead of, or in addition to, the default `.kube/config` file from your home directory.
-- For environments where the client is configured to connect to multiple clusters, use the `Kubernetes Config Context to Use` field to
-specify the configuration file's context associated with the cluster to which you want to connect.
-- The `Helm Executable to Use` field tells the application where to find Helm, which is used to install the WebLogic
-Kubernetes Operator and ingress controllers. For more information
-about Helm, see the [Helm](https://helm.sh/) documentation.
-
-#### Authentication with Managed Kubernetes Clusters
-Most cloud vendors require the use of their command-line tooling to authenticate `kubectl` connections to their managed
-Kubernetes clusters. For example, after `kubectl` is configured to connect to a Kubernetes cluster managed by the
-Oracle Kubernetes Engine (OKE), the Kubernetes client configuration file will have a section that looks similar to the
-one shown here.
-
-```
-users:
-- name: user-abcdefghi8d
- user:
- exec:
- apiVersion: client.authentication.k8s.io/v1beta1
- command: oci
- args:
- - ce
- - cluster
- - generate-token
- - --cluster-id
- - ocid1.cluster.oc1.phx.aaaaaaaaahdirjdmcjfpogfkdhjsdhshssk2abcdefghijk2d
- - --region
- - us-phoenix-1
- env: []
-```
-
-This configuration causes each `kubectl` invocation that references this user definition to execute the `oci` command
-(the Oracle Cloud command-line tool) to get the credentials necessary to successfully authenticate to the cluster.
-If the `oci` executable is not in a directory in the `PATH` environment variable when the `kubectl` command is executed,
-then an error similar to the one shown here will occur.
-
-```
-Failed to verify Kubernetes client connectivity: Unable to verify Kubernetes client connectivity:
-Command failed: /Users/rpatrick/bin/kubectl version --short
-Unable to connect to the server: getting credentials: exec: executable oci not found
-
-It looks like you are trying to use a client-go credential plugin that is not installed.
-
-To learn more about this feature, consult the documentation available at:
-https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins.
-```
-
-When running the application on Windows or Linux, add the appropriate directory to the `PATH` environment variable and make sure to
-run the application with that environment. On MacOS, things are a bit more complicated.
-
-When running the WKT UI application on MacOS, the application inherits the environment of a daemon process called `launchd` instead
-of your environment. By default, the `launchd` environment contains only a few core directories on the `PATH`
-(that is, `/usr/bin`, `/bin`, `/usr/sbin`, and `/sbin`). This will cause `kubectl` invocations requiring access to one of
-the cloud providers' command-line tooling to fail if the tool is not found in one of those locations. While it is
-possible for an administrative user to change the environment that `launchd` uses to address this issue, the application
-provides the `Extra Kubernetes Client Path Directories` field to explicitly add the directory where the cloud providers'
-command-line tooling is installed, to the `PATH` that the application uses to invoke `kubectl`. Note that this field
-is only visible when running the application on MacOS.
-
-#### Verify Connectivity
-To verify the application configuration for connecting to the specified Kubernetes cluster,
-use the `Verify Connectivity` button on the `Client Configuration` page or
-`Go` > `Verify Kubernetes Client Connection`.
diff --git a/documentation/1.0/content/navigate/kubernetes/k8s-ingress-controller.md b/documentation/1.0/content/navigate/kubernetes/k8s-ingress-controller.md
deleted file mode 100644
index a389941d1..000000000
--- a/documentation/1.0/content/navigate/kubernetes/k8s-ingress-controller.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: "Ingress Controller"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 4
-description: "Install and configure an ingress controller."
----
-
-### Contents
-- [Ingress Controller](#ingress-controller)
-- [Design View](#design-view)
- - [Ingress Controller Configuration](#ingress-controller-configuration)
- - [TLS Secret for Ingress Routes](#tls-secret-for-ingress-routes)
- - [Ingress Routes Configuration](#ingress-routes-configuration)
-- [Code View](#code-view)
-- [Install Ingress Controller](#install-ingress-controller)
-- [Update Ingress Routes](#update-ingress-routes)
-
-### Ingress Controller
-This section supports two distinct functions related to an ingress controller. First, it supports installing an ingress
-controller to a Kubernetes cluster. Second, it supports adding the necessary routes to an ingress controller to make
-a deployed WebLogic domain's endpoints accessible.
-
-### Design View
-`Design View` helps you specify the data needed to install an ingress controller, if desired, and
-specify the data needed to expose one or more endpoints for a deployed WebLogic domain. This page contains three panes:
-
-- [Ingress Controller Configuration](#ingress-controller-configuration)
-- [TLS Secret for Ingress Routes](#tls-secret-for-ingress-routes)
-- [Ingress Routes Configuration](#ingress-routes-configuration)
-
-#### Ingress Controller Configuration
-The most important field in this pane is the `Ingress Provider` field. This fields tells the WKT UI application with which of the
-supported ingress controllers it will need to work. The current release supports two ingress
-controllers:
-
-- NGINX
-- Traefik
-
-To install the ingress controller, enable `Install Ingress Controller`.
-- To set the release name used by the Helm install process, use the `Helm Release Name to Use` field.
-- Set the Kubernetes namespace to which the ingress controller should be installed with the `Ingress Controller Namespace` field.
-
-The container image for the Traefik ingress controller resides in Docker Hub. Due to changes made
-to Docker Hub, anonymous pull requests are throttled. This can result in pull requests being denied when the Kubernetes
-cluster attempts to pull the image and start the container.
-- To work around this limitation, enable the `Use Docker Hub Secret` field to provide login credentials for Docker Hub.
-- The `Docker Registry Secret Name` field specifies the name of the Kubernetes pull secret to use when pulling the image.
-To create this secret, enable `Create Docker Hub Secret` and fill in the pull secret data in the `Docker Hub Username`, `Docker Hub Password`,
-and `Docker Hub Email Address` fields.
-
-#### TLS Secret for Ingress Routes
-Use this pane to configure the Transport Layer Security (TLS) secret containing the certificate and private key data that will be used by the
-ingress controller when establishing HTTPS connections from clients to the ingress controller. The TLS connection will be
-terminated at the ingress controller, so traffic between the ingress controller and services/pods will not be encrypted.
-In the current release, only a single TLS certificate is supported for the routes being defined.
-
-- To use TLS-enabled routes, enable `Use Ingress TLS Secret` and provide the secret name using the
-`Ingress TLS Secret Name` field.
-- To have the application create this secret, enable `Create Ingress TLS Secret`.
-- If you already have a certificate file and its corresponding private key file, then use the `TLS Certificate File`
-and `TLS Private Key File` fields to provide them.
-- To create these files automatically, enable `Generate a TLS Certificate and Private Key`.
- - Provide the path to the OpenSSL executable using the
-`OpenSSL Executable to Use` field.
- - Use the `Subject to Use for the Generated TLS Certificate` field to specify the data
-to put into the subject of the certificate.
- - For example, if your ingress route will use the virtual host name
-`www.myapp.com`, you might specify the subject contents as `/CN=www.myapp.com`.
- - The subject data will support multiple
-key/value pairs using a comma-separated syntax, like `/key1=value1,/key2=value2,/key3=value3`.
-
-#### Ingress Routes Configuration
-Use the table in this section to define the ingress routes to be added by the application. _Note that this table does
-not currently display existing routes already defined._ Any routes defined in or removed from the table will happen in
-the WKT Project object. When applying or updating the routes, only the fields currently in the table will be considered.
-If the routes do not exist, then they will be added. If one or more of the routes already exists, then the application will warn
-you to confirm whether you want to update the existing route or routes before performing the operation.
-
-To add a new route, click the plus (`+`) button in the table header. To edit a route, use the edit button on the corresponding
-route row. To remove a route, use the delete icon on the corresponding route row.
-
-When editing a route:
-- Use the `Name` field to set the route name.
-- Use the `Virtual Host` and `Path Expression` fields to define the matching rules that determine which requests match this route.
-- All requests in the defined rules are routed to the service specified by the `Target Service` field that resides in the namespace specified by the read-only
-`Target Service Namespace` field and the port specified by the `Target Port` field.
-- To enable TLS between the client
-and the ingress controller, enable the `Enable TLS` option. Remember, enabling TLS means that the TLS secret
-information must be provided in the `TLS Secret for Ingress Routes` pane. Different ingress controllers support advanced ingress route configuration using ingress controller-specific annotations.
-- Use the `Ingress Route Annotations` table to
-add annotations to the ingress route, as needed.
-
-### Code View
-The `Code View` displays shell scripts for installing an ingress controller and for updating ingress routes. It also
-displays the YAML definitions of the routes to be added, if applicable.
-
-If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
-that the application is providing a working sample script simply to show how the process might be automated. Before
-using the script, review the script and make any changes necessary for your environment. One typical change that
-would be considered a best practice would be to change the script to accept either command-line arguments or externally
-set environment variables to specify any credentials required by the script to eliminate hard-coding the credentials in
-the script itself. This change is left as an exercise for you because different environments typically will have
-existing standards for securely handling such credentials.
-
-### Install Ingress Controller
-`Install Ingress Controller` creates any namespace and secret specified and runs the ingress controller's Helm
-chart to install the ingress controller. You can access it by using the `Install Ingress Controller` button on the
-`Ingress Controller` page or `Go` > `Install Ingress Controller`.
-
-### Update Ingress Routes
-`Update Ingress Routes` creates the TLS secret, if needed, and adds or updates the specified ingress routes. You can access it
-by using the `Update Ingress Routes` button on the `Ingress Controller` page or
-`Go` > `Update Ingress Routes to Domain`.
diff --git a/documentation/1.0/content/navigate/kubernetes/k8s-weblogic-domain.md b/documentation/1.0/content/navigate/kubernetes/k8s-weblogic-domain.md
deleted file mode 100644
index eb680c0e5..000000000
--- a/documentation/1.0/content/navigate/kubernetes/k8s-weblogic-domain.md
+++ /dev/null
@@ -1,224 +0,0 @@
----
-title: "WebLogic Domain"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 3
-description: "Create and deploy the Kubernetes custom resource for the WebLogic domain."
----
-
-### Contents
-- [WebLogic Domain](#weblogic-domain)
-- [Design View](#design-view)
- - [Image to Use for the Domain](#image-to-use-for-the-domain)
- - [Clusters](#clusters)
- - [Model Variables Overrides](#model-variables-overrides)
- - [Secrets](#secrets)
- - [Runtime Encryption Secret](#runtime-encryption-secret)
- - [WebLogic Kubernetes Operator Introspection Configuration](#weblogic-kubernetes-operator-introspection-configuration)
- - [Domain-Wide Server Settings](#domain-wide-server-settings)
-- [Code View](#code-view)
-- [Prepare Model](#prepare-model)
-- [Deploy Domain](#deploy-domain)
-- [Get Domain Status](#get-domain-status)
-
-### WebLogic Domain
-The `WebLogic Domain` section provides support for creating and deploying the Kubernetes custom resource for the WebLogic domain as
-defined by the WebLogic Kubernetes Operator. For more information, see
-[Domain Resource](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/domain-resource/)
-in the WebLogic Kubernetes Operator documentation.
-
-### Design View
-The `Design View` helps you specify the necessary data needed to generate the Domain resource definition and deploy
-that resource into a Kubernetes cluster.
-
-The `Domain UID` field defines the name of the Kubernetes Domain custom resource object. This name must be unique
-within the Kubernetes namespace where it will be created, which is controlled by the `Kubernetes Namespace` field.
-
-The default value of the `Domain UID` field is based on the WebLogic domain's name, as defined by the WDT model:
-
-- When using either "Model in Image" or "Domain in Image" [domain location]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}),
-the `Domain Home Path` field is read-only and its value is set using the `Domain Home Directory` field under `Advanced`.
-- When using "Domain in PV", this field must be set to the fully
-qualified path to the domain home directory in the persistent volume. For example, if the persistent volume mount
-path is set to `/shared` and the domain home is located in `/domains/mydomain` in the persistent volume, then the
-`Domain Home Path` field must be set to `/shared/domains/mydomain`.
-
-Set the Kubernetes secret name where the WebLogic domain credentials will be stored using the
-`WebLogic Credentials Secret Name` field. Set the value of the WebLogic Server administration credentials using the
-`WebLogic Admin Username` and `WebLogic Admin Password` fields. Remember that these fields must be set appropriately
-for the selected domain location:
-
-- For "Model in Image", these fields are used to set the WebLogic Server credentials used to create the domain, and
- by the operator at runtime to perform actions on the domain (for example, start a server).
-- For "Domain in Image", the domain was created using the WebLogic Image Tool using the credentials specified in the
- model. These values must match the ones used during the image creation process.
-- For "Domain in PV", the domain was created outside the application so the values provided in these fields must match
- the ones used when the domain was created.
-
-When using "Domain in PV", three additional fields associated with the persistent volume will be shown:
-
-- `Persistent Volume Name` - The name of the persistent volume to use in the Domain resource file.
-- `Persistent Volume Claim Name` - The persistent volume claim to associate with the persistent volume.
-- `Persistent Volume Mount Path` - The path to the persistent volume within the container(s).
-- `Enable Log Home` - Enables the ability to separate the logs directory from the domain directory on the persistent
- volume.
-- `Log Home Path` - The path to use for the log home when `Enable Log Home` is enabled.
-
-The following sections describe the other panes that support configuring the generated Domain resource; they are:
-
-- [Image to Use for the Domain](#image-to-use-for-the-domain)
-- [Clusters](#clusters)
-- [Model Variables Overrides](#model-variables-overrides)
-- [Secrets](#secrets)
-- [Runtime Encryption Secret](#runtime-encryption-secret)
-- [WebLogic Kubernetes Operator Introspection Configuration](#weblogic-kubernetes-operator-introspection-configuration)
-- [Domain-Wide Server Settings](#domain-wide-server-settings)
-
-#### Image to Use for the Domain
-This pane focuses on the container image to use to run the WebLogic Server domain in a container.
-- When using either "Model in Image" or "Domain in Image" [domain location]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}), the `Image Tag` field is read-only; its value is set using the
-`Image Tag` field in the `Image` section.
-- In the case of "Domain in PV", the `Image Tag` field is not read-only and _is_
-the place to specify the image to use to run the WebLogic domain's containers.
-- The read-only `Image Registry Address` field is populated by parsing the value of the `Image Tag` field
-to extract any container image registry address. If the tag has no image registry address, then it is assumed to reside on Docker Hub.
-
-Use the `Image Pull Policy` field to specify when Kubernetes should pull the image from the specified image registry.
-The choices are:
-
-- `If Not Present` (default) - Only pull the image if it is not already present on the Kubernetes node.
-- `Always` - Pull the image every time the image is needed to start a container.
-- `Never` - Never pull the image; this will result in an error if the image is not already present on the Kubernetes node.
-
-If pulling the image from the specified image registry does not require authentication,
-then `Specify Image Pull Credentials` should be disabled. When enabled, use the `Use Existing Image Pull Secret` field to tell the application
-whether to use an existing image pull secret or create a new one. Specify the image pull secret name in the
-`Image Pull Secret Name` field. When creating a new secret, specify the secret data using the
-`Image Registry Pull Username`, `Image Registry Pull Email Address`, and `Image Registry Pull Password` fields.
-
-#### Clusters
-The Clusters pane lists the names of each cluster in the model and lets you adjust the WebLogic Server
-startup configuration and Kubernetes resource requests and limits. It is currently populated when `Prepare Model` is run,
-which means that projects using "Domain in PV" will not have access to adjust the configuration at the cluster level.
-"Domain in PV" projects can still use the `Domain-Wide Server Settings` pane under `Advanced`.
-
-To view or edit the settings for a cluster, select the edit icon at the right end of the cluster's row in the
-table. This opens a dialog that shows all the cluster-related fields and their values. The read-only
-`Cluster Name` field shows the name of the cluster, as specified in the underlying model.
-
-Use the `Replicas` field to adjust the number of managed servers that the WebLogic Kubernetes Operator should start when the domain is deployed.
-The default value for the `Replicas` field is set based on the maximum number of servers specified by the model:
-- In the case of a static cluster, it will be the number of servers that are configured to be part of the cluster.
-- When using a dynamic cluster, the value is set based on the maximum number of servers that the dynamic cluster allows.
-- This default value also serves as the upper limit for the `Replicas` field. In other words, you may only reduce the number of
-replicas. It is not possible to increase the replica count above the maximum limit defined by the model.
-
-Use the `Minimum Heap Size` and `Maximum Heap Size` fields to control the amount of Java heap space available for each
-server in the cluster. Specify any additional Java command-line options with the `Additional Java Options`
-field.
-
-`Disable debug logging to standard out` disables WebLogic Server debug log messages from being
-written to standard out. In WebLogic Server 12.2.1.3.0, there is an issue that impacts the Oracle JDBC driver
-processing FAN (Fast Application Notification) events from an Oracle Database. To work around this issue, enable
-`Disable Oracle JDBC Support for FAN Events`.
-
-`Use pseudo-random number generator` controls whether
-WebLogic Server uses the pseudo-random number generator (that is, `/dev/urandom`) or the regular random number generator
-(that is, `/dev/random`). Because the latter is impacted by the available entropy, it can negatively impact performance when
-running WebLogic Server on a virtual machine or in a container. Because the servers being configured by this application
-will always be running in a container, the default is set to use the pseudo-random number generator.
-
-The Kubernetes resource requests and limits values help the Kubernetes scheduler determine which node to use to start
-a container (to ensure there are sufficient resources available for the container to run). The following fields allow
-these values to be specified:
-
-- `Kubernetes CPU Request` - The requested amount of CPU for each managed server's container.
-- `Kubernetes CPU Limit` - The maximum amount of CPU each managed server's container is allowed to use.
-- `Kubernetes Memory Request` - The requested amount of memory for each managed server's container.
-- `Kubernetes Memory Limit` - The maximum amount of memory each managed server's container is allowed to use.
-
-For more information about these fields and setting their values, see the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-memory).
-
-#### Model Variables Overrides
-Use this pane to override values of model variables when using "Model in Image" to customize the model data already set
-in the image. For example, the image may contain a variable whose value refers to a JDBC URL to connect to a database.
-Because the image may be used across development, test, and production environments, overriding the JDBC URL to point to
-the correct database for the environment helps make the same image usable across all three environments. All override
-values are added to a Kubernetes ConfigMap that is passed to the WebLogic Kubernetes Operator so that it creates the
-underlying WebLogic Server domain with the correct values for the environment.
-
-If the model has one or more variables, then the `Kubernetes Config Map Name` field is visible and allows the name of the
-Kubernetes ConfigMap name to be controlled. The table will be populated with the model variables, as defined by the
-model variables file. Because the model variables file is typically already set in the image by the time you
-reach this page, both the `Model Variable Name` and the `Model Variable File Value` entries are read-only. Enter an
-`Model Variable Override Value` for any variable whose `Model Variable File Value` should be overridden. Note that the
-ConfigMap will only be created if one or more variables have an override value specified.
-
-#### Secrets
-When using "Model in Image", use this pane to set the value of any secrets referenced in the model (other than the WebLogic administrator credentials
-secret). The secrets that appear in the table are pulled from the model file directly;
-as such, the `Secret Name` field is read-only. Set the appropriate `Username` and `Password` field values for each
-secret in the table. These values are required and will be used to create or update the secret with the specified
-values.
-
-#### Runtime Encryption Secret
-When using "Model in Image", the WebLogic Kubernetes Operator requires a runtime encryption secret it uses to encrypt
-sensitive WebLogic Server domain data stored in Kubernetes. For more information, see
-[Required runtime encryption secret](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/model-in-image/usage/#required-runtime-encryption-secret)
-in the WebLogic Kubernetes Operator documentation.
-
-Use the `Runtime Encryption Secret Name` field to control the name of the secret, if needed. Typically, the default
-name is sufficient. The `Runtime Encryption Secret Value` field's default value is generated but may be changed, if
-desired.
-
-#### WebLogic Kubernetes Operator Introspection Configuration
-This pane controls the WebLogic Kubernetes Operator introspection job configuration. Use the
-`Introspection Job Active Deadline Seconds` field to control how long the operator waits for the introspection job to
-complete. The application sets the default to 900 seconds (15 minutes); this overrides the underlying default of 120
-seconds (2 minutes) built into the operator. As such, clearing the value of this field will cause the effective value
-to be set to 120 seconds.
-
-#### Domain-Wide Server Settings
-This pane lets you adjust the WebLogic Server startup configuration and Kubernetes resource requests and
-limits default values for every WebLogic Server container in the WebLogic Server domain. Any fields set here will be
-applied only if they are not overridden elsewhere. For example, setting the `Minimum Heap Size` will set
-WebLogic Server's minimum heap size to the specified value only if the cluster to which the server belongs does not
-override the minimum heap size. For typical domains with an Administration Server and one or more clusters, the best practice is
-to use this section to configure the Administration Server and use the `Clusters` pane to configure each cluster explicitly.
-
-The fields in this pane have similar meaning to the equivalent fields previously described in
-[Clusters](#clusters); refer to that section for more information.
-
-### Code View
-The `Code View` displays a shell script for deploying the domain and creating its dependent resources as well as
-the YAML definition for the Kubernetes custom resource (that is, the Domain resource) and the Model Variables Overrides
-ConfigMap, if applicable.
-
-If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
-that the application is providing a working sample script simply to show how the process might be automated. Before
-using the script, review the script and make any changes necessary for your environment. One typical change that
-would be considered a best practice would be to change the script to accept either command-line arguments or externally
-set environment variables to specify any credentials required by the script to eliminate hard-coding the credentials in
-the script itself. This change is left as an exercise for you because different environments typically will have
-existing standards for securely handling such credentials.
-
-### Prepare Model
-`Prepare Model` is the same as was previously described in the [`Model`]({{< relref "/navigate/model#prepare-model" >}}) section. It is only
-surfaced here because the `Clusters` pane of the `Design View` is populated only when `Prepare Model` is run.
-
-### Deploy Domain
-`Deploy Domain` creates the Domain custom resource object and any of its dependent objects (for example,
-namespace, secrets, ConfigMap) in Kubernetes. You can access it by using the `Deploy Domain` button on the
-`WebLogic Domain` page or `Go` > `Deploy WebLogic Domain to Kubernetes`. As previously
-mentioned, this action also updates the operator configuration, if needed, and reruns the operator Helm chart to ensure
-that the new namespace is manageable by the WebLogic Kubernetes Operator configured for this project.
-
-`Deploy Domain` completes as soon as the objects are created and the operator Helm chart execution completes. At some point
-after the action completes, the operator will detect a new (or updated) version of the Domain custom resource object and
-start a new introspection job to create the domain and start or restart the WebLogic Server containers. `Get Domain Status`
-provides the current status of the last `Deploy Domain` action.
-
-### Get Domain Status
-To view the current status of the last domain deployment, use the `Get Domain Status` button or the
-`Go` > `Get WebLogic Domain Status`. This action retrieves and displays the domain deployment
-status, as provided by the WebLogic Kubernetes Operator.
diff --git a/documentation/1.0/content/navigate/kubernetes/k8s-wko.md b/documentation/1.0/content/navigate/kubernetes/k8s-wko.md
deleted file mode 100644
index 71150a75a..000000000
--- a/documentation/1.0/content/navigate/kubernetes/k8s-wko.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: "WebLogic Kubernetes Operator"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 2
-description: "Install the WebLogic Kubernetes Operator in the target Kubernetes cluster."
----
-
-
-
-### Contents
-- [WebLogic Kubernetes Operator](#weblogic-kubernetes-operator)
-- [Design View](#design-view)
- - [WebLogic Kubernetes Operator Image](#weblogic-kubernetes-operator-image)
- - [Image Pull Secret](#image-pull-secret)
- - [Kubernetes Namespace Selection Strategy](#kubernetes-namespace-selection-strategy)
- - [WebLogic Kubernetes Operator Role Bindings](#weblogic-kubernetes-operator-role-bindings)
- - [External REST API Access](#external-rest-api-access)
- - [Third Party Integrations](#third-party-integrations)
- - [Java Logging](#java-logging)
-- [Code View](#code-view)
-- [Install Operator](#install-operator)
-
-### WebLogic Kubernetes Operator
-This section provides support for installing the WebLogic Kubernetes Operator (the "operator") in the target Kubernetes cluster.
-For detailed information about the operator, see the
-[WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/) documentation.
-
-### Design View
-The `Design View` helps you specify the necessary data needed to install the WebLogic Kubernetes Operator to manage
-WebLogic domains in one or more Kubernetes namespaces. To install the operator using the default settings, simply
-provide values for the following three fields:
-
-- `Kubernetes Namespace` - The Kubernetes namespace to which to install the operator.
-- `Kubernetes Service Account` - The Kubernetes service account for the operator to use when making Kubernetes API
- requests.
-- `Helm Release Name to Use for Operator Installation` - The Helm release name to use to identify this installation.
-
-{{% notice note %}}
-The WKT UI application overrides a few default values in the operator Helm Chart. Read the details of the parameters descriptions in
-[Kubernetes Namespace Selection Strategy](#kubernetes-namespace-selection-strategy). These panes and their fields are made visible by expanding the
-`Advanced` portion of the page.
-{{% /notice %}}
-
-#### WebLogic Kubernetes Operator Image
-By default, the operator's `Image Tag to Use` field is set to the image tag corresponding to the latest operator
-release version on the GitHub Container Registry. The `Image Pull Policy` field configures the operator deployment in
-Kubernetes to tell it when to pull the image from the specified registry:
-
-- `If Not Present` (default) - Only pull the image if it is not already present on the Kubernetes node.
-- `Always` - Pull the image every time the image is needed to start a container.
-- `Never` - Never pull the image; this will result in an error if the image is not already present on the Kubernetes node.
-
-Because the GitHub Container Registry does not require image pull authentication to pull the official WebLogic Kubernetes
-Operator image, `Image Pull Requires Authentication` is disabled by default. If a custom
-operator image is being used from a container image registry that requires pull authentication, then enable the option
-and complete the appropriate fields described in the [Image Pull Secret](#image-pull-secret)
-pane that follows.
-
-#### Image Pull Secret
-This pane is hidden unless the `Image Pull Requires Authentication` from the WebLogic Kubernetes Operator Image pane
-is enabled. To allow Kubernetes to pull the custom operator image requiring pull authentication, use the
-`Kubernetes Image Pull Secret Name` field to provide the name of the Kubernetes secret to use for the credentials. To
-have the application create this secret, disable `Use Existing Secret` and provide the values for the following
-fields:
-
-- `Image Pull Secret Email Address` - The email address of the user.
-- `Image Pull Secret Username` - The user name to use when authenticating to the container image registry.
-- `Image Pull Secret Password` - The user's password to use when authenticating to the container image registry.
-
-The read-only `Image Registry Address` field is parsed from the `Image Tag to Use` field. If the
-`Image Registry Address` field is empty, then the application will assume that Docker Hub is the target container image
-registry to use when creating the pull secret.
-
-#### Kubernetes Namespace Selection Strategy
-The operator needs to know which WebLogic domains in the Kubernetes cluster that it will manage. It does this at the
-Kubernetes namespace level, so any WebLogic domain in a Kubernetes namespace the operator is configured to manage, will
-be managed by the operator instance being installed. Use the `Kubernetes Namespace Selection Strategy` field to choose
-the desired namespace selection strategy from one of the supported values:
-
-- `Label Selector` (default) - Any Kubernetes namespace with a specified label will be managed by this operator.
-- `List` - Any Kubernetes namespace in the provided list will be managed by this operator.
-- `Regular Expression` - Any Kubernetes namespace whose name matches the provided regular expression will be managed
- by this operator.
-- `Dedicated` - Only the Kubernetes namespace where the operator is installed will be managed by this operator.
-
-_**Note** that the operator Helm chart default is `List` but the application overrides this to specify `Label Selector` as
-the default value._
-
-Each namespace selection strategy takes different input values; the form fields will change based on the strategy
-selected:
-
-- When using the `Label Selector` strategy, the `Kubernetes Namespace Label Selector` field will appear with a default
-value that aligns with the Helm chart default value.
-- The `Regular Expression` strategy uses the required
-`Kubernetes Namespaces Regular Expression` field to specify the regular expression to use for matching the Kubernetes
-namespaces that the operator should manage.
-- Selecting the `List` strategy will cause the `Kubernetes Namespaces to Manage` field to appear with a list containing
-the `default` namespace; this aligns with the default value in the Helm chart.
- - Removing the `default` namespace is fine and will result in an empty list.
- - Note that when deploying the domain with an operator using the `List` strategy, the
-application will automatically add the new domain's Kubernetes namespace to the list specified list, if needed. As
-such, specifying an empty list will not prevent your WebLogic domain from being managed by the operator.
-- `Dedicated` is self-defining so no additional fields are necessary.
-
-#### WebLogic Kubernetes Operator Role Bindings
-When installing the operator, the operator Helm chart default is to create a Kubernetes Role and a Kubernetes RoleBinding
-in each Kubernetes namespace being managed by the operator. By enabling `Enable Cluster Role Binding`, the
-operator installation will create a Kubernetes ClusterRole and ClusterRoleBinding that the operator will use for all managed
-namespaces. This ClusterRole and ClusterRoleBinding will be shared across all operator installations in the Kubernetes
-cluster (assuming that those installations also enable cluster role binding).
-
-Using the default namespace-specific roles and role bindings, the administrator follows the Principle of Least
-Privilege to guarantee that the operator cannot perform any actions on other, non-managed namespaces. The implication
-of this configuration is that because the operator service account does not have permission to create roles and role
-bindings, any new namespace added for the operator to manage does not have the necessary role and role binding needed
-for the operator to manage the namespace. Rerunning the operator Helm chart with the operator configured to manage the
-new namespaces will cause the Helm chart to create the necessary Role and RoleBinding objects in each namespace,
-as needed.
-
-If the operator is using the ClusterRole and ClusterRoleBinding, then the new namespaces will be automatically picked up by
-the operator when using either the `Label Selector` or `Regular Expression` namespace selection strategy without any
-need to rerun the operator Helm chart.
-
-As previously mentioned, the WKT UI application automatically reruns the operator Helm chart when deploying new WebLogic
-domains to ensure that the new domain's namespace is being managed by the operator.
-
-#### External REST API Access
-By default, the operator's REST API is not exposed outside the Kubernetes cluster. To enable the REST API to be
-exposed, enable `Expose REST API Externally`, set the desired HTTPS port using the
-`External REST API HTTPS Port` field, and name of the Kubernetes TLS secret to use in the
-`External REST API Identity Secret Name` field. For more information, see the WebLogic Kubernetes Operator
-[Rest API](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-operators/the-rest-api/) documentation.
-
-#### Third Party Integrations
-To enable integration with the Elasticsearch, Logstash, and Kibana (ELK) stack, enable `ELK Integration Enabled` and provide values for the
-following fields.
-
-- `Logstash Image Tag to Use` - The container image of `logstash` to use.
-- `Elasticsearch Host Name` - The DNS name of IP address of the Elasticsearch server.
-- `Elasticsearch Port` - The port number for the Elasticsearch server.
-
-For more information, see [Elastic Stack integration](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-operators/#optional-elastic-stack-elasticsearch-logstash-and-kibana-integration)
-in the WebLogic Kubernetes Operator documentation.
-
-#### Java Logging
-This pane lets you override the operator's Java logging configuration, which can be useful when debugging issues
-with the operator. Use the `Logging Level` field to customize the minimum log level written to the log file. The
-`Log File Size Limit` field sets the maximum size of a single operator log file while the `Log File Count` limits the
-maximum number of retained log files. For more information, see
-[Operator Helm configuration values](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-operators/using-helm/#operator-helm-configuration-values)
-in the WebLogic Kubernetes Operator documentation.
-
-### Code View
-The `WebLogic Operator` page's `Code View` displays a shell script that you can use as a starting point for automating the
-operator installation process.
-
-If it is not already selected, then use the `Script Language` drop-down menu to choose the desired scripting language. Note
-that the application is providing a working sample script to show how the process might be automated. Before
-using the script, review the script and make any changes necessary for your environment. One typical change that
-would be considered a best practice would be to change the script to accept either command-line arguments or externally
-set environment variables to specify any credentials required by the script to eliminate hard-coding the credentials in
-the script itself. This change is left as an exercise for you because different environments typically will have
-existing standards for securely handling such credentials.
-
-### Install Operator
-The `Install Operator` action installs the WebLogic Kubernetes Operator in the target Kubernetes cluster.
-You can access it by using the `Install Operator` button on the
-`WebLogic Operator` page or `Go` > `Install WebLogic Kubernetes Operator`.
-
-At a high level, `Install Operator` performs the following steps:
-
-1. Validates the input values necessary for running the action based on your selections.
-2. Saves the WKT Project, if needed.
-3. Creates the Kubernetes namespace for installing the operator, if needed.
-4. Creates the Kubernetes service account for the operator to use, if needed.
-5. Creates the operator image pull secret, if needed.
-6. Adds the latest operator Helm chart to the local Helm repository.
-7. Runs Helm to install the operator using the specified configuration.
diff --git a/documentation/1.0/content/navigate/model.md b/documentation/1.0/content/navigate/model.md
deleted file mode 100644
index 7681790c2..000000000
--- a/documentation/1.0/content/navigate/model.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
-title: "Model"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 2
----
-
-
-### Contents
-- [Model](#model)
-- [Design View](#design-view)
-- [Code View](#code-view)
- - [Model Editor](#model-editor)
- - [Variables Editor](#variables-editor)
- - [Archive Editor](#archive-editor)
-- [Prepare Model](#prepare-model)
-
-
-### Model
-The `Model` section helps you work with WebLogic Deploy Tooling models for a WebLogic domain. A WebLogic
-Deploy Tooling model for a domain can include the following file types:
-
-- Model file - A declarative definition of the domain configuration.
-- Variable file - A property file that maps names to values. These names can be referenced from the model file to
- allow a model to be used across environments by applying the variable file for a particular environment to the model.
-- Archive file - A ZIP file containing application binaries and other files and directories needed to run the domain.
-
-For more information about WebLogic Deploy Tooling models, see [Metadata Model](https://oracle.github.io/weblogic-deploy-tooling/concepts/model/)
-and [Archive File](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/) in the WebLogic Deploy
-Tooling documentation.
-
-### Design View
-In the current release, the `Design View` is empty. Our intention is to eventually provide a WebLogic
-console-like set of pages that will make it easier to create or edit a model using an interface more familiar to
-WebLogic administrators and developers.
-
-### Code View
-Using an IDE-like layout, the `Code View` provides editor panes for editing the model, variables, and archive files,
-each of which support creating and editing the domain's WDT files. When working with an editor, there are several things
-to keep in mind:
-
-- When working with a WKT Project that has no associated WDT file for storing the data, entering data into an editor
- will cause a new WDT file with the editor's current content to be created and associated with the project.
-- Changes made in the editor are buffered in memory until the WKT Project is saved.
-- Adding, deleting, or modifying data in the variable or archive editors will _not_ change the model references. You
- will need to make sure that the model references are accurate and up to date.
-
-While it is possible to use the WKT UI application to create the files from scratch, the `File > Add Model`
-menu supports adding existing files or using the WebLogic Deploy Tooling's
-[Discover Domain Tool](https://oracle.github.io/weblogic-deploy-tooling/userguide/tools/discover/)
-to create a model of an existing domain.
-
-{{% notice note %}}
-While WebLogic Deploy Tooling supports using multiple model, variables, or archive files to describe a single
-domain, the current release of WKT supports _only_ one WDT model file, one WDT variables file, and one WDT archive file for
-describing the domain.
-{{% /notice %}}
-
-#### Model Editor
-In `Code View`, the model editor is just to the right of the navigation pane. This editor displays the current
-model file associated with the WKT Project file. Typing model content into the editor will
-result in a new model file being added to the project the next time the project is saved.
-
-The current release has the following limitations:
-
-- Model files must be in YAML format.
-- Model files must exist directly on the file system and not inside an archive, such as in a ZIP file; any model file inside an archive is ignored by the application.
-
-#### Variables Editor
-The WDT variables editor is in the upper right pane of the `Code View` page. It supports editing any existing
-name-value pairs, as well as adding or removing name-value pairs.
-
-To reference a variable from the model, you must set the value of the desired model file to a variable reference.
-For example, the model snippet shown here references a variable named `httpPort`.
-
-```yaml
-topology:
- Name: tododomain
- ProductionModeEnabled: true
- Cluster:
- mycluster:
- DynamicServers:
- ServerNamePrefix: Server_
- DynamicClusterSize: 10
- ServerTemplate: mysrvtemplate
- ServerTemplate:
- mysrvtemplate:
- ListenPort: '@@PROP:httpPort@@'
- Cluster: mycluster
-
-```
-
-When working with this model file, WebLogic Deploy Tooling expects the `httpPort` variable to be defined in the model's
-variables file, as shown here:
-
-```properties
-httpPort = 7001
-```
-
-#### Archive Editor
-The WDT archive editor is in the lower right pane of the `Code View` page. It supports adding content to and
-removing content from the archive file. While updating content in the archive is not supported directly by the archive
-editor, the archive editor safely supports multiple operations on the same entry. As such, combining a
-`remove` operation followed by the corresponding `add` operation will effectively replace an entry.
-
-To add content to the archive file, use the plus (`+`) button in the archive editor
-title bar and follow the prompts to choose the type of content to add and select the corresponding file or directory.
-For example, to add a WAR file called `todo.war` to the archive, do the following:
-
-1. On the archive editor title bar, click `+`.
-2. In the resulting dialog, choose `Application File` from the list and click `OK`.
-3. In the resulting file chooser dialog, select the `todo.war` file and click `Select`.
-
-This will result in the file structure `wlsdeploy/applications/todo.war` being added to the archive editor pane.
-At this point, the application has not created or modified the archive file; it is simply storing
-the data it needs about the archive path to the added entry and the file path where the content is found. Saving the
-WKT Project will update the archive to reflect the buffered operations performed in the editor.
-
-{{% notice note %}}
-Don't forget to add the application to the model and set its `SourcePath` attribute to the path in the archive where it can be found,
-as shown in the following model file snippet.
-{{% /notice %}}
-
-```yaml
-appDeployments:
- Application:
- todo:
- SourcePath: wlsdeploy/applications/todo.war
- ModuleType: war
- Target: mycluster
-```
-
-To remove content from the archive file, select the content to remove in the archive editor pane and click the minus (`-`)
-button in the archive editor title bar. _Don't forget to remove any reference to this content from the model file._
-
-#### Prepare Model
-`Prepare Model` invokes the WDT [Prepare Model Tool](https://oracle.github.io/weblogic-deploy-tooling/userguide/tools/prepare/)
-to modify the model to work in a Kubernetes cluster with WebLogic Kubernetes Operator or Verrazzano installed. This
-action is available by using the `Prepare Model` button on the `Model` and `Kubernetes WebLogic Domain` pages and by selecting
-`Go` > `Prepare Model for Kubernetes`. It is also possible to run `Prepare Model` during the `Create
-Image` action, though typically it is best to run `Prepare Model` explicitly, prior to moving to the `Image` section.
-
-
-`Prepare Model` does the following:
-
-1. Removes model sections and fields that are not compatible with the target environment.
-2. Replaces endpoint values with model tokens that reference variables.
-3. Replaces credential values with model tokens that reference either a field in a Kubernetes secret or a variable.
-4. Provides default values for fields displayed in the application's variable, variable overrides, and secret editors.
-5. Extracts topology information to the application that it uses to generate the resource file used to deploy the domain.
-
-For more information, see the WDT [model tokens](https://oracle.github.io/weblogic-deploy-tooling/concepts/model/#model-tokens)
-documentation.
-
-In replacing credential values, `Prepare Model` must handle the replacement differently for the "Domain in Image" and
-"Model in Image" [domain locations]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}):
-
-- With "Domain in Image", the WebLogic Image Tool creates the domain while creating the image. As such, it has no
-knowledge of Kubernetes so the token replacement uses variable tokens so that domain creation has access to the actual
-credential values. You must ensure that all variables have valid values prior to running `Create Image`.
-
-- For "Model in Image", the domain is created at runtime by the WebLogic Kubernetes Operator running in a Kubernetes
-cluster. As such, token replacement uses secret tokens for all credential fields. You must to be sure to provide
-values for all secret reference fields using the `WebLogic Domain` section's `Secrets` pane so that the required secrets
-get populated correctly during domain deployment. For more information, see [WebLogic Domain]({{< relref "/navigate/kubernetes/k8s-weblogic-domain.md" >}}).
-
-{{% notice note %}}
-The application tries to preserve any values from the model and variable files that `Prepare Model` replaces
-with secret tokens. The current release is limited by the behavior of the underlying WDT Prepare Model Tool in that
-all passwords are not retained and must be re-entered in the appropriate location.
-{{% /notice %}}
diff --git a/documentation/1.0/content/navigate/project-settings.md b/documentation/1.0/content/navigate/project-settings.md
deleted file mode 100644
index fce46bddc..000000000
--- a/documentation/1.0/content/navigate/project-settings.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: "Project Settings"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 1
----
-
-The first stop for every new project is `Project Settings`. In this section, you make decisions and provide
-input for the project on:
-
-- [Credential Storage](#choosing-a-credential-storage-scheme)
-- [Domain Location](#choosing-a-domain-location)
-- [Kubernetes Environment Target Type](#choosing-a-kubernetes-environment-target-type)
-- [JDK and WebLogic Server Installation Directories](#choosing-the-java-and-oracle-installation-directories)
-- [Image Build Tool Type and Executable Location](#choosing-the-image-build-tool)
-
-#### Choosing a Credential Storage Scheme
-The WKT UI application can securely store credentials for your project or not store them at all. The three choices
-are:
-
-- Use the Native OS Credential Store
-- Store Encrypted Credentials in the WKT Project File
-- Not Store Credentials
-
-If you choose `Store in Native OS Credential Store`, then you will be using the Windows Credential Manager, the MacOS Keychain,
-or the Linux `libsecret` library's credential store. These credential stores offer a well-known, secure mechanism for
-storing credentials that most users already understand. The only downside to this scheme is that the credentials are
-stored only on the local machine. Anyone trying to share their project with others users will have to have the other users
-re-enter the credentials so that they get saved to their local machine's credential store.
-
-{{% notice note %}}
-The WKT UI application can require storing a dozen or more credentials, depending on your WebLogic Server
-domain configuration. Upon first access by the WKT UI to load credentials from the credential store, the OS will prompt
-whether you want to allow the application access to each credential, prompting you once for each credential. This
-can get annoying, but on some platforms (for example, MacOS), you have the option of telling the OS to always allow access to
-the credential by the WKT UI application.
-{{% /notice %}}
-
-The other choice to store credentials, `Store Encrypted in Project File`, uses a passphrase-based encryption built into the application that allows
-the credentials to be stored inline in the WKT Project file. The algorithms and techniques used follow the current
-industry standards and recommendations; however, because this project is open source, you can look at the details,
-if you are interested. The only downside to this approach is that, because the passphrase itself is
-never stored, you must share the passphrase with any other users that should be able to use the WKT Project file.
-
-A creative person might realize that they can use the passphrase-based encryption to move credentials normally stored
-in the native OS credential store to another machine. The steps to accomplish this would be:
-
-1. Open the project using the native OS credential store on the machine where the credentials are stored.
-2. Change the credential storage option to passphrase-based encryption and enter a passphrase.
-3. Save the project file.
-4. Open the project file on a different machine, supplying the passphrase entered in step 2.
-5. Change the credential storage option to native OS credential store.
-6. Save the project file.
-
-The final choice, `Not Stored`, is to not store the credentials at all. While this is a viable option, it also means that whenever you
-need to run any of the actions that require credentials, you will need to re-enter the value of every credential in the
-project.
-
-#### Choosing a Domain Location
-When getting started with a new WKT Project, one of the first things to consider is where you want the domain to reside.
-Domains can reside in a container, in an image, or in a persistent volume. Your choice will expose and hide different
-fields across most sections of the UI. The following describe the implications of the three locations:
-
-- `Created in the container from the model in the image` - The newest and most popular location for a domain is in the container. This is known as "Model in Image" but also
-referred to as a "From Model" in the underlying WKT tooling. In this case, the set of model-related files are added to
-the image. When the WebLogic Kubernetes Operator domain object is deployed, its inspector process runs and creates the
-WebLogic Server domain inside a running container on-the-fly. While this process adds a small amount of overhead at
-startup, it also makes it easier to maintain the image. For example, you can have a common WebLogic Server image that
-is updated periodically to pick up the latest Patch Set Updates (PSUs). Then, you use that image to add the
-most recent version of the WebLogic Deploy Tooling and your domain model files as a layer on top.
-
-- `Created as part of the image` - This selection stores the domain in the image. This is known as "Domain in Image" but also is referred to as "Image"
-in the WebLogic Kubernetes Operator configuration. Using this option, the domain is created from the model by the
-WebLogic Image Tool (using the WebLogic Deploy Tooling) and baked into the image. While this saves a little overhead
-at startup, it is more expensive to maintain due to the need to recreate the domain every time a new WebLogic
-Server image is created.
-
-- `Externally created in a Kubernetes persistent volume` - This selection stores the domain in a Kubernetes persistent volume; this is known as "Domain in PV".
-This closely approximates the traditional way of maintaining a domain where the domain is created on disk and then
-used and maintained for as long as necessary. Depending on which Fusion Middleware products you are using, this may be
-your only supported choice for running the domain in Kubernetes. The WKT UI application currently doesn't do anything to help
-you create the persistent volume, the necessary persistent volume claim, or the domain. After those things exist, the
-application will allow you to use them to deploy new domains stored in a persistent volume.
-
-##### Choosing a Kubernetes Environment Target Type
-The target type tells the application what sort of Kubernetes environment that you plan to use. Currently, `WebLogic
-Kubernetes Operator` and `Verrazzano` are the only two choices. The application uses the target type to:
-
-- Tell WDT how to prepare the model for deployment.
-- Determine what sections and their associated actions within the application, to display.
-
-For example, the `Kubernetes` pages are relevant to the WebLogic Kubernetes Operator target type, so those pages
-and their associated actions are hidden when the Verrazzano target type is selected; instead, the `Verrazzano`
-pages are displayed. Note that in the current release, Verrazzano support is limited to the `Model` and `Image` sections.
-
-#### Choosing the Java and Oracle Installation Directories
-The application uses these directories when invoking the WebLogic Deploy Tooling and WebLogic Image Tool; it does not
-use them for any other purpose. When selecting these directories, make sure to select the same directory you would use
-to set the `JAVA_HOME` and `ORACLE_HOME` (or `MW_HOME`) environment variables. These are generally the top-level
-installation directories.
-
-#### Choosing the Image Build Tool
-To build new images, inspect images, and interact with image repositories, the WKT UI application uses an image build
-tool, which defaults to `docker`. The image build tool must be installed locally, as mentioned in the [Prerequisites]({{< relref "/setup/prerequisites.md" >}}).
-While `docker` is currently the most popular tool, many vendors (for example, Oracle, IBM RedHat, Google) are moving to
-use `podman` by default.
diff --git a/documentation/1.0/content/release notes/_index.md b/documentation/1.0/content/release notes/_index.md
deleted file mode 100644
index 525b0e18b..000000000
--- a/documentation/1.0/content/release notes/_index.md
+++ /dev/null
@@ -1,29 +0,0 @@
-+++
-title = "Release Notes"
-date = 2019-02-22T15:27:38-05:00
-weight = 5
-pre = ""
-+++
-
-### Known Issues
-
-- On Windows, the Application Update dialog `Install on Exit` works _only_ if you installed the application for the current user only. If the application was installed for all users, `Install on Exit` will cause the older version of the application to be uninstalled but the new version will not be installed. This is due to issue https://github.com/electron-userland/electron-builder/issues/2363. This issue is fixed in the latest version of electron-updater but unfortunately, the fix breaks the `Install Now` functionality (see issue https://github.com/electron-userland/electron-builder/issues/6425).
-
-- When running the WKT UI application on Windows, the image builder tool (docker or podman) also must be directly executable in Windows. For example, there is currently no support for running the WKT UI application in Windows and running podman under the Windows Subsystem for Linux (WSL2). However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use podman on Windows, then refer to the podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.
-
-- On Linux, the application depends on libGL being installed. libGL is not currently listed in the dependencies list for the `rpm` (or `deb`) installers. Therefore, you will need to install libGL using your package manager. For example:
- ```
- sudo yum install libGL
- ```
-
-- When trying to run the application on a Linux machine and display it on a Windows machine, do not use the Xming X server. There appears to be a bug (presumably with their OpenGL support) that prevents applications using Electron 13.x or later from working (for example, Microsoft VS Code doesn't work either).
-
-- On Linux when running the application that was installed using the `rpm` or `deb` installers, the following error messages will appear in the log. These are expected and can safely be ignored. The errors are due to the fact that the electron-updater package being used to perform application updates only supports upgrading Linux applications when run using an `AppImage` binary.
- ```
- info: Checking for update
- error: Error: Error: ENOENT: no such file or directory, open '/opt/WebLogic Kubernetes Toolkit UI/resources/app-update.yml'
- error: Application auto-updater failed: ENOENT: no such file or directory, open '/opt/WebLogic Kubernetes Toolkit UI/resources/app-update.yml'
- error: Error: ENOENT: no such file or directory, open '/opt/WebLogic Kubernetes Toolkit UI/resources/app-update.yml'
- ```
-
-- The application is limited to working with archive files whose size is less than 2 GB.
diff --git a/documentation/1.0/content/setup/install.md b/documentation/1.0/content/setup/install.md
deleted file mode 100644
index d47e3d81f..000000000
--- a/documentation/1.0/content/setup/install.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: "Install WKT UI"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 2
-description: "Install the WKT UI application and check for updates."
----
-
-1. Download the latest WebLogic Kubernetes Toolkit UI (WKT UI) application installers from the [GitHub Releases section](https://github.com/oracle/weblogic-toolkit-ui/releases) of this repository.
-2. Simply run the appropriate installer for your operating system.
-
-
-**NOTE**: On Linux, to get _all_ the dependencies and have them installed in the correct order, you need to use the package manager to install the `rpm` or `deb` file. First, be sure to review the Linux prerequisites [here]({{< relref "/setup/prerequisites.md" >}}).
-
-- For RPM-based systems, use either `yum` or `dnf`; for example:
- ```
- sudo yum -y localinstall wktui_1.0.0_amd64.rpm
- ```
-
-- For Debian-based systems, use:
- ```
- sudo apt install ./wktui_1.0.0_amd64.deb
- ```
-Alternatively, you can download the `AppImage` file, copy it to your local file system, then either:
-- Open a terminal, navigate to the directory where the file exists, and make it executable; for example:
-
- `chmod u+x `
-
-- Use your file manager, right click on the file, edit the properties, and change the permissions to make it executable.
-
-If you download and run the `AppImage` file, you get the added benefits of 1.) Not requiring an installation or root access and 2.) Being able to participate in the auto-update functionality, like MacOS and Windows.
-
-#### Helpful Hints
-
-- When launching the WKT UI application, if you see this:
- ```
- libGL error: No matching fbConfigs or visuals found
- libGL error: failed to load driver: swrast
- ```
- This is harmless and can be removed by setting the environment variable:
-
- `export LIBGL_ALWAYS_INDIRECT=1`
-
-
-- If you are storing credentials in the OS native store, and you see this failure message:
- ```
- Error occurred in handler for 'save-project': Error: Failed to save credential for image.
- imageRegistryPushUser: Error: No such interface "org.freedesktop.Secret.Collection" on object at path /
- org/freedesktop/secrets/collection/login
- at /tmp/.mount_WebLogpIPFto/resources/app.asar/app/js/credentialManager.js:92:32
- ```
- You can solve it by running this command (only once) before launching the WKT UI application:
-
- `dbus-update-activation-environment --systemd DBUS_SESSION_BUS_ADDRESS DISPLAY XAUTHORITY`
-
-### Application Startup
-
-Application startup detects Internet connectivity to GitHub. If it fails to connect, a `Network Configuration` dialog appears in which you can set or modify your proxy settings, test your changes, and then restart the application.
-
-Launching the application displays a thorough "Introduction" to the WKT UI. Step through it or dismiss it; you can peruse it at any time using `Help > Show Introduction`.
-
-### Version Updates
-
-Upon application startup, if a more recent version exists, an Application Update dialog appears with these choices:
-
-- `Install Now`
-- `Install on Exit`
- - Downloads the application and installs it after you exit.
- - Not available on MacOS.
-- `Ignore Update`
-
-At any time, you can check for application updates using `Help > Check for WKT UI Updates`.
-
-For updates to in-application versions of WKT Tools (WebLogic Deploy Tooling and WebLogic Image Tool), select `Help > Check for WKT Tool Updates`.
diff --git a/documentation/staging/.gitkeep b/documentation/1.1/.gitkeep
similarity index 100%
rename from documentation/staging/.gitkeep
rename to documentation/1.1/.gitkeep
diff --git a/documentation/1.0/archetypes/default.md b/documentation/1.1/archetypes/default.md
similarity index 100%
rename from documentation/1.0/archetypes/default.md
rename to documentation/1.1/archetypes/default.md
diff --git a/documentation/1.0/config.toml b/documentation/1.1/config.toml
similarity index 100%
rename from documentation/1.0/config.toml
rename to documentation/1.1/config.toml
diff --git a/documentation/1.0/content/_index.md b/documentation/1.1/content/_index.md
similarity index 100%
rename from documentation/1.0/content/_index.md
rename to documentation/1.1/content/_index.md
diff --git a/documentation/staging/content/concepts/_index.md b/documentation/1.1/content/concepts/_index.md
similarity index 100%
rename from documentation/staging/content/concepts/_index.md
rename to documentation/1.1/content/concepts/_index.md
diff --git a/documentation/staging/content/developer/_index.md b/documentation/1.1/content/developer/_index.md
similarity index 100%
rename from documentation/staging/content/developer/_index.md
rename to documentation/1.1/content/developer/_index.md
diff --git a/documentation/1.0/content/navigate/_index.md b/documentation/1.1/content/navigate/_index.md
similarity index 100%
rename from documentation/1.0/content/navigate/_index.md
rename to documentation/1.1/content/navigate/_index.md
diff --git a/documentation/staging/content/navigate/image.md b/documentation/1.1/content/navigate/image.md
similarity index 100%
rename from documentation/staging/content/navigate/image.md
rename to documentation/1.1/content/navigate/image.md
diff --git a/documentation/1.0/content/navigate/kubernetes/_index.md b/documentation/1.1/content/navigate/kubernetes/_index.md
similarity index 100%
rename from documentation/1.0/content/navigate/kubernetes/_index.md
rename to documentation/1.1/content/navigate/kubernetes/_index.md
diff --git a/documentation/staging/content/navigate/kubernetes/k8s-client-config.md b/documentation/1.1/content/navigate/kubernetes/k8s-client-config.md
similarity index 100%
rename from documentation/staging/content/navigate/kubernetes/k8s-client-config.md
rename to documentation/1.1/content/navigate/kubernetes/k8s-client-config.md
diff --git a/documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md b/documentation/1.1/content/navigate/kubernetes/k8s-ingress-controller.md
similarity index 100%
rename from documentation/staging/content/navigate/kubernetes/k8s-ingress-controller.md
rename to documentation/1.1/content/navigate/kubernetes/k8s-ingress-controller.md
diff --git a/documentation/staging/content/navigate/kubernetes/k8s-weblogic-domain.md b/documentation/1.1/content/navigate/kubernetes/k8s-weblogic-domain.md
similarity index 100%
rename from documentation/staging/content/navigate/kubernetes/k8s-weblogic-domain.md
rename to documentation/1.1/content/navigate/kubernetes/k8s-weblogic-domain.md
diff --git a/documentation/staging/content/navigate/kubernetes/k8s-wko.md b/documentation/1.1/content/navigate/kubernetes/k8s-wko.md
similarity index 100%
rename from documentation/staging/content/navigate/kubernetes/k8s-wko.md
rename to documentation/1.1/content/navigate/kubernetes/k8s-wko.md
diff --git a/documentation/staging/content/navigate/model.md b/documentation/1.1/content/navigate/model.md
similarity index 100%
rename from documentation/staging/content/navigate/model.md
rename to documentation/1.1/content/navigate/model.md
diff --git a/documentation/staging/content/navigate/project-settings.md b/documentation/1.1/content/navigate/project-settings.md
similarity index 100%
rename from documentation/staging/content/navigate/project-settings.md
rename to documentation/1.1/content/navigate/project-settings.md
diff --git a/documentation/1.0/content/navigate/verrazzano.md b/documentation/1.1/content/navigate/verrazzano.md
similarity index 100%
rename from documentation/1.0/content/navigate/verrazzano.md
rename to documentation/1.1/content/navigate/verrazzano.md
diff --git a/documentation/staging/content/release notes/_index.md b/documentation/1.1/content/release notes/_index.md
similarity index 100%
rename from documentation/staging/content/release notes/_index.md
rename to documentation/1.1/content/release notes/_index.md
diff --git a/documentation/1.0/content/setup/_index.md b/documentation/1.1/content/setup/_index.md
similarity index 100%
rename from documentation/1.0/content/setup/_index.md
rename to documentation/1.1/content/setup/_index.md
diff --git a/documentation/staging/content/setup/install.md b/documentation/1.1/content/setup/install.md
similarity index 100%
rename from documentation/staging/content/setup/install.md
rename to documentation/1.1/content/setup/install.md
diff --git a/documentation/1.0/content/setup/prerequisites.md b/documentation/1.1/content/setup/prerequisites.md
similarity index 100%
rename from documentation/1.0/content/setup/prerequisites.md
rename to documentation/1.1/content/setup/prerequisites.md
diff --git a/documentation/1.0/runlocal.sh b/documentation/1.1/runlocal.sh
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/runlocal.sh
rename to documentation/1.1/runlocal.sh
diff --git a/documentation/1.0/runpublic.sh b/documentation/1.1/runpublic.sh
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/runpublic.sh
rename to documentation/1.1/runpublic.sh
diff --git a/documentation/1.0/static/images/logo.png b/documentation/1.1/static/images/logo.png
similarity index 100%
rename from documentation/1.0/static/images/logo.png
rename to documentation/1.1/static/images/logo.png
diff --git a/documentation/1.0/themes/learn/.editorconfig b/documentation/1.1/themes/learn/.editorconfig
similarity index 100%
rename from documentation/1.0/themes/learn/.editorconfig
rename to documentation/1.1/themes/learn/.editorconfig
diff --git a/documentation/1.0/themes/learn/.gitignore b/documentation/1.1/themes/learn/.gitignore
similarity index 100%
rename from documentation/1.0/themes/learn/.gitignore
rename to documentation/1.1/themes/learn/.gitignore
diff --git a/documentation/1.0/themes/learn/.grenrc.yml b/documentation/1.1/themes/learn/.grenrc.yml
similarity index 100%
rename from documentation/1.0/themes/learn/.grenrc.yml
rename to documentation/1.1/themes/learn/.grenrc.yml
diff --git a/documentation/1.0/themes/learn/CHANGELOG.md b/documentation/1.1/themes/learn/CHANGELOG.md
similarity index 100%
rename from documentation/1.0/themes/learn/CHANGELOG.md
rename to documentation/1.1/themes/learn/CHANGELOG.md
diff --git a/documentation/1.0/themes/learn/LICENSE.md b/documentation/1.1/themes/learn/LICENSE.md
similarity index 100%
rename from documentation/1.0/themes/learn/LICENSE.md
rename to documentation/1.1/themes/learn/LICENSE.md
diff --git a/documentation/1.0/themes/learn/README.md b/documentation/1.1/themes/learn/README.md
similarity index 100%
rename from documentation/1.0/themes/learn/README.md
rename to documentation/1.1/themes/learn/README.md
diff --git a/documentation/1.0/themes/learn/archetypes/chapter.md b/documentation/1.1/themes/learn/archetypes/chapter.md
similarity index 100%
rename from documentation/1.0/themes/learn/archetypes/chapter.md
rename to documentation/1.1/themes/learn/archetypes/chapter.md
diff --git a/documentation/1.0/themes/learn/archetypes/default.md b/documentation/1.1/themes/learn/archetypes/default.md
similarity index 100%
rename from documentation/1.0/themes/learn/archetypes/default.md
rename to documentation/1.1/themes/learn/archetypes/default.md
diff --git a/documentation/1.0/themes/learn/exampleSite/LICENSE.md b/documentation/1.1/themes/learn/exampleSite/LICENSE.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/LICENSE.md
rename to documentation/1.1/themes/learn/exampleSite/LICENSE.md
diff --git a/documentation/1.0/themes/learn/exampleSite/config.toml b/documentation/1.1/themes/learn/exampleSite/config.toml
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/config.toml
rename to documentation/1.1/themes/learn/exampleSite/config.toml
diff --git a/documentation/1.0/themes/learn/exampleSite/content/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/basics/_index.en.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/basics/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/_index.zh.md b/documentation/1.1/themes/learn/exampleSite/content/basics/_index.zh.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/_index.zh.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/_index.zh.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/configuration/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/basics/configuration/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/configuration/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/configuration/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/configuration/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/basics/configuration/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/configuration/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/configuration/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg b/documentation/1.1/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg
rename to documentation/1.1/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/installation/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/basics/installation/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/installation/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/installation/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/installation/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/basics/installation/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/installation/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/installation/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/installation/images/chapter.png b/documentation/1.1/themes/learn/exampleSite/content/basics/installation/images/chapter.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/installation/images/chapter.png
rename to documentation/1.1/themes/learn/exampleSite/content/basics/installation/images/chapter.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/requirements/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/basics/requirements/_index.en.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/requirements/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/requirements/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/requirements/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/basics/requirements/_index.fr.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/requirements/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/requirements/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/requirements/images/magic.gif b/documentation/1.1/themes/learn/exampleSite/content/basics/requirements/images/magic.gif
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/requirements/images/magic.gif
rename to documentation/1.1/themes/learn/exampleSite/content/basics/requirements/images/magic.gif
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png b/documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png
rename to documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png b/documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png
rename to documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png b/documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png
rename to documentation/1.1/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/_index.en.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/_index.fr.md
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/archetypes.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/archetypes.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/archetypes.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/archetypes.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/archetypes.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/archetypes.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/archetypes.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/archetypes.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/i18n/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/i18n/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/i18n/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/i18n/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/i18n/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/i18n/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/i18n/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/i18n/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif b/documentation/1.1/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif
rename to documentation/1.1/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/icons.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/icons.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/icons.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/icons.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/markdown.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/markdown.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/markdown.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/markdown.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/markdown.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/markdown.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/markdown.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/markdown.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/menushortcuts.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/menushortcuts.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/menushortcuts.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/menushortcuts.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/menushortcuts.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/menushortcuts.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/menushortcuts.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/menushortcuts.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/pages/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/pages/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/pages/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/pages/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/pages/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/pages/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/pages/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/pages/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png b/documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png
rename to documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png b/documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png
rename to documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/pages-default.png b/documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/pages-default.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/pages/images/pages-default.png
rename to documentation/1.1/themes/learn/exampleSite/content/cont/pages/images/pages-default.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/tags.en.md b/documentation/1.1/themes/learn/exampleSite/content/cont/tags.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/tags.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/tags.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/cont/tags.fr.md b/documentation/1.1/themes/learn/exampleSite/content/cont/tags.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/cont/tags.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/cont/tags.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/credits.en.md b/documentation/1.1/themes/learn/exampleSite/content/credits.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/credits.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/credits.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/credits.fr.md b/documentation/1.1/themes/learn/exampleSite/content/credits.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/credits.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/credits.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3 b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4 b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3 b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4 b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/attachments.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/attachments.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/button.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/button.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/button.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/button.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/button.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/button.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/button.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/button.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/test.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/test.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/test.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/test.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/test.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/test.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/children/test.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/children/test.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/expand.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/expand.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/expand.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/expand.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/expand.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/expand.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/expand.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/expand.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/mermaid.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/mermaid.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/mermaid.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/mermaid.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/notice.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/notice.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/notice.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/notice.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/notice.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/notice.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/notice.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/notice.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/siteparam.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/siteparam.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/siteparam.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/siteparam.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/shortcodes/tabs.en.md b/documentation/1.1/themes/learn/exampleSite/content/shortcodes/tabs.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/shortcodes/tabs.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/shortcodes/tabs.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/showcase.en.md b/documentation/1.1/themes/learn/exampleSite/content/showcase.en.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/showcase.en.md
rename to documentation/1.1/themes/learn/exampleSite/content/showcase.en.md
diff --git a/documentation/1.0/themes/learn/exampleSite/content/showcase.fr.md b/documentation/1.1/themes/learn/exampleSite/content/showcase.fr.md
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/content/showcase.fr.md
rename to documentation/1.1/themes/learn/exampleSite/content/showcase.fr.md
diff --git a/documentation/1.0/themes/learn/exampleSite/layouts/partials/custom-footer.html b/documentation/1.1/themes/learn/exampleSite/layouts/partials/custom-footer.html
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/layouts/partials/custom-footer.html
rename to documentation/1.1/themes/learn/exampleSite/layouts/partials/custom-footer.html
diff --git a/documentation/1.0/themes/learn/exampleSite/layouts/partials/logo.html b/documentation/1.1/themes/learn/exampleSite/layouts/partials/logo.html
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/layouts/partials/logo.html
rename to documentation/1.1/themes/learn/exampleSite/layouts/partials/logo.html
diff --git a/documentation/1.0/themes/learn/exampleSite/layouts/partials/menu-footer.html b/documentation/1.1/themes/learn/exampleSite/layouts/partials/menu-footer.html
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/layouts/partials/menu-footer.html
rename to documentation/1.1/themes/learn/exampleSite/layouts/partials/menu-footer.html
diff --git a/documentation/1.0/themes/learn/exampleSite/layouts/shortcodes/ghcontributors.html b/documentation/1.1/themes/learn/exampleSite/layouts/shortcodes/ghcontributors.html
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/layouts/shortcodes/ghcontributors.html
rename to documentation/1.1/themes/learn/exampleSite/layouts/shortcodes/ghcontributors.html
diff --git a/documentation/1.0/themes/learn/exampleSite/static/css/theme-mine.css b/documentation/1.1/themes/learn/exampleSite/static/css/theme-mine.css
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/css/theme-mine.css
rename to documentation/1.1/themes/learn/exampleSite/static/css/theme-mine.css
diff --git a/documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.eot b/documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.eot
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.eot
rename to documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.eot
diff --git a/documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.svg b/documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.svg
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.svg
rename to documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.svg
diff --git a/documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.ttf b/documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.ttf
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.ttf
rename to documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.ttf
diff --git a/documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff b/documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff
rename to documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff
diff --git a/documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff2 b/documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff2
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff2
rename to documentation/1.1/themes/learn/exampleSite/static/fonts/monogramos-webfont.woff2
diff --git a/documentation/1.0/themes/learn/exampleSite/static/images/showcase/inteliver_docs.png b/documentation/1.1/themes/learn/exampleSite/static/images/showcase/inteliver_docs.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/images/showcase/inteliver_docs.png
rename to documentation/1.1/themes/learn/exampleSite/static/images/showcase/inteliver_docs.png
diff --git a/documentation/1.0/themes/learn/exampleSite/static/images/showcase/tat.png b/documentation/1.1/themes/learn/exampleSite/static/images/showcase/tat.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/images/showcase/tat.png
rename to documentation/1.1/themes/learn/exampleSite/static/images/showcase/tat.png
diff --git a/documentation/1.0/themes/learn/exampleSite/static/images/showcase/tshark_dev.png b/documentation/1.1/themes/learn/exampleSite/static/images/showcase/tshark_dev.png
similarity index 100%
rename from documentation/1.0/themes/learn/exampleSite/static/images/showcase/tshark_dev.png
rename to documentation/1.1/themes/learn/exampleSite/static/images/showcase/tshark_dev.png
diff --git a/documentation/1.0/themes/learn/i18n/ar.toml b/documentation/1.1/themes/learn/i18n/ar.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/ar.toml
rename to documentation/1.1/themes/learn/i18n/ar.toml
diff --git a/documentation/1.0/themes/learn/i18n/de.toml b/documentation/1.1/themes/learn/i18n/de.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/de.toml
rename to documentation/1.1/themes/learn/i18n/de.toml
diff --git a/documentation/1.0/themes/learn/i18n/en.toml b/documentation/1.1/themes/learn/i18n/en.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/en.toml
rename to documentation/1.1/themes/learn/i18n/en.toml
diff --git a/documentation/1.0/themes/learn/i18n/es.toml b/documentation/1.1/themes/learn/i18n/es.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/es.toml
rename to documentation/1.1/themes/learn/i18n/es.toml
diff --git a/documentation/1.0/themes/learn/i18n/fr.toml b/documentation/1.1/themes/learn/i18n/fr.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/fr.toml
rename to documentation/1.1/themes/learn/i18n/fr.toml
diff --git a/documentation/1.0/themes/learn/i18n/hi.toml b/documentation/1.1/themes/learn/i18n/hi.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/hi.toml
rename to documentation/1.1/themes/learn/i18n/hi.toml
diff --git a/documentation/1.0/themes/learn/i18n/id.toml b/documentation/1.1/themes/learn/i18n/id.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/id.toml
rename to documentation/1.1/themes/learn/i18n/id.toml
diff --git a/documentation/1.0/themes/learn/i18n/ja.toml b/documentation/1.1/themes/learn/i18n/ja.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/ja.toml
rename to documentation/1.1/themes/learn/i18n/ja.toml
diff --git a/documentation/1.0/themes/learn/i18n/nl.toml b/documentation/1.1/themes/learn/i18n/nl.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/nl.toml
rename to documentation/1.1/themes/learn/i18n/nl.toml
diff --git a/documentation/1.0/themes/learn/i18n/pt.toml b/documentation/1.1/themes/learn/i18n/pt.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/pt.toml
rename to documentation/1.1/themes/learn/i18n/pt.toml
diff --git a/documentation/1.0/themes/learn/i18n/ru.toml b/documentation/1.1/themes/learn/i18n/ru.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/ru.toml
rename to documentation/1.1/themes/learn/i18n/ru.toml
diff --git a/documentation/1.0/themes/learn/i18n/tr.toml b/documentation/1.1/themes/learn/i18n/tr.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/tr.toml
rename to documentation/1.1/themes/learn/i18n/tr.toml
diff --git a/documentation/1.0/themes/learn/i18n/zh-cn.toml b/documentation/1.1/themes/learn/i18n/zh-cn.toml
similarity index 100%
rename from documentation/1.0/themes/learn/i18n/zh-cn.toml
rename to documentation/1.1/themes/learn/i18n/zh-cn.toml
diff --git a/documentation/1.0/themes/learn/images/screenshot.png b/documentation/1.1/themes/learn/images/screenshot.png
similarity index 100%
rename from documentation/1.0/themes/learn/images/screenshot.png
rename to documentation/1.1/themes/learn/images/screenshot.png
diff --git a/documentation/1.0/themes/learn/images/tn.png b/documentation/1.1/themes/learn/images/tn.png
similarity index 100%
rename from documentation/1.0/themes/learn/images/tn.png
rename to documentation/1.1/themes/learn/images/tn.png
diff --git a/documentation/1.0/themes/learn/layouts/404.html b/documentation/1.1/themes/learn/layouts/404.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/404.html
rename to documentation/1.1/themes/learn/layouts/404.html
diff --git a/documentation/1.0/themes/learn/layouts/_default/list.html b/documentation/1.1/themes/learn/layouts/_default/list.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/_default/list.html
rename to documentation/1.1/themes/learn/layouts/_default/list.html
diff --git a/documentation/1.0/themes/learn/layouts/_default/single.html b/documentation/1.1/themes/learn/layouts/_default/single.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/_default/single.html
rename to documentation/1.1/themes/learn/layouts/_default/single.html
diff --git a/documentation/1.0/themes/learn/layouts/index.html b/documentation/1.1/themes/learn/layouts/index.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/index.html
rename to documentation/1.1/themes/learn/layouts/index.html
diff --git a/documentation/1.0/themes/learn/layouts/index.json b/documentation/1.1/themes/learn/layouts/index.json
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/index.json
rename to documentation/1.1/themes/learn/layouts/index.json
diff --git a/documentation/1.0/themes/learn/layouts/partials/custom-comments.html b/documentation/1.1/themes/learn/layouts/partials/custom-comments.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/custom-comments.html
rename to documentation/1.1/themes/learn/layouts/partials/custom-comments.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/custom-footer.html b/documentation/1.1/themes/learn/layouts/partials/custom-footer.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/custom-footer.html
rename to documentation/1.1/themes/learn/layouts/partials/custom-footer.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/custom-header.html b/documentation/1.1/themes/learn/layouts/partials/custom-header.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/custom-header.html
rename to documentation/1.1/themes/learn/layouts/partials/custom-header.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/favicon.html b/documentation/1.1/themes/learn/layouts/partials/favicon.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/favicon.html
rename to documentation/1.1/themes/learn/layouts/partials/favicon.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/footer.html b/documentation/1.1/themes/learn/layouts/partials/footer.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/footer.html
rename to documentation/1.1/themes/learn/layouts/partials/footer.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/header.html b/documentation/1.1/themes/learn/layouts/partials/header.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/header.html
rename to documentation/1.1/themes/learn/layouts/partials/header.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/logo.html b/documentation/1.1/themes/learn/layouts/partials/logo.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/logo.html
rename to documentation/1.1/themes/learn/layouts/partials/logo.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/menu-footer.html b/documentation/1.1/themes/learn/layouts/partials/menu-footer.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/menu-footer.html
rename to documentation/1.1/themes/learn/layouts/partials/menu-footer.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/menu.html b/documentation/1.1/themes/learn/layouts/partials/menu.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/menu.html
rename to documentation/1.1/themes/learn/layouts/partials/menu.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/meta.html b/documentation/1.1/themes/learn/layouts/partials/meta.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/meta.html
rename to documentation/1.1/themes/learn/layouts/partials/meta.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/search.html b/documentation/1.1/themes/learn/layouts/partials/search.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/search.html
rename to documentation/1.1/themes/learn/layouts/partials/search.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/tags.html b/documentation/1.1/themes/learn/layouts/partials/tags.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/tags.html
rename to documentation/1.1/themes/learn/layouts/partials/tags.html
diff --git a/documentation/1.0/themes/learn/layouts/partials/toc.html b/documentation/1.1/themes/learn/layouts/partials/toc.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/partials/toc.html
rename to documentation/1.1/themes/learn/layouts/partials/toc.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/attachments.html b/documentation/1.1/themes/learn/layouts/shortcodes/attachments.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/attachments.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/attachments.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/button.html b/documentation/1.1/themes/learn/layouts/shortcodes/button.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/button.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/button.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/children.html b/documentation/1.1/themes/learn/layouts/shortcodes/children.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/children.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/children.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/expand.html b/documentation/1.1/themes/learn/layouts/shortcodes/expand.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/expand.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/expand.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/mermaid.html b/documentation/1.1/themes/learn/layouts/shortcodes/mermaid.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/mermaid.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/mermaid.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/notice.html b/documentation/1.1/themes/learn/layouts/shortcodes/notice.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/notice.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/notice.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/ref.html b/documentation/1.1/themes/learn/layouts/shortcodes/ref.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/ref.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/ref.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/relref.html b/documentation/1.1/themes/learn/layouts/shortcodes/relref.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/relref.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/relref.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/siteparam.html b/documentation/1.1/themes/learn/layouts/shortcodes/siteparam.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/siteparam.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/siteparam.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/tab.html b/documentation/1.1/themes/learn/layouts/shortcodes/tab.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/tab.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/tab.html
diff --git a/documentation/1.0/themes/learn/layouts/shortcodes/tabs.html b/documentation/1.1/themes/learn/layouts/shortcodes/tabs.html
similarity index 100%
rename from documentation/1.0/themes/learn/layouts/shortcodes/tabs.html
rename to documentation/1.1/themes/learn/layouts/shortcodes/tabs.html
diff --git a/documentation/1.0/themes/learn/netlify.toml b/documentation/1.1/themes/learn/netlify.toml
similarity index 100%
rename from documentation/1.0/themes/learn/netlify.toml
rename to documentation/1.1/themes/learn/netlify.toml
diff --git a/documentation/1.0/themes/learn/static/css/atom-one-dark-reasonable.css b/documentation/1.1/themes/learn/static/css/atom-one-dark-reasonable.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/atom-one-dark-reasonable.css
rename to documentation/1.1/themes/learn/static/css/atom-one-dark-reasonable.css
diff --git a/documentation/1.0/themes/learn/static/css/auto-complete.css b/documentation/1.1/themes/learn/static/css/auto-complete.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/auto-complete.css
rename to documentation/1.1/themes/learn/static/css/auto-complete.css
diff --git a/documentation/1.0/themes/learn/static/css/featherlight.min.css b/documentation/1.1/themes/learn/static/css/featherlight.min.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/featherlight.min.css
rename to documentation/1.1/themes/learn/static/css/featherlight.min.css
diff --git a/documentation/1.0/themes/learn/static/css/fontawesome-all.min.css b/documentation/1.1/themes/learn/static/css/fontawesome-all.min.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/fontawesome-all.min.css
rename to documentation/1.1/themes/learn/static/css/fontawesome-all.min.css
diff --git a/documentation/1.0/themes/learn/static/css/hugo-theme.css b/documentation/1.1/themes/learn/static/css/hugo-theme.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/hugo-theme.css
rename to documentation/1.1/themes/learn/static/css/hugo-theme.css
diff --git a/documentation/1.0/themes/learn/static/css/hybrid.css b/documentation/1.1/themes/learn/static/css/hybrid.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/hybrid.css
rename to documentation/1.1/themes/learn/static/css/hybrid.css
diff --git a/documentation/1.0/themes/learn/static/css/nucleus.css b/documentation/1.1/themes/learn/static/css/nucleus.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/nucleus.css
rename to documentation/1.1/themes/learn/static/css/nucleus.css
diff --git a/documentation/1.0/themes/learn/static/css/perfect-scrollbar.min.css b/documentation/1.1/themes/learn/static/css/perfect-scrollbar.min.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/perfect-scrollbar.min.css
rename to documentation/1.1/themes/learn/static/css/perfect-scrollbar.min.css
diff --git a/documentation/1.0/themes/learn/static/css/tabs.css b/documentation/1.1/themes/learn/static/css/tabs.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/tabs.css
rename to documentation/1.1/themes/learn/static/css/tabs.css
diff --git a/documentation/1.0/themes/learn/static/css/tags.css b/documentation/1.1/themes/learn/static/css/tags.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/tags.css
rename to documentation/1.1/themes/learn/static/css/tags.css
diff --git a/documentation/1.0/themes/learn/static/css/theme-blue.css b/documentation/1.1/themes/learn/static/css/theme-blue.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/theme-blue.css
rename to documentation/1.1/themes/learn/static/css/theme-blue.css
diff --git a/documentation/1.0/themes/learn/static/css/theme-green.css b/documentation/1.1/themes/learn/static/css/theme-green.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/theme-green.css
rename to documentation/1.1/themes/learn/static/css/theme-green.css
diff --git a/documentation/1.0/themes/learn/static/css/theme-red.css b/documentation/1.1/themes/learn/static/css/theme-red.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/theme-red.css
rename to documentation/1.1/themes/learn/static/css/theme-red.css
diff --git a/documentation/1.0/themes/learn/static/css/theme.css b/documentation/1.1/themes/learn/static/css/theme.css
similarity index 100%
rename from documentation/1.0/themes/learn/static/css/theme.css
rename to documentation/1.1/themes/learn/static/css/theme.css
diff --git a/documentation/1.0/themes/learn/static/fonts/Inconsolata.eot b/documentation/1.1/themes/learn/static/fonts/Inconsolata.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Inconsolata.eot
rename to documentation/1.1/themes/learn/static/fonts/Inconsolata.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Inconsolata.svg b/documentation/1.1/themes/learn/static/fonts/Inconsolata.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Inconsolata.svg
rename to documentation/1.1/themes/learn/static/fonts/Inconsolata.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Inconsolata.ttf b/documentation/1.1/themes/learn/static/fonts/Inconsolata.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Inconsolata.ttf
rename to documentation/1.1/themes/learn/static/fonts/Inconsolata.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Inconsolata.woff b/documentation/1.1/themes/learn/static/fonts/Inconsolata.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Inconsolata.woff
rename to documentation/1.1/themes/learn/static/fonts/Inconsolata.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.eot b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.eot
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.svg b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.svg
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.ttf b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.ttf
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff2 b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff2
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-Normal-webfont.woff2
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.eot b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.eot
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.svg b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.svg
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.ttf b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.ttf
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff2 b/documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff2
rename to documentation/1.1/themes/learn/static/fonts/Novecentosanswide-UltraLight-webfont.woff2
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_200.eot b/documentation/1.1/themes/learn/static/fonts/Work_Sans_200.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_200.eot
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_200.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_200.svg b/documentation/1.1/themes/learn/static/fonts/Work_Sans_200.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_200.svg
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_200.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_200.ttf b/documentation/1.1/themes/learn/static/fonts/Work_Sans_200.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_200.ttf
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_200.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_200.woff b/documentation/1.1/themes/learn/static/fonts/Work_Sans_200.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_200.woff
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_200.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_200.woff2 b/documentation/1.1/themes/learn/static/fonts/Work_Sans_200.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_200.woff2
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_200.woff2
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_300.eot b/documentation/1.1/themes/learn/static/fonts/Work_Sans_300.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_300.eot
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_300.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_300.svg b/documentation/1.1/themes/learn/static/fonts/Work_Sans_300.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_300.svg
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_300.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_300.ttf b/documentation/1.1/themes/learn/static/fonts/Work_Sans_300.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_300.ttf
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_300.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_300.woff b/documentation/1.1/themes/learn/static/fonts/Work_Sans_300.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_300.woff
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_300.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_300.woff2 b/documentation/1.1/themes/learn/static/fonts/Work_Sans_300.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_300.woff2
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_300.woff2
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_500.eot b/documentation/1.1/themes/learn/static/fonts/Work_Sans_500.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_500.eot
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_500.eot
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_500.svg b/documentation/1.1/themes/learn/static/fonts/Work_Sans_500.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_500.svg
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_500.svg
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_500.ttf b/documentation/1.1/themes/learn/static/fonts/Work_Sans_500.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_500.ttf
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_500.ttf
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_500.woff b/documentation/1.1/themes/learn/static/fonts/Work_Sans_500.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_500.woff
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_500.woff
diff --git a/documentation/1.0/themes/learn/static/fonts/Work_Sans_500.woff2 b/documentation/1.1/themes/learn/static/fonts/Work_Sans_500.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/fonts/Work_Sans_500.woff2
rename to documentation/1.1/themes/learn/static/fonts/Work_Sans_500.woff2
diff --git a/documentation/1.0/themes/learn/static/images/clippy.svg b/documentation/1.1/themes/learn/static/images/clippy.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/images/clippy.svg
rename to documentation/1.1/themes/learn/static/images/clippy.svg
diff --git a/documentation/1.0/themes/learn/static/images/favicon.png b/documentation/1.1/themes/learn/static/images/favicon.png
similarity index 100%
rename from documentation/1.0/themes/learn/static/images/favicon.png
rename to documentation/1.1/themes/learn/static/images/favicon.png
diff --git a/documentation/1.0/themes/learn/static/images/gopher-404.jpg b/documentation/1.1/themes/learn/static/images/gopher-404.jpg
similarity index 100%
rename from documentation/1.0/themes/learn/static/images/gopher-404.jpg
rename to documentation/1.1/themes/learn/static/images/gopher-404.jpg
diff --git a/documentation/1.0/themes/learn/static/js/auto-complete.js b/documentation/1.1/themes/learn/static/js/auto-complete.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/auto-complete.js
rename to documentation/1.1/themes/learn/static/js/auto-complete.js
diff --git a/documentation/1.0/themes/learn/static/js/clipboard.min.js b/documentation/1.1/themes/learn/static/js/clipboard.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/clipboard.min.js
rename to documentation/1.1/themes/learn/static/js/clipboard.min.js
diff --git a/documentation/1.0/themes/learn/static/js/featherlight.min.js b/documentation/1.1/themes/learn/static/js/featherlight.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/featherlight.min.js
rename to documentation/1.1/themes/learn/static/js/featherlight.min.js
diff --git a/documentation/1.0/themes/learn/static/js/highlight.pack.js b/documentation/1.1/themes/learn/static/js/highlight.pack.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/highlight.pack.js
rename to documentation/1.1/themes/learn/static/js/highlight.pack.js
diff --git a/documentation/1.0/themes/learn/static/js/hugo-learn.js b/documentation/1.1/themes/learn/static/js/hugo-learn.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/hugo-learn.js
rename to documentation/1.1/themes/learn/static/js/hugo-learn.js
diff --git a/documentation/1.0/themes/learn/static/js/jquery-3.3.1.min.js b/documentation/1.1/themes/learn/static/js/jquery-3.3.1.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/jquery-3.3.1.min.js
rename to documentation/1.1/themes/learn/static/js/jquery-3.3.1.min.js
diff --git a/documentation/1.0/themes/learn/static/js/jquery.sticky.js b/documentation/1.1/themes/learn/static/js/jquery.sticky.js
old mode 100755
new mode 100644
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/jquery.sticky.js
rename to documentation/1.1/themes/learn/static/js/jquery.sticky.js
diff --git a/documentation/1.0/themes/learn/static/js/learn.js b/documentation/1.1/themes/learn/static/js/learn.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/learn.js
rename to documentation/1.1/themes/learn/static/js/learn.js
diff --git a/documentation/1.0/themes/learn/static/js/lunr.min.js b/documentation/1.1/themes/learn/static/js/lunr.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/lunr.min.js
rename to documentation/1.1/themes/learn/static/js/lunr.min.js
diff --git a/documentation/1.0/themes/learn/static/js/modernizr.custom-3.6.0.js b/documentation/1.1/themes/learn/static/js/modernizr.custom-3.6.0.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/modernizr.custom-3.6.0.js
rename to documentation/1.1/themes/learn/static/js/modernizr.custom-3.6.0.js
diff --git a/documentation/1.0/themes/learn/static/js/perfect-scrollbar.jquery.min.js b/documentation/1.1/themes/learn/static/js/perfect-scrollbar.jquery.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/perfect-scrollbar.jquery.min.js
rename to documentation/1.1/themes/learn/static/js/perfect-scrollbar.jquery.min.js
diff --git a/documentation/1.0/themes/learn/static/js/perfect-scrollbar.min.js b/documentation/1.1/themes/learn/static/js/perfect-scrollbar.min.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/perfect-scrollbar.min.js
rename to documentation/1.1/themes/learn/static/js/perfect-scrollbar.min.js
diff --git a/documentation/1.0/themes/learn/static/js/search.js b/documentation/1.1/themes/learn/static/js/search.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/js/search.js
rename to documentation/1.1/themes/learn/static/js/search.js
diff --git a/documentation/1.0/themes/learn/static/mermaid/mermaid.js b/documentation/1.1/themes/learn/static/mermaid/mermaid.js
similarity index 100%
rename from documentation/1.0/themes/learn/static/mermaid/mermaid.js
rename to documentation/1.1/themes/learn/static/mermaid/mermaid.js
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-brands-400.eot b/documentation/1.1/themes/learn/static/webfonts/fa-brands-400.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-brands-400.eot
rename to documentation/1.1/themes/learn/static/webfonts/fa-brands-400.eot
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-brands-400.svg b/documentation/1.1/themes/learn/static/webfonts/fa-brands-400.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-brands-400.svg
rename to documentation/1.1/themes/learn/static/webfonts/fa-brands-400.svg
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-brands-400.ttf b/documentation/1.1/themes/learn/static/webfonts/fa-brands-400.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-brands-400.ttf
rename to documentation/1.1/themes/learn/static/webfonts/fa-brands-400.ttf
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-brands-400.woff b/documentation/1.1/themes/learn/static/webfonts/fa-brands-400.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-brands-400.woff
rename to documentation/1.1/themes/learn/static/webfonts/fa-brands-400.woff
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-brands-400.woff2 b/documentation/1.1/themes/learn/static/webfonts/fa-brands-400.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-brands-400.woff2
rename to documentation/1.1/themes/learn/static/webfonts/fa-brands-400.woff2
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-regular-400.eot b/documentation/1.1/themes/learn/static/webfonts/fa-regular-400.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-regular-400.eot
rename to documentation/1.1/themes/learn/static/webfonts/fa-regular-400.eot
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-regular-400.svg b/documentation/1.1/themes/learn/static/webfonts/fa-regular-400.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-regular-400.svg
rename to documentation/1.1/themes/learn/static/webfonts/fa-regular-400.svg
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-regular-400.ttf b/documentation/1.1/themes/learn/static/webfonts/fa-regular-400.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-regular-400.ttf
rename to documentation/1.1/themes/learn/static/webfonts/fa-regular-400.ttf
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-regular-400.woff b/documentation/1.1/themes/learn/static/webfonts/fa-regular-400.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-regular-400.woff
rename to documentation/1.1/themes/learn/static/webfonts/fa-regular-400.woff
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-regular-400.woff2 b/documentation/1.1/themes/learn/static/webfonts/fa-regular-400.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-regular-400.woff2
rename to documentation/1.1/themes/learn/static/webfonts/fa-regular-400.woff2
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-solid-900.eot b/documentation/1.1/themes/learn/static/webfonts/fa-solid-900.eot
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-solid-900.eot
rename to documentation/1.1/themes/learn/static/webfonts/fa-solid-900.eot
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-solid-900.svg b/documentation/1.1/themes/learn/static/webfonts/fa-solid-900.svg
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-solid-900.svg
rename to documentation/1.1/themes/learn/static/webfonts/fa-solid-900.svg
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-solid-900.ttf b/documentation/1.1/themes/learn/static/webfonts/fa-solid-900.ttf
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-solid-900.ttf
rename to documentation/1.1/themes/learn/static/webfonts/fa-solid-900.ttf
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-solid-900.woff b/documentation/1.1/themes/learn/static/webfonts/fa-solid-900.woff
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-solid-900.woff
rename to documentation/1.1/themes/learn/static/webfonts/fa-solid-900.woff
diff --git a/documentation/1.0/themes/learn/static/webfonts/fa-solid-900.woff2 b/documentation/1.1/themes/learn/static/webfonts/fa-solid-900.woff2
similarity index 100%
rename from documentation/1.0/themes/learn/static/webfonts/fa-solid-900.woff2
rename to documentation/1.1/themes/learn/static/webfonts/fa-solid-900.woff2
diff --git a/documentation/1.0/themes/learn/theme.toml b/documentation/1.1/themes/learn/theme.toml
similarity index 100%
rename from documentation/1.0/themes/learn/theme.toml
rename to documentation/1.1/themes/learn/theme.toml
diff --git a/documentation/1.0/themes/learn/wercker.yml b/documentation/1.1/themes/learn/wercker.yml
similarity index 100%
rename from documentation/1.0/themes/learn/wercker.yml
rename to documentation/1.1/themes/learn/wercker.yml
diff --git a/documentation/staging/archetypes/default.md b/documentation/staging/archetypes/default.md
deleted file mode 100644
index 5ae3c0131..000000000
--- a/documentation/staging/archetypes/default.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: false
----
-
diff --git a/documentation/staging/config.toml b/documentation/staging/config.toml
deleted file mode 100644
index 0e02910d9..000000000
--- a/documentation/staging/config.toml
+++ /dev/null
@@ -1,19 +0,0 @@
-# analytics
-googleAnalytics = "UA-129126578-2"
-
-baseURL = '/weblogic-toolikit-ui'
-languageCode = 'en-us'
-title = 'WebLogic Kubernetes Toolkit UI'
-
-# Change the default theme to be use when building the site with Hugo
-theme = 'learn'
-
-publishDir = "docs"
-
-# For search functionality
-[outputs]
- home = [ "HTML", "RSS", "JSON"]
-
-[params]
- # disable the copy to clipboard links
- disableInlineCopyToClipBoard = true
diff --git a/documentation/staging/content/_index.md b/documentation/staging/content/_index.md
deleted file mode 100644
index c188ae826..000000000
--- a/documentation/staging/content/_index.md
+++ /dev/null
@@ -1,48 +0,0 @@
-## WebLogic Kubernetes Toolkit UI Documentation
-
-The WebLogic Kubernetes Toolkit (WKT) is a collection of open source tools that help you provision WebLogic-based
-applications to run in Linux containers on a Kubernetes cluster. WKT includes the following tools:
-
-- [WebLogic Deploy Tooling (WDT)](https://github.com/oracle/weblogic-deploy-tooling) - A set of single-purpose,
- lifecycle tools that operate off of a single metadata model representation of a WebLogic domain.
-- [WebLogic Image Tool (WIT)](https://github.com/oracle/weblogic-image-tool) - A tool for creating Linux container
- images for running WebLogic domains.
-- [WebLogic Kubernetes Operator (WKO)](https://github.com/oracle/weblogic-kubernetes-operator) - A Kubernetes operator
- that allows WebLogic domains to run natively in a Kubernetes cluster.
-
-The WKT UI provides a graphical user interface that wraps the WKT tools, Docker, Helm, and the Kubernetes client
-(`kubectl`) and helps guide you through the process of creating and modifying a model of your WebLogic domain, creating
-a Linux container image to use to run the domain, and setting up and deploying the software and configuration
-necessary to deploy and access the domain in your Kubernetes cluster.
-
-### Current release
-
-WebLogic Kubernetes Toolkit UI version and release information can be found [here](https://github.com/oracle/weblogic-toolkit-ui/releases).
-
-### About the Documentation
-For detailed user information, read the following:
-
-- [About the WKT UI Application]({{< relref "/concepts/_index.md" >}})
-- WebLogic Kubernetes Toolkit UI [Prerequisites]({{< relref "/setup/prerequisites.md" >}}) and [Installation]({{< relref "/setup/install.md" >}})
-- [Navigate the WKT UI]({{< relref "/navigate/_index.md" >}})
- - [Model]({{< relref "/navigate/model.md" >}})
- - [Image]({{< relref "/navigate/image.md" >}})
- - [Kubernetes]({{< relref "/navigate/kubernetes/_index.md" >}})
- - [Verrazzano]({{< relref "/navigate/verrazzano.md" >}})
-
-For developer information, see [WebLogic Kubernetes Toolkit UI Project]({{< relref "/developer/_index.md" >}}).
-
-### Get Help
-
-We have a closely monitored public Slack channel where you can get in touch with us to ask questions about using the
-WebLogic Toolkit UI or give us feedback or suggestions about what features and improvements you would like to see.
-We would love to hear from you.
-
-To join our public channel, please visit this [site](https://weblogic-slack-inviter.herokuapp.com/) to get an invitation. The invitation email will include details of how to access our Slack workspace. After you are logged in, please come to `#weblogic-kubernetes-toolkit` and say, “hello!”
-
-### Related Projects
-For detailed documentation and access to WebLogic Toolkit-related projects, see:
-
-- [WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/)
-- [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/)
-- [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/)
diff --git a/documentation/staging/content/navigate/_index.md b/documentation/staging/content/navigate/_index.md
deleted file mode 100644
index f125e30d4..000000000
--- a/documentation/staging/content/navigate/_index.md
+++ /dev/null
@@ -1,34 +0,0 @@
-+++
-title = "Navigate the UI"
-date = 2019-02-22T15:27:38-05:00
-weight = 3
-pre = ""
-+++
-
-### Before you begin
-
-Make sure you have read [About the WKT UI Application]({{< relref "/concepts/_index.md" >}}).
-
-### About the UI
-
-To help you understand how to use the WKT UI, we will step you through it, section by section,
-describing the important decisions to make and fields to populate. The sections are listed in
-the left side navigation pane. Depending on the `Kubernetes Environment Target Type` field
-on the `Project Settings` page, you will see either the `Kubernetes` or `Verrazzano` section.
-
-The UI sections are:
-
-- [Project Settings]({{< relref "/navigate/project-settings.md" >}})
-- [Model]({{< relref "/navigate/model.md" >}})
-- [Image]({{< relref "/navigate/image.md" >}})
-- [Kubernetes]({{< relref "/navigate/kubernetes/_index.md" >}})
- - [Client Configuration]({{< relref "/navigate/kubernetes/k8s-client-config.md" >}})
- - [WebLogic Operator]({{< relref "/navigate/kubernetes/k8s-wko.md" >}})
- - [WebLogic Domain]({{< relref "/navigate/kubernetes/k8s-weblogic-domain.md" >}})
- - [Ingress Controller]({{< relref "/navigate/kubernetes/k8s-ingress-controller.md" >}})
-- [Verrazzano]({{< relref "/navigate/verrazzano.md" >}})
- - Client Configuration
- - Application
-
-At the bottom of the page, the collapsed `Console` panel automatically appears and displays the `stdout` and `stderr`
-streams when running certain actions, such as `Prepare Model`.
diff --git a/documentation/staging/content/navigate/kubernetes/_index.md b/documentation/staging/content/navigate/kubernetes/_index.md
deleted file mode 100644
index ad44cdebb..000000000
--- a/documentation/staging/content/navigate/kubernetes/_index.md
+++ /dev/null
@@ -1,18 +0,0 @@
-+++
-title = "Kubernetes"
-date = 2019-02-22T15:27:38-05:00
-weight = 5
-pre = ""
-+++
-
-The `Kubernetes` section and its four subsections support deploying a WebLogic-based application to a
-Kubernetes cluster where the WebLogic domain will be managed by the WebLogic Kubernetes Operator. It includes sections
-to help you:
-
-1. [Configure]({{< relref "/navigate/kubernetes/k8s-client-config#client-configuration" >}}) your Kubernetes client (`kubectl`) to connect to the Kubernetes cluster.
-2. [Install]({{< relref "/navigate/kubernetes/k8s-wko#install-operator" >}}) the WebLogic Kubernetes Operator.
-3. [Deploy]({{< relref "/navigate/kubernetes/k8s-weblogic-domain#deploy-domain" >}}) the WebLogic domain's `Domain` resource configuration used by WebLogic Kubernetes Operator.
-4. [Install]({{< relref "/navigate/kubernetes/k8s-ingress-controller#install-ingress-controller" >}}) an ingress controller, if needed, and add ingress routes to allow access to the WebLogic domain from
- outside the Kubernetes cluster.
-
-{{% children style="h4" description="true" %}}
diff --git a/documentation/staging/content/navigate/verrazzano.md b/documentation/staging/content/navigate/verrazzano.md
deleted file mode 100644
index 81e6a49cf..000000000
--- a/documentation/staging/content/navigate/verrazzano.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Verrazzano"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 6
----
-
-
-
-In the current release, this is a placeholder for pages that will provide similar functionality to the Kubernetes
-section when using Verrazzano.
diff --git a/documentation/staging/content/setup/_index.md b/documentation/staging/content/setup/_index.md
deleted file mode 100644
index 9cdf77d6a..000000000
--- a/documentation/staging/content/setup/_index.md
+++ /dev/null
@@ -1,8 +0,0 @@
-+++
-title = "Get Started"
-date = 2019-02-22T15:27:38-05:00
-weight = 2
-pre = ""
-+++
-
-{{% children style="h4" description="true" %}}
diff --git a/documentation/staging/content/setup/prerequisites.md b/documentation/staging/content/setup/prerequisites.md
deleted file mode 100644
index b26a161a7..000000000
--- a/documentation/staging/content/setup/prerequisites.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: "Prerequisites"
-date: 2019-02-22T15:44:42-05:00
-draft: false
-weight: 1
-description: "Install the prerequisite requirements."
----
-
-
-WebLogic Kubernetes Toolkit UI has a number of prerequisites that must be installed locally to fully use the
-WKT UI application functionality.
-
-These include:
-
-- Java Development Kit (JDK) - Required by both WebLogic Deploy Tooling and WebLogic Image Tool.
- Install a JDK version that is compatible with your local WebLogic Server installation.
-- WebLogic Server (WLS) - Required by WebLogic Deploy Tooling. Install a WebLogic Server version
- 12.2.1.3.0 or later; it is a best practice to install the latest Patch Set Updates (PSUs) and other recommended patches. The
- application uses WebLogic Server to gain access to the WebLogic Server Scripting Tool (WLST) and other related artifacts to use
- as a client.
-- `docker` (or `podman`) - Required to create images locally and interact with image registries.
-- `kubectl` - Required to interact with your Kubernetes cluster. Install a version that is
- compatible with your Kubernetes cluster version. For more information, see the Kubernetes `Client Configuration` page in the UI.
-- Cloud Provider's Command-Line Interface (CLI) tool - If your Kubernetes cluster is running in one of the cloud
- provider's managed Kubernetes services, then you will need to download and install the cloud provider's CLI. This is
- typically required to configure `kubectl` to properly authenticate to the Kubernetes cluster. Again, see the Kubernetes
- `Client Configuration` page for more information about configuring `kubectl` to work with your cluster.
-- `helm` - Helm version 3.3.2 or later. Required to install the WebLogic Kubernetes Operator and to install an ingress controller.
-- `openssl` - Used to generate an X.509 TLS certificate for ingress routes, should you ask the application
- to generate one for you.
-
-The WKT UI application is built using the Electron framework and as such, we support only the platforms and versions supported by [Electron](https://www.electronjs.org/docs/latest/tutorial/support#supported-platforms). For example, because of the Electron requirement for Fedora 24 or newer, we support only versions 8.0 and higher of Oracle Linux, RedHat Linux, and CentOS Linux.
-
-In addition to these local software dependencies, you will need a Kubernetes cluster to which you can deploy your
-containerized WebLogic Server domain and its applications. If you do not already have a model, then you can either write
-one by hand using the WKT UI application or discover the model from an existing domain. Most likely, you'll want to start
-with a WebLogic domain that can be used to discover the model from the domain.
-
-#### Linux Prerequisites
-
-- For RPM-based systems, such as Oracle, RedHat, CentOS, and some others:
-
- - For storing credentials in the OS native credentials store, you must have a desktop environment. If your system does not have a graphical desktop environment, then you can install one; for example, installing GNOME Desktop on Oracle Linux:
-
- https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2717454_1.html
-
- - For storing credentials as an encrypted project file, and for a minimum GUI requirement, make sure the following packages are installed in your system:
- ```
- sudo dnf update
- sudo dnf install libxshmfence libdrm.x86_64 libgbm alsa-lib xauth atk-devel.x86_64 java-atk-wrapper.x86_64
- sudo reboot
- ```
-- For Debian-based systems, such as Ubuntu and Debian:
-
- - For storing credentials in the OS native credentials store, you must have a desktop environment. If your system does not have a graphical desktop environment, then you can install one; for example, installing GNOME on Ubuntu 20x:
- ```
- sudo apt install gnome-session gdm3
- sudo reboot
- ```
diff --git a/documentation/staging/runlocal.sh b/documentation/staging/runlocal.sh
deleted file mode 100644
index a09259d2f..000000000
--- a/documentation/staging/runlocal.sh
+++ /dev/null
@@ -1,9 +0,0 @@
-#!/bin/bash
-#
-# Copyright (c) 2019, 2021, Oracle and/or its affiliates.
-# Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.
-#
-# 1313 is the hugo default port
-port=${1:-1313}
-
-hugo server -b http://localhost:$port/weblogic-toolkit-ui -D -p $port
diff --git a/documentation/staging/runpublic.sh b/documentation/staging/runpublic.sh
deleted file mode 100644
index 38a26b645..000000000
--- a/documentation/staging/runpublic.sh
+++ /dev/null
@@ -1,9 +0,0 @@
-#!/bin/bash
-
-# Copyright (c) 2019, 2021, Oracle and/or its affiliates.
-# Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.
-
-# 1313 is the hugo default port
-port=${1:-1313}
-
-hugo server -b http://$(hostname).$(dnsdomainname):$port/weblogic-toolkit-ui -D --bind=$(hostname).$(dnsdomainname) -p $port
diff --git a/documentation/staging/static/images/logo.png b/documentation/staging/static/images/logo.png
deleted file mode 100644
index 28828b74d..000000000
Binary files a/documentation/staging/static/images/logo.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/.editorconfig b/documentation/staging/themes/learn/.editorconfig
deleted file mode 100644
index 12f0ef580..000000000
--- a/documentation/staging/themes/learn/.editorconfig
+++ /dev/null
@@ -1,16 +0,0 @@
-# https://editorconfig.org
-
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-indent_size = 2
-indent_style = space
-trim_trailing_whitespace = true
-
-[*.js]
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false
diff --git a/documentation/staging/themes/learn/.gitignore b/documentation/staging/themes/learn/.gitignore
deleted file mode 100644
index 64297518e..000000000
--- a/documentation/staging/themes/learn/.gitignore
+++ /dev/null
@@ -1,3 +0,0 @@
-.DS_Store
-public/
-exampleSite/public
diff --git a/documentation/staging/themes/learn/.grenrc.yml b/documentation/staging/themes/learn/.grenrc.yml
deleted file mode 100644
index ad31ac817..000000000
--- a/documentation/staging/themes/learn/.grenrc.yml
+++ /dev/null
@@ -1,25 +0,0 @@
----
- dataSource: "prs"
- prefix: "v"
- onlyMilestones: false
- changelogFilename: "CHANGELOG.md"
- includeMessages: "all"
- ignoreIssuesWith:
- - "support"
- ignoreLabels:
- - "duplicate"
- - "invalid"
- - "wontfix"
- groupBy:
- New features:
- - "feature"
- Bug Fixes:
- - "bug"
- Enhancements:
- - "enhancement"
- Internationalisation:
- - "i18n"
- Theme Meta:
- - "meta"
- Uncategorised:
- - "closed"
diff --git a/documentation/staging/themes/learn/CHANGELOG.md b/documentation/staging/themes/learn/CHANGELOG.md
deleted file mode 100644
index b5f5eac9f..000000000
--- a/documentation/staging/themes/learn/CHANGELOG.md
+++ /dev/null
@@ -1,226 +0,0 @@
-# Changelog
-
-## v2.5.0 (01/06/2020)
-
-#### New features
-
-- [**feature**] Allow custom css files to be loaded by configuration [#376](https://github.com/matcornic/hugo-theme-learn/pull/376)
-- [**feature**] Added flag to turn off image featherlight [#333](https://github.com/matcornic/hugo-theme-learn/pull/333)
-
-#### Bug Fixes
-
-- [**bug**] fix null pointer when no params on image url [#383](https://github.com/matcornic/hugo-theme-learn/pull/383)
-- [**bug**] can't give argument to non-function not .Params.hidden [#403](https://github.com/matcornic/hugo-theme-learn/pull/403)
-- [**bug**] Fix .File.UniqueID on zero object warning [#372](https://github.com/matcornic/hugo-theme-learn/pull/372)
-- [**bug**] fix select option color in Chrome [#345](https://github.com/matcornic/hugo-theme-learn/pull/345)
-- [**bug**] remove unneeded spaces from HTML [#320](https://github.com/matcornic/hugo-theme-learn/pull/320)
-- [**bug**] Avoid displaying hidden sections in menu [#354](https://github.com/matcornic/hugo-theme-learn/pull/354)
-
-#### Enhancements
-
-- [**enhancement**] Updated theme installation documentation link. [#390](https://github.com/matcornic/hugo-theme-learn/pull/390)
-- [**enhancement**] [ImgBot] Optimize images [#366](https://github.com/matcornic/hugo-theme-learn/pull/366)
-- [**enhancement**] fix extra spaces in the description [#339](https://github.com/matcornic/hugo-theme-learn/pull/339)
-- [**enhancement**] change to minified 'autocomplete.js' for improved performance [#321](https://github.com/matcornic/hugo-theme-learn/pull/321)
-
-#### Internationalisation
-
-- [**i18n**] Fix: typos [#343](https://github.com/matcornic/hugo-theme-learn/pull/343)
-- [**i18n**] Fix: typo [#342](https://github.com/matcornic/hugo-theme-learn/pull/342)
-- [**i18n**] Incorrect english in notice documentation [#336](https://github.com/matcornic/hugo-theme-learn/pull/336)
-- [**i18n**] Add Chinese language for this theme [#349](https://github.com/matcornic/hugo-theme-learn/pull/349)
-- [**i18n**] Add jp and zh cn [#335](https://github.com/matcornic/hugo-theme-learn/pull/335)
-- [**i18n**] Added Russian translation [#332](https://github.com/matcornic/hugo-theme-learn/pull/332)
-
-#### Theme Meta
-
-- [**meta**] Fix various linting warnings [#405](https://github.com/matcornic/hugo-theme-learn/pull/405)
-- [**meta**] Netlify build on 0.66.0 [#377](https://github.com/matcornic/hugo-theme-learn/pull/377)
-- [**meta**] add inteliver documentation showcase [#331](https://github.com/matcornic/hugo-theme-learn/pull/331)
-
----
-
-## v2.4.0 (04/09/2019)
-
-#### Bug Fixes
-
-- [**bug**] correct GitHub capitalization [#293](https://github.com/matcornic/hugo-theme-learn/pull/293)
-- [**bug**] fix 'locate' typo [#285](https://github.com/matcornic/hugo-theme-learn/pull/285)
-- [**bug**] Remove reference to the unused horsey CSS [#284](https://github.com/matcornic/hugo-theme-learn/pull/284)
-- [**bug**] Fix invalid HTML in 404 template. [#271](https://github.com/matcornic/hugo-theme-learn/pull/271)
-
-#### Enhancements
-
-- [**enhancement**] Delete html5shiv-printshiv.min.js [#319](https://github.com/matcornic/hugo-theme-learn/pull/319)
-- [**enhancement**] remove html5shiv [#315](https://github.com/matcornic/hugo-theme-learn/pull/315)
-- [**enhancement**] Fix deprecated .Hugo, .UniqueID and .URL references [#303](https://github.com/matcornic/hugo-theme-learn/pull/303)
-- [**enhancement**] Fix type lines 364 and 369 [#304](https://github.com/matcornic/hugo-theme-learn/pull/304)
-- [**enhancement**] remove unneeded type="text/css" [#298](https://github.com/matcornic/hugo-theme-learn/pull/298)
-- [**enhancement**] remove unneeded type="text/css" [#297](https://github.com/matcornic/hugo-theme-learn/pull/297)
-- [**enhancement**] HTTPS links in footer [#295](https://github.com/matcornic/hugo-theme-learn/pull/295)
-- [**enhancement**] remove unneeded type="text/css" [#292](https://github.com/matcornic/hugo-theme-learn/pull/292)
-- [**enhancement**] Make shortcodes & example site compatible with Hugo v0.55 [#281](https://github.com/matcornic/hugo-theme-learn/pull/281)
-
-#### Internationalisation
-
-- [**i18n**] Added German and Arabic translation [#312](https://github.com/matcornic/hugo-theme-learn/pull/312)
-
-#### Theme Meta
-
-- [**meta**] Added Tshark.dev as example site [#318](https://github.com/matcornic/hugo-theme-learn/pull/318)
-
----
-
-## v2.3.0 (16/04/2019)
-
-#### New features
-
-- [**feature**] Added support for tags [#196](https://github.com/matcornic/hugo-theme-learn/pull/196)
-
-#### Bug Fixes
-
-- [**bug**] Fix issue where "children" shortcode only shows top level. [#252](https://github.com/matcornic/hugo-theme-learn/pull/252)
-- [**bug**] Fix translation when using a custom baseURL [#234](https://github.com/matcornic/hugo-theme-learn/pull/234)
-- [**bug**] Preventing left/right arrow key navigation in textareas [#241](https://github.com/matcornic/hugo-theme-learn/pull/241)
-- [**bug**] Update menu.html to include the check icon [#229](https://github.com/matcornic/hugo-theme-learn/pull/229)
-
-#### Enhancements
-
-- [**enhancement**] Render the ```mermaid blocks into graphs [#226](https://github.com/matcornic/hugo-theme-learn/pull/226)
-- [**enhancement**] Remove oudated versions of jquery & modernizr libraries [#259](https://github.com/matcornic/hugo-theme-learn/pull/259)
-- [**enhancement**] Various Updates [#237](https://github.com/matcornic/hugo-theme-learn/pull/237)
-- [**enhancement**] Use style instead of width and height in logo [#250](https://github.com/matcornic/hugo-theme-learn/pull/250)
-- [**enhancement**] [ImgBot] Optimize images [#222](https://github.com/matcornic/hugo-theme-learn/pull/222)
-- [**enhancement**] remove duplicate icon and fix incorrect favicon type [#227](https://github.com/matcornic/hugo-theme-learn/pull/227)
-- [**enhancement**] HTTPS links in exampleSite menu-footer [#223](https://github.com/matcornic/hugo-theme-learn/pull/223)
-
-#### Internationalisation
-
-- [**i18n**] Dutch i18n [#239](https://github.com/matcornic/hugo-theme-learn/pull/239)
-
-#### Theme Meta
-
-- [**meta**] Add .editorconfig [#224](https://github.com/matcornic/hugo-theme-learn/pull/224)
-
----
-
-## v2.2.0 (28/01/2019)
-
-#### New features
-
-- [**feature**] Sitewide param to enable or disable next/previous page buttons and breadcrumbs [#184](https://github.com/matcornic/hugo-theme-learn/pull/184)
-
-#### Bug Fixes
-
-- [**bug**] Fix baseurl used by search to load json data [#177](https://github.com/matcornic/hugo-theme-learn/pull/177)
-- [**bug**] Updated CSS link to fontawesome library [#186](https://github.com/matcornic/hugo-theme-learn/pull/186)
-- [**bug**] Close / Cancel search icon not showing in input box [#215](https://github.com/matcornic/hugo-theme-learn/pull/215)
-- [**bug**] Prevent left and right keydown events while in input fields [#219](https://github.com/matcornic/hugo-theme-learn/pull/219)
-- [**bug**] xss fix [#182](https://github.com/matcornic/hugo-theme-learn/pull/182)
-- [**bug**] Fix error in blockquote documentation fixes #165 [#190](https://github.com/matcornic/hugo-theme-learn/pull/190)
-
-#### Enhancements
-
-- [**enhancement**] Update mermaid.js to a499296 [#199](https://github.com/matcornic/hugo-theme-learn/pull/199)
-- [**enhancement**] Update Font Awesome to 5.0.6 [#129](https://github.com/matcornic/hugo-theme-learn/pull/129)
-- [**enhancement**] Update 404.html alttext [#161](https://github.com/matcornic/hugo-theme-learn/pull/161)
-- [**enhancement**] Remove CSS source map metadata [#167](https://github.com/matcornic/hugo-theme-learn/pull/167)
-- [**enhancement**] Load github images in examplesite via https instead of http [#180](https://github.com/matcornic/hugo-theme-learn/pull/180)
-- [**enhancement**] Load main site logo via BaseUrl [#185](https://github.com/matcornic/hugo-theme-learn/pull/185)
-- [**enhancement**] HTTPS links in examplesite sidebar [#200](https://github.com/matcornic/hugo-theme-learn/pull/200)
-- [**enhancement**] Use correct input type for search [#205](https://github.com/matcornic/hugo-theme-learn/pull/205)
-- [**enhancement**] HTTPS link to learn.getgrav.org [#207](https://github.com/matcornic/hugo-theme-learn/pull/207)
-- [**enhancement**] Update html5shiv-printshiv.min.js [#208](https://github.com/matcornic/hugo-theme-learn/pull/208)
-- [**enhancement**] Remove whitespace from clippy.svg [#211](https://github.com/matcornic/hugo-theme-learn/pull/211)
-- [**enhancement**] Upgrade fontawesome to 5.6.3 [#218](https://github.com/matcornic/hugo-theme-learn/pull/218)
-- [**enhancement**] fix clickable nodes style in mermaid [#169](https://github.com/matcornic/hugo-theme-learn/pull/169)
-
-#### Internationalisation
-
-- [**i18n**] French language correction [#157](https://github.com/matcornic/hugo-theme-learn/pull/157)
-- [**i18n**] French language correction [#158](https://github.com/matcornic/hugo-theme-learn/pull/158)
-- [**i18n**] Add indonesian translation [#159](https://github.com/matcornic/hugo-theme-learn/pull/159)
-- [**i18n**] Add Turkish i18n config file [#175](https://github.com/matcornic/hugo-theme-learn/pull/175)
-
-#### Theme Meta
-
-- [**meta**] Fix wercker builds [#178](https://github.com/matcornic/hugo-theme-learn/pull/178)
-- [**meta**] Declare netlify buildsteps in repo file rather than in webui [#217](https://github.com/matcornic/hugo-theme-learn/pull/217)
-
----
-
-## v2.1.0 (10/08/2018)
-
-#### Internationalisation
-
-- [**i18n**] Clean up the English language phrasing [#146](https://github.com/matcornic/hugo-theme-learn/pull/146)
-- [**i18n**] Updated _index.en.md for typo "names" [#150](https://github.com/matcornic/hugo-theme-learn/pull/150)
-
-#### Theme Meta
-
-- [**meta**] Add license scan report and status [#151](https://github.com/matcornic/hugo-theme-learn/pull/151)
-
-#### Uncategorised
-
-- [**closed**] Different viewport [#122](https://github.com/matcornic/hugo-theme-learn/pull/122)
-- [**closed**] TranslationBaseName replaced for Name on archetypes template [#145](https://github.com/matcornic/hugo-theme-learn/pull/145)
-- [**closed**] Improved variant of #119, as per request [#124](https://github.com/matcornic/hugo-theme-learn/pull/124)
-- [**closed**] role="" is invalid [#121](https://github.com/matcornic/hugo-theme-learn/pull/121)
-- [**closed**] Related to previous PR [#120](https://github.com/matcornic/hugo-theme-learn/pull/120)
-- [**closed**] Issue #111 for _index.fr.md [#117](https://github.com/matcornic/hugo-theme-learn/pull/117)
-- [**closed**] Issue #111 for _index.en.md [#116](https://github.com/matcornic/hugo-theme-learn/pull/116)
-- [**closed**] Issue #111 for theme-green.css [#114](https://github.com/matcornic/hugo-theme-learn/pull/114)
-- [**closed**] Issue #111 for theme-red.css [#113](https://github.com/matcornic/hugo-theme-learn/pull/113)
-- [**closed**] Issue #111 for theme-blue.css [#112](https://github.com/matcornic/hugo-theme-learn/pull/112)
-- [**closed**] Issue #111 for theme-mine.css [#115](https://github.com/matcornic/hugo-theme-learn/pull/115)
-- [**closed**] fix #77 : no wrap images that already wrapped [#118](https://github.com/matcornic/hugo-theme-learn/pull/118)
-- [**closed**] doc: Keep icons aligned [#110](https://github.com/matcornic/hugo-theme-learn/pull/110)
-- [**closed**] Add Portuguese translation [#109](https://github.com/matcornic/hugo-theme-learn/pull/109)
-- [**closed**] Use `relURL` where possible [#102](https://github.com/matcornic/hugo-theme-learn/pull/102)
-- [**closed**] Bug fix in sidebar menu and children description generation [#105](https://github.com/matcornic/hugo-theme-learn/pull/105)
-- [**closed**] fix some typo [#104](https://github.com/matcornic/hugo-theme-learn/pull/104)
-- [**closed**] Added a `menuTitle` attribute to partials/menu.html [#90](https://github.com/matcornic/hugo-theme-learn/pull/90)
-- [**closed**] allowing comments system [#86](https://github.com/matcornic/hugo-theme-learn/pull/86)
-- [**closed**] Add spanish translation [#85](https://github.com/matcornic/hugo-theme-learn/pull/85)
-- [**closed**] Replace horsey with Pixabay's autocomplete [#75](https://github.com/matcornic/hugo-theme-learn/pull/75)
-- [**closed**] Added info about 'draft:true' [#74](https://github.com/matcornic/hugo-theme-learn/pull/74)
-- [**closed**] Remove white space from `align` parameter [#63](https://github.com/matcornic/hugo-theme-learn/pull/63)
-
----
-
-## v2.0.0 (20/08/2017)
-
-#### Uncategorised
-
-- [**closed**] V2 [#56](https://github.com/matcornic/hugo-theme-learn/pull/56)
-
----
-
-## v1.1.0 (22/07/2017)
-
-#### Bug Fixes
-
-- [**bug**] Fix sticky header jumpiness [#45](https://github.com/matcornic/hugo-theme-learn/pull/45)
-
-#### Uncategorised
-
-- [**closed**] Fix anchor scrolling that hides behind top nav bar [#46](https://github.com/matcornic/hugo-theme-learn/pull/46)
-- [**closed**] feat: Change the default code color [#43](https://github.com/matcornic/hugo-theme-learn/pull/43)
-- [**closed**] Use index pages + automatic navigation arrows [#36](https://github.com/matcornic/hugo-theme-learn/pull/36)
-
----
-
-## v1.0.0 (25/03/2017)
-
-#### Uncategorised
-
-- [**closed**] Search [#18](https://github.com/matcornic/hugo-theme-learn/pull/18)
-- [**closed**] Extracted menu footer content to separate partial file [#35](https://github.com/matcornic/hugo-theme-learn/pull/35)
-- [**closed**] feat: style Hugo figure shortcode [#33](https://github.com/matcornic/hugo-theme-learn/pull/33)
-- [**closed**] Fix URL for 'Edit this page' on Windows [#27](https://github.com/matcornic/hugo-theme-learn/pull/27)
-- [**closed**] Revert "Menu generation using Content file instead directories" [#10](https://github.com/matcornic/hugo-theme-learn/pull/10)
-- [**closed**] (#25) use .Site.BaseURL to lcoate static assets [#26](https://github.com/matcornic/hugo-theme-learn/pull/26)
-- [**closed**] Menu ordering and definition in config.toml [#8](https://github.com/matcornic/hugo-theme-learn/pull/8)
-- [**closed**] Menu generation using Content file instead directories [#5](https://github.com/matcornic/hugo-theme-learn/pull/5)
-- [**closed**] Add Checkmark On visited Links [#4](https://github.com/matcornic/hugo-theme-learn/pull/4)
-- [**closed**] doc: Add theme installation instructions [#1](https://github.com/matcornic/hugo-theme-learn/pull/1)
diff --git a/documentation/staging/themes/learn/LICENSE.md b/documentation/staging/themes/learn/LICENSE.md
deleted file mode 100644
index 0cf9fcb49..000000000
--- a/documentation/staging/themes/learn/LICENSE.md
+++ /dev/null
@@ -1,22 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2014 Grav
-Copyright (c) 2016 MATHIEU CORNIC
-Copyright (c) 2017 Valere JEANTET
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/documentation/staging/themes/learn/README.md b/documentation/staging/themes/learn/README.md
deleted file mode 100644
index 3e0801e9c..000000000
--- a/documentation/staging/themes/learn/README.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# Hugo Learn Theme
-
-This repository contains a theme for [Hugo](https://gohugo.io/), based on great [Grav Learn Theme](https://learn.getgrav.org/).
-
-Visit the [theme documentation](https://learn.netlify.com/en/) to see what is going on. It is actually built with this theme.
-
-[](https://app.wercker.com/project/byKey/233466a2be73fcea400e7dc02ef6adf9)
-[](https://app.fossa.io/projects/git%2Bgithub.com%2Fmatcornic%2Fhugo-theme-learn?ref=badge_shield)
-
-## Main features
-
-- Automatic Search
-- Multilingual mode
-- Unlimited menu levels
-- Automatic next/prev buttons to navigate through menu entries
-- Image resizing, shadow…
-- Attachments files
-- List child pages
-- Mermaid diagram (flowchart, sequence, gantt)
-- Customizable look and feel and themes variants
-- Buttons, Tip/Note/Info/Warning boxes, Expand
-
-## Installation
-
-Navigate to your themes folder in your Hugo site and use the following commands:
-
-```shell
-cd themes/
-git clone https://github.com/matcornic/hugo-theme-learn.git
-```
-
-Check that your Hugo version is minimum `0.25` with `hugo version`.
-
-
-
-## Usage
-
-- [Visit the documentation](https://learn.netlify.com/en/)
-
-## Download old versions (prior to 2.0.0)
-
-If you need old version for compatibility purpose, either download [theme source code from releases](https://github.com/matcornic/hugo-theme-learn/releases) or use the right git tag. For example, with `1.1.0`
-
-- Direct download way: https://github.com/matcornic/hugo-theme-learn/archive/1.1.0.zip
-- Git way:
-
-```shell
-cd themes/hugo-theme-learn
-git checkout tags/1.1.0
-```
-
-For both solutions, the documentation is available at https://github.com/matcornic/hugo-theme-learn/releases/download/1.1.0/hugo-learn-doc-1.1.0.zip
-
-## Credits
-
-Many thanks to [@vjeantet](https://github.com/vjeantet/) for the fork [docdock](https://github.com/vjeantet/hugo-theme-docdock). The v2 of this theme is mainly based on his work !
-
-## License
-
-[](https://app.fossa.io/projects/git%2Bgithub.com%2Fmatcornic%2Fhugo-theme-learn?ref=badge_large)
-
-## Releasing
-
-Somewhat work-in-progress steps to release with [gren](https://github.com/github-tools/github-release-notes)
-
-- Check all MRs assigned to the milestone are closed or pushed back to another release
-- Close the milestone
-- Check merged MRs on the milestone have a tag (Bug, Enhancement, etc.)
-- Tag and push the repo
-
- ```shell
- git tag
- git push origin
- ```
-
-- Generate CHANGELOG.md with _gren_
-
- ```shell
- gren changelog --override --generate --tags=all
- ```
-
-- Fix the date for the current release in CHANGELOG.md
-- Add the changelog to git and update the tag
-
- ```shell
- git add CHANGELOG.md
- git commit -m "Ship tag "
- git push origin master
- git tag -f
- git push --force origin
- ```
-
-- Generate release with _gren_
-
- ```shell
- gren release -t
- ```
diff --git a/documentation/staging/themes/learn/archetypes/chapter.md b/documentation/staging/themes/learn/archetypes/chapter.md
deleted file mode 100644
index a29ba1bd4..000000000
--- a/documentation/staging/themes/learn/archetypes/chapter.md
+++ /dev/null
@@ -1,13 +0,0 @@
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-chapter = true
-pre = "X. "
-+++
-
-### Chapter X
-
-# Some Chapter title
-
-Lorem Ipsum.
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/archetypes/default.md b/documentation/staging/themes/learn/archetypes/default.md
deleted file mode 100644
index 5124e2a77..000000000
--- a/documentation/staging/themes/learn/archetypes/default.md
+++ /dev/null
@@ -1,7 +0,0 @@
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-+++
-
-Lorem Ipsum.
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/LICENSE.md b/documentation/staging/themes/learn/exampleSite/LICENSE.md
deleted file mode 100644
index 973626de8..000000000
--- a/documentation/staging/themes/learn/exampleSite/LICENSE.md
+++ /dev/null
@@ -1,20 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2016 MATHIEU CORNIC
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/documentation/staging/themes/learn/exampleSite/config.toml b/documentation/staging/themes/learn/exampleSite/config.toml
deleted file mode 100644
index c1381da47..000000000
--- a/documentation/staging/themes/learn/exampleSite/config.toml
+++ /dev/null
@@ -1,112 +0,0 @@
-baseURL = "/"
-languageCode = "en-US"
-defaultContentLanguage = "en"
-
-title = "Hugo Learn Documentation"
-theme = "hugo-theme-learn"
-themesdir = "../.."
-metaDataFormat = "yaml"
-defaultContentLanguageInSubdir= true
-
-[params]
- editURL = "https://github.com/matcornic/hugo-theme-learn/edit/master/exampleSite/content/"
- description = "Documentation for Hugo Learn Theme"
- author = "Mathieu Cornic"
- showVisitedLinks = true
- disableBreadcrumb = false
- disableNextPrev = false
- disableLandingPageButton = true
- disableMermaid = false
- customMermaidURL = "https://unpkg.com/mermaid@8.8.0/dist/mermaid.min.js"
- titleSeparator = "::"
-
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-
-[Languages]
-[Languages.en]
-title = "Documentation for Hugo Learn Theme"
-weight = 1
-languageName = "English"
-landingPageURL = "/en"
-landingPageName = " Home"
-
-[[Languages.en.menu.shortcuts]]
-name = " GitHub repo"
-identifier = "ds"
-url = "https://github.com/matcornic/hugo-theme-learn"
-weight = 10
-
-[[Languages.en.menu.shortcuts]]
-name = " Showcases"
-url = "showcase"
-weight = 11
-
-[[Languages.en.menu.shortcuts]]
-name = " Hugo Documentation"
-identifier = "hugodoc"
-url = "https://gohugo.io/"
-weight = 20
-
-[[Languages.en.menu.shortcuts]]
-name = " Credits"
-url = "/credits"
-weight = 30
-
-[Languages.fr]
-title = "Documentation du thème Hugo Learn"
-weight = 2
-languageName = "Français"
-landingPageURL = "/fr"
-landingPageName = " Accueil"
-
-[[Languages.fr.menu.shortcuts]]
-name = " Repo GitHub"
-identifier = "ds"
-url = "https://github.com/matcornic/hugo-theme-learn"
-weight = 10
-
-[[Languages.fr.menu.shortcuts]]
-name = " Vitrine"
-url = "/showcase"
-weight = 11
-
-[[Languages.fr.menu.shortcuts]]
-name = " Documentation Hugo"
-identifier = "hugodoc"
-url = "https://gohugo.io/"
-weight = 20
-
-[[Languages.fr.menu.shortcuts]]
-name = " Crédits"
-url = "/credits"
-weight = 30
-
-[Languages.zh]
-title = "Hugo 主题的 Learn 文档"
-weight = 3
-languageName = "简体中文"
-landingPageURL = "/zh"
-landingPageName = " 家"
-
-[[Languages.zh.menu.shortcuts]]
-name = " GitHub 仓库"
-identifier = "ds"
-url = "https://github.com/matcornic/hugo-theme-learn"
-weight = 10
-
-[[Languages.zh.menu.shortcuts]]
-name = " 展示区"
-url = "/showcase"
-weight = 11
-
-[[Languages.zh.menu.shortcuts]]
-name = " Hugo 文档"
-identifier = "hugodoc"
-url = "https://gohugo.io/"
-weight = 20
-
-[[Languages.zh.menu.shortcuts]]
-name = " 鸣谢"
-url = "/credits"
-weight = 30
diff --git a/documentation/staging/themes/learn/exampleSite/content/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/_index.en.md
deleted file mode 100644
index a36357957..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/_index.en.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: "Learn Theme for Hugo"
----
-
-# Hugo learn theme
-
-[Hugo-theme-learn](http://github.com/matcornic/hugo-theme-learn) is a theme for [Hugo](https://gohugo.io/), a fast and modern static website engine written in Go. Where Hugo is often used for blogs, this multilingual-ready theme is **fully designed for documentation**.
-
-This theme is a partial porting of the [Learn theme](http://learn.getgrav.org/) of [Grav](https://getgrav.org/), a modern flat-file CMS written in PHP.
-
-{{% notice tip %}}Learn theme works with a _page tree structure_ to organize content : All contents are pages, which belong to other pages. [read more about this]({{%relref "cont/pages/_index.md"%}})
-{{% /notice %}}
-
-## Main features
-
-* [Automatic Search]({{%relref "basics/configuration/_index.md#activate-search" %}})
-* [Multilingual mode]({{%relref "cont/i18n/_index.md" %}})
-* **Unlimited menu levels**
-* **Automatic next/prev buttons to navigate through menu entries**
-* [Image resizing, shadow...]({{%relref "cont/markdown.en.md#images" %}})
-* [Attachments files]({{%relref "shortcodes/attachments.en.md" %}})
-* [List child pages]({{%relref "shortcodes/children/_index.md" %}})
-* [Mermaid diagram]({{%relref "shortcodes/mermaid.en.md" %}}) (flowchart, sequence, gantt)
-* [Customizable look and feel and themes variants]({{%relref "basics/style-customization/_index.md"%}})
-* [Buttons]({{%relref "shortcodes/button.en.md" %}}), [Tip/Note/Info/Warning boxes]({{%relref "shortcodes/notice.en.md" %}}), [Expand]({{%relref "shortcodes/expand.en.md" %}})
-
-
-
-## Contribute to this documentation
-Feel free to update this content, just click the **Edit this page** link displayed on top right of each page, and pullrequest it
-
-{{% notice info %}}
-Your modification will be deployed automatically when merged.
-{{% /notice %}}
-
-## Documentation website
-This current documentation has been statically generated with Hugo with a simple command : `hugo -t hugo-theme-learn` -- source code is [available here at GitHub](https://github.com/matcornic/hugo-theme-learn)
-
-{{% notice note %}}
-Automatically published and hosted thanks to [Netlify](https://www.netlify.com/). Read more about [Automated HUGO deployments with Netlify](https://www.netlify.com/blog/2015/07/30/hosting-hugo-on-netlifyinsanely-fast-deploys/)
-{{% /notice %}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/_index.fr.md
deleted file mode 100644
index 40b2dc352..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/_index.fr.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: "Learn Theme for Hugo"
----
-
-# Thème Hugo learn
-
-[Hugo-theme-learn](http://github.com/matcornic/hugo-theme-learn) est un thème pour [Hugo](https://gohugo.io/), un générateur de site statique, rapide et modern, écrit en Go. Tandis que Hugo est souvent utilisé pour des blogs, ce thème multi-langue est **entièrement conçu pour la documentation**.
-
-Ce thème est un portage partiel du [thème Learn](http://learn.getgrav.org/) de [Grav](https://getgrav.org/), un CMS modern écrit en PHP.
-
-{{% notice tip %}}Le thème Learn fonctionne grâce à la structure de page aborescentes pour organiser le contenu: tous les contenus sont des pages qui appartiennent à d'autres pages. [Plus d'infos]({{%relref "cont/pages/_index.md"%}})
-{{% /notice %}}
-
-## Fonctionnalités principales
-
-* [Recherche automatique]({{%relref "basics/configuration/_index.md#activer-recherche" %}})
-* [Mode multi-langue]({{%relref "cont/i18n/_index.md" %}})
-* **Nombre de niveau infini dans le menu**
-* **Boutons suivant/précédent automatiquement générés pour naviguer entre les items du menu**
-* [Taille d'image, ombres...]({{%relref "cont/markdown.fr.md#images" %}})
-* [Fichiers joints]({{%relref "shortcodes/attachments.fr.md" %}})
-* [Lister les pages filles]({{%relref "shortcodes/children/_index.md" %}})
-* [Diagrammes Mermaid]({{%relref "shortcodes/mermaid.fr.md" %}}) (flowchart, sequence, gantt)
-* [Style configurable and variantes de couleurs]({{%relref "basics/style-customization/_index.md"%}})
-* [Boutons]({{%relref "shortcodes/button.fr.md" %}}), [Messages Astuce/Note/Info/Attention]({{%relref "shortcodes/notice.fr.md" %}}), [Expand]({{%relref "shortcodes/expand.fr.md" %}})
-
-
-
-## Contribuer à cette documentation
-
-N'hésitez pas à mettre à jour ce contenu en cliquant sur le lien **Modifier cette page** en haut de chaque page, et créer la Pull Request associée.
-
-{{% notice info %}}
-Votre modification sera déployée automatiquement quand elle sera mergée.
-{{% /notice %}}
-
-## Site de documentation
-
-Cette documentation statique a été générée avec Hugo avec une simple commande : `hugo -t hugo-theme-learn` -- le code source est [disponible sur Github](https://github.com/matcornic/hugo-theme-learn)
-
-{{% notice note %}}
-Le site est auomatiquement publié et hébergé par [Netlify](https://www.netlify.com/). Plus d'infos sur le [déploiement de site Hugo avec Netlify](https://www.netlify.com/blog/2015/07/30/hosting-hugo-on-netlifyinsanely-fast-deploys/)(En anglais)
-{{% /notice %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/basics/_index.en.md
deleted file mode 100644
index 56e2968e2..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/_index.en.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Basics
-weight: 5
-pre: "1. "
-chapter: true
----
-
-### Chapter 1
-
-# Basics
-
-Discover what this Hugo theme is all about and the core-concepts behind it.
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/basics/_index.fr.md
deleted file mode 100644
index 1b800c905..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/_index.fr.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Démarrage
-weight: 5
-pre: "1. "
-chapter: true
----
-
-### Chapitre 1
-
-# Démarrage
-
-Découvrez comment utiliser ce thème Hugo et apprenez-en les concepts
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/_index.zh.md b/documentation/staging/themes/learn/exampleSite/content/basics/_index.zh.md
deleted file mode 100644
index 6c5d5dacc..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/_index.zh.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 基础
-weight: 5
-pre: "1. "
-chapter: true
----
-
-### 章节 1
-
-# 基础
-
-了解该 Hugo 主题的特点以及背后的核心概念。
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.en.md
deleted file mode 100644
index c46212524..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.en.md
+++ /dev/null
@@ -1,112 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Configuration
-weight: 20
----
-
-## Global site parameters
-
-On top of [Hugo global configuration](https://gohugo.io/overview/configuration/), **Hugo-theme-learn** lets you define the following parameters in your `config.toml` (here, values are default).
-
-Note that some of these parameters are explained in details in other sections of this documentation.
-
-```toml
-[params]
- # Prefix URL to edit current page. Will display an "Edit this page" button on top right hand corner of every page.
- # Useful to give opportunity to people to create merge request for your doc.
- # See the config.toml file from this documentation site to have an example.
- editURL = ""
- # Author of the site, will be used in meta information
- author = ""
- # Description of the site, will be used in meta information
- description = ""
- # Shows a checkmark for visited pages on the menu
- showVisitedLinks = false
- # Disable search function. It will hide search bar
- disableSearch = false
- # Javascript and CSS cache are automatically busted when new version of site is generated.
- # Set this to true to disable this behavior (some proxies don't handle well this optimization)
- disableAssetsBusting = false
- # Set this to true to disable copy-to-clipboard button for inline code.
- disableInlineCopyToClipBoard = false
- # A title for shortcuts in menu is set by default. Set this to true to disable it.
- disableShortcutsTitle = false
- # If set to false, a Home button will appear below the search bar on the menu.
- # It is redirecting to the landing page of the current language if specified. (Default is "/")
- disableLandingPageButton = true
- # When using mulitlingual website, disable the switch language button.
- disableLanguageSwitchingButton = false
- # Hide breadcrumbs in the header and only show the current page title
- disableBreadcrumb = true
- # If set to true, prevents Hugo from including the mermaid module if not needed (will reduce load times and traffic)
- disableMermaid = false
- # Specifies the remote location of the mermaid js
- customMermaidURL = "https://unpkg.com/mermaid@8.8.0/dist/mermaid.min.js"
- # Hide Next and Previous page buttons normally displayed full height beside content
- disableNextPrev = true
- # Order sections in menu by "weight" or "title". Default to "weight"
- ordersectionsby = "weight"
- # Change default color scheme with a variant one. Can be "red", "blue", "green".
- themeVariant = ""
- # Provide a list of custom css files to load relative from the `static/` folder in the site root.
- custom_css = ["css/foo.css", "css/bar.css"]
- # Change the title separator. Default to "::".
- titleSeparator = "-"
-```
-
-## Activate search
-
-If not already present, add the follow lines in the same `config.toml` file.
-
-```toml
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-```
-
-Learn theme uses the last improvement available in hugo version 20+ to generate a json index file ready to be consumed by lunr.js javascript search engine.
-
-> Hugo generate lunrjs index.json at the root of public folder.
-> When you build the site with `hugo server`, hugo generates it internally and of course it doesn’t show up in the filesystem
-
-## Mermaid
-
-The mermaid configuration parameters can also be set on a specific page. In this case, the global parameter would be overwritten by the local one.
-
-> Example:
->
-> Mermaid is globally disabled. By default it won't be loaded by any page.
-> On page "Architecture" you need a class diagram. You can set the mermaid parameters locally to only load mermaid on this page (not on the others).
-
-You also can disable mermaid for specific pages while globally enabled.
-
-## Home Button Configuration
-
-If the `disableLandingPage` option is set to `false`, an Home button will appear
-on the left menu. It is an alternative for clicking on the logo. To edit the
-appearance, you will have to configure two parameters for the defined languages:
-
-```toml
-[Lanugages]
-[Lanugages.en]
-...
-landingPageURL = "/en"
-landingPageName = " Redirect to Home"
-...
-[Lanugages.fr]
-...
-landingPageURL = "/fr"
-landingPageName = " Accueil"
-...
-```
-
-If those params are not configured for a specific language, they will get their
-default values:
-
-```toml
-landingPageURL = "/"
-landingPageName = " Home"
-```
-
-The home button is going to looks like this:
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.fr.md
deleted file mode 100644
index 72e496da7..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/_index.fr.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Configuration
-weight: 20
----
-
-## Paramètres globaux du site
-
-En plus de la [configuration globale d'Hugo](https://gohugo.io/overview/configuration/), **Hugo-theme-learn** vous permet de définir les paramètres suivant dans votre fichier `config.toml` (ci-dessous sont affichées les valeurs par défaut).
-
-Notez que certains de ces paramètres sont expliqués en détails dans d'autres sections de cette documentation.
-
-```toml
-[params]
- # L'URL préfixe pour éditer la page courante. Ce paramètre affichera un bouton "Modifier cette page" on haut de de chacune des pages.
- # Pratique pour donner les possibilité à vos utilisateurs de créer une merge request pour votre doc.
- # Allez voir le fichier config.toml de cette documentation pour avoir un exemple.
- editURL = ""
- # Autheur du site, est utilisé dans les informations meta
- author = ""
- # Description du site, est utilisé dans les informations meta
- description = ""
- # Affiche une icône lorsque la page a été visitée
- showVisitedLinks = false
- # Désactive la fonction de recherche. Une valeur à true cache la barre de recherche.
- disableSearch = false
- # Par défaut, le cache Javascript et CSS est automatiquement vidé lorsqu'une nouvelle version du site est générée.
- # Utilisez ce paramètre lorsque vous voulez désactiver ce comportement (c'est parfois incompatible avec certains proxys)
- disableAssetsBusting = false
- # Utilisez ce paramètre pour désactiver le bouton copy-to-clipboard pour le code formatté sur une ligne.
- disableInlineCopyToClipBoard = false
- # Un titre est défini par défaut lorsque vous utilisez un raccourci dans le menu. Utilisez ce paramètre pour le cacher.
- disableShortcutsTitle = false
- # S'il est réglé sur faux, un bouton Accueil apparaîtra sous la barre de recherche dans le menu.
- # Il redirige vers la page d'accueil de la langue actuelle si cela est spécifié. (La valeur par défaut est "/")
- disableLandingPageButton = true
- # Si défini à true, empêche Hugo d'inclure le module "mermaid" s'il n'est pas nécessaire (réduira les temps de chargement et le trafic)
- disableMermaid = false
- # Spécifie l'emplacement distant du mermaid js
- customMermaidURL = "https://unpkg.com/mermaid@8.8.0/dist/mermaid.min.js"
- # Quand vous utilisez un site multi-langue, utilisez ce paramètre pour désactiver le bouton de changement de langue.
- disableLanguageSwitchingButton = false
- # Ordonne les sections dans menu par poids ("weight") ou titre ("title"). Défaut à "weight"
- ordersectionsby = "weight"
- # Utilisez ce paramètre pour modifier le schéma de couleur du site. Les valeurs par défaut sont "red", "blue", "green".
- themeVariant = ""
- # Fournissez une liste de fichiers css personnalisés à charger par rapport depuis le dossier `static/` à la racine du site.
- custom_css = ["css/foo.css", "css/bar.css"]
-```
-
-## Activer la recherche {#activer-recherche}
-
-Si ce n'est pas déjà présent, ajoutez les lignes suivantes dans le fichier `config.toml`.
-
-```toml
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-```
-
-Le thème *Learn* utilise les dernières améliorations d'Hugo pour générer un fichier d'index JSON, prêt à être consommé par le moteur de recherche lunr.js.
-
-> Hugo génère lunrjs index.json à la racine du dossier `public`.
-> Quand vous générez le site avec `hugo server`, Hugo génère le fichier en mémoire, il n'est donc pas disponible sur le disque.
-
-## Mermaid
-
-Les paramètres de configuration du mermaid peuvent également être définis sur une page spécifique. Dans ce cas, le paramètre global sera écrasé par le paramètre local.
-
-> Exemple:
->
-> Mermaid est globalement handicapé. Par défaut, elle ne sera chargée par aucune page.
-> À la page "Architecture", vous avez besoin d'un diagramme de classe. Vous pouvez régler les paramètres de mermaid localement pour ne charger que la sirène sur cette page (pas sur les autres).
-
-Vous pouvez également désactiver mermaid pour des pages spécifiques tout en l'activant globalement.
-<<<<<<< HEAD
-
-## Configuration du bouton Accueil
-
-Si l'option `disableLandingPage` est définie sur `false`, un bouton
-"Accueil" apparaîtra dans le menu de gauche. C'est une alternative pour cliquer
-sur le logo. Pour modifier le vous devrez configurer deux paramètres pour les
-langues définies :
-
-```toml
-[Lanugages]
-[Lanugages.en]
-...
-landingPageURL = "/en"
-landingPageName = " Redirect to Home"
-...
-[Lanugages.fr]
-...
-landingPageURL = "/fr"
-landingPageName = " Accueil"
-...
-```
-
-Si ces paramètres ne sont pas configurés pour une langue spécifique, ils
-obtiendront leur valeurs par défaut:
-
-```toml
-landingPageURL = "/"
-landingPageName = " Home"
-```
-
-Le bouton d'accueil va ressembler à ceci:
-
-
-=======
->>>>>>> 023fe7ef2b4c45fe66ac932d9e25d09f30b74a4e
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg b/documentation/staging/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg
deleted file mode 100644
index 84b045d00..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/configuration/images/home_button_defaults.jpg and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.en.md
deleted file mode 100644
index e53d006c7..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.en.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Installation
-weight: 15
----
-
-The following steps are here to help you initialize your new website. If you don't know Hugo at all, we strongly suggest you learn more about it by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
-
-## Create your project
-
-Hugo provides a `new` command to create a new website.
-
-```
-hugo new site
-```
-
-## Install the theme
-
-Install the **Hugo-theme-learn** theme by following [this documentation](https://gohugo.io/getting-started/quick-start/#step-3-add-a-theme)
-
-This theme's repository is: https://github.com/matcornic/hugo-theme-learn.git
-
-Alternatively, you can [download the theme as .zip](https://github.com/matcornic/hugo-theme-learn/archive/master.zip) file and extract it in the `themes` directory
-
-## Basic configuration
-
-When building the website, you can set a theme by using `--theme` option. However, we suggest you modify the configuration file (`config.toml`) and set the theme as the default. You can also add the `[outputs]` section to enable the search functionality.
-
-```toml
-# Change the default theme to be use when building the site with Hugo
-theme = "hugo-theme-learn"
-
-# For search functionality
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-```
-
-## Create your first chapter page
-
-Chapters are pages that contain other child pages. It has a special layout style and usually just contains a _chapter name_, the _title_ and a _brief abstract_ of the section.
-
-```
-### Chapter 1
-
-# Basics
-
-Discover what this Hugo theme is all about and the core concepts behind it.
-```
-
-renders as
-
-
-
-**Hugo-theme-learn** provides archetypes to create skeletons for your website. Begin by creating your first chapter page with the following command
-
-```
-hugo new --kind chapter basics/_index.md
-```
-
-By opening the given file, you should see the property `chapter=true` on top, meaning this page is a _chapter_.
-
-By default all chapters and pages are created as a draft. If you want to render these pages, remove the property `draft: true` from the metadata.
-
-## Create your first content pages
-
-Then, create content pages inside the previously created chapter. Here are two ways to create content in the chapter:
-
-```
-hugo new basics/first-content.md
-hugo new basics/second-content/_index.md
-```
-
-Feel free to edit thoses files by adding some sample content and replacing the `title` value in the beginning of the files.
-
-## Launching the website locally
-
-Launch by using the following command:
-
-```
-hugo serve
-```
-
-Go to `http://localhost:1313`
-
-You should notice three things:
-
-1. You have a left-side **Basics** menu, containing two submenus with names equal to the `title` properties in the previously created files.
-2. The home page explains how to customize it by following the instructions.
-3. When you run `hugo serve`, when the contents of the files change, the page automatically refreshes with the changes. Neat!
-
-## Build the website
-
-When your site is ready to deploy, run the following command:
-
-```
-hugo
-```
-
-A `public` folder will be generated, containing all static content and assets for your website. It can now be deployed on any web server.
-
-{{% notice note %}}
-This website can be automatically published and hosted with [Netlify](https://www.netlify.com/) (Read more about [Automated HUGO deployments with Netlify](https://www.netlify.com/blog/2015/07/30/hosting-hugo-on-netlifyinsanely-fast-deploys/)). Alternatively, you can use [Github pages](https://gohugo.io/hosting-and-deployment/hosting-on-github/)
-{{% /notice %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.fr.md
deleted file mode 100644
index 268d0c3ce..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/installation/_index.fr.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: Installation
-weight: 15
----
-
-Les étapes suivantes sont là pour vous aider à initialiser votre site. Si vous ne connaissez pas du tout Hugo, il est fortement conseillé de vous entrainer en suivant ce [super tuto pour débutants](https://gohugo.io/overview/quickstart/).
-
-## Créer votre projet
-
-Hugo fournit une commande `new` pour créer un nouveau site.
-
-```
-hugo new site
-```
-
-## Installer le thème
-
-Installer le thème **Hugo-theme-learn** en suivant [cette documentation](https://gohugo.io/themes/installing/)
-
-Le repo du thème est : https://github.com/matcornic/hugo-theme-learn.git
-
-Sinon, vous pouvez [télécharger le thème sous forme d'un fichier .zip](https://github.com/matcornic/hugo-theme-learn/archive/master.zip) et extrayez le dans votre dossier de thèmes.
-
-## Configuration simple
-
-Lorsque vous générez votre site, vous pouvez définir un thème en utilisant l'option `--theme`. Il est conseillé de modifier votre fichier de configuration `config.toml` and définir votre thème par défaut. En passant, ajoutez les prérequis à l'utilisation de la fonctionnalité de recherche.
-
-```toml
-# Modifiez le thème pour qu'il soit utilisé par défaut à chaque génération de site.
-theme = "hugo-theme-learn"
-
-# Pour la fonctionnalité de recherche
-[outputs]
-home = [ "HTML", "RSS", "JSON"]
-```
-
-## Créer votre première page chapitre
-
-Les *chapitres* sont des pages contenant d'autre pages filles. Elles ont un affichage spécial et contiennent habituellement juste un _nom_ de chapitre, le _titre_ et un _résumé_ de la section.
-
-```
-### Chapitre 1
-
-# Démarrage
-
-Découvrez comment utiliser ce thème Hugo et apprenez en les concepts
-```
-
-s'affiche comme
-
-
-
-**Hugo-theme-learn** fournit des archétypes pour créer des squelettes pour votre site. Commencez par créer votre premier chapitre avec la commande suivante:
-
-```
-hugo new --kind chapter basics/_index.md
-```
-
-En ouvrant le fichier généré, vous devriez voir la propriété `chapter=true` en haut, paramètre quit définit que le page est un _chapitre_.
-
-## Créer votre première page
-
-Puis, créez votre premier page dans le chapitre précédent. Pour ce faire, il existe deux possibilités :
-
-```
-hugo new basics/first-content.md
-hugo new basics/second-content/_index.md
-```
-
-N'hésitez pas à éditer ces fichiers en ajoutant des exemple de contenu et en remplaçant le paramètre `title` au début du fichier.
-
-## Lancer le site localement
-
-Lancez la commande suivante :
-
-```
-hugo serve
-```
-
-Se rendre sur `http://localhost:1313`
-
-Vous devriez voir trois choses:
-
-1. Vous avez un menu **Basics** à gauche, qui contient deux sous-menu avec des noms égal au paramètre `title` des fichiers précédemment générés.
-2. La page d'accueil vous explique comment la modifier. Suivez les instructions.
-3. Avec la commande `hugo serve`, la page se rafraichit automatiquement à chaque fois que vous sauvegardez. Super !
-
-## Générez le site
-
-Quand votre site est prêt à être déployé, lancez la commande suivante:
-
-```
-hugo
-```
-
-Un dossier `public` a été généré. Il contient tout le contenu statique et les ressources nécessaires pour votre site. Votre site peut maintenant être déployé en utilisant n'importe quel serveur !
-
-{{% notice note %}}
-Ce site peut être automatiquement publié et hébergé avec [Netlify](https://www.netlify.com/) ([Plus d'infos](https://www.netlify.com/blog/2015/07/30/hosting-hugo-on-netlifyinsanely-fast-deploys/)). Sinon, vous pouvez utiliser les [Github pages](https://gohugo.io/hosting-and-deployment/hosting-on-github/)
-{{% /notice %}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/installation/images/chapter.png b/documentation/staging/themes/learn/exampleSite/content/basics/installation/images/chapter.png
deleted file mode 100644
index 80da0c6d6..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/installation/images/chapter.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.en.md
deleted file mode 100644
index 2b3f51d93..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.en.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Requirements
-weight: 10
-disableToc: true
----
-
-Thanks to the simplicity of Hugo, this page is as empty as this theme needs requirements.
-
-Just download latest version of [Hugo binary (> 0.25)](https://gohugo.io/getting-started/installing/) for your OS (Windows, Linux, Mac) : it's that simple.
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.fr.md
deleted file mode 100644
index ae70caea5..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/_index.fr.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Prérequis
-weight: 10
-disableToc: true
----
-
-Grâce à la simplicité d'Hugo, cette page est vide car il n'y a quasi pas de prérequis pour utiliser le thème.
-
-Téléchargez la dernière version du [binaire Hugo (> 0.25)](https://gohugo.io/getting-started/installing/) pour votre Système d'exploitation (Windows, Linux, Mac) : et c'est tout !
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/images/magic.gif b/documentation/staging/themes/learn/exampleSite/content/basics/requirements/images/magic.gif
deleted file mode 100644
index 235c4edb3..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/requirements/images/magic.gif and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.en.md
deleted file mode 100644
index c6920c5d4..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.en.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Style customization
-weight: 25
----
-
-**Hugo-theme-learn** has been built to be as configurable as possible by defining multiple [partials](https://gohugo.io/templates/partials/)
-
-In `themes/hugo-theme-learn/layouts/partials/`, you will find all the partials defined for this theme. If you need to overwrite something, don't change the code directly. Instead [follow this page](https://gohugo.io/themes/customizing/). You'd create a new partial in the `layouts/partials` folder of your local project. This partial will have the priority.
-
-This theme defines the following partials :
-
-- *header*: the header of the content page (contains the breadcrumbs). _Not meant to be overwritten_
-- *custom-header*: custom headers in page. Meant to be overwritten when adding CSS imports. Don't forget to include `style` HTML tag directive in your file
-- *footer*: the footer of the content page (contains the arrows). _Not meant to be overwritten_
-- *custom-footer*: custom footer in page. Meant to be overwritten when adding Javacript. Don't forget to include `javascript` HTML tag directive in your file
-- *favicon*: the favicon
-- *logo*: the logo, on top left hand corner.
-- *meta*: HTML meta tags, if you want to change default behavior
-- *menu*: left menu. _Not meant to be overwritten_
-- *menu-footer*: footer of the the left menu
-- *search*: search box
-- *toc*: table of contents
-
-## Change the logo
-
-Create a new file in `layouts/partials/` named `logo.html`. Then write any HTML you want.
-You could use an `img` HTML tag and reference an image created under the *static* folder, or you could paste a SVG definition !
-
-{{% notice note %}}
-The size of the logo will adapt automatically
-{{% /notice %}}
-
-## Change the favicon
-
-If your favicon is a png, just drop off your image in your local `static/images/` folder and name it `favicon.png`
-
-If you need to change this default behavior, create a new file in `layouts/partials/` named `favicon.html`. Then write something like this:
-
-```html
-
-```
-
-## Change default colors {#theme-variant}
-
-**Hugo Learn theme** let you choose between 3 native color scheme variants, but feel free to add one yourself ! Default color scheme is based on [Grav Learn Theme](https://learn.getgrav.org/).
-
-### Red variant
-
-```toml
-[params]
- # Change default color scheme with a variant one. Can be "red", "blue", "green".
- themeVariant = "red"
-```
-
-
-
-### Blue variant
-
-```toml
-[params]
- # Change default color scheme with a variant one. Can be "red", "blue", "green".
- themeVariant = "blue"
-```
-
-
-
-### Green variant
-
-```toml
-[params]
- # Change default color scheme with a variant one. Can be "red", "blue", "green".
- themeVariant = "green"
-```
-
-
-
-### 'Yours‘ variant
-
-First, create a new CSS file in your local `static/css` folder prefixed by `theme` (e.g. with _mine_ theme `static/css/theme-mine.css`). Copy the following content and modify colors in CSS variables.
-
-```css
-
-:root{
-
- --MAIN-TEXT-color:#323232; /* Color of text by default */
- --MAIN-TITLES-TEXT-color: #5e5e5e; /* Color of titles h2-h3-h4-h5 */
- --MAIN-LINK-color:#1C90F3; /* Color of links */
- --MAIN-LINK-HOVER-color:#167ad0; /* Color of hovered links */
- --MAIN-ANCHOR-color: #1C90F3; /* color of anchors on titles */
-
- --MENU-HEADER-BG-color:#1C90F3; /* Background color of menu header */
- --MENU-HEADER-BORDER-color:#33a1ff; /*Color of menu header border */
-
- --MENU-SEARCH-BG-color:#167ad0; /* Search field background color (by default borders + icons) */
- --MENU-SEARCH-BOX-color: #33a1ff; /* Override search field border color */
- --MENU-SEARCH-BOX-ICONS-color: #a1d2fd; /* Override search field icons color */
-
- --MENU-SECTIONS-ACTIVE-BG-color:#20272b; /* Background color of the active section and its childs */
- --MENU-SECTIONS-BG-color:#252c31; /* Background color of other sections */
- --MENU-SECTIONS-LINK-color: #ccc; /* Color of links in menu */
- --MENU-SECTIONS-LINK-HOVER-color: #e6e6e6; /* Color of links in menu, when hovered */
- --MENU-SECTION-ACTIVE-CATEGORY-color: #777; /* Color of active category text */
- --MENU-SECTION-ACTIVE-CATEGORY-BG-color: #fff; /* Color of background for the active category (only) */
-
- --MENU-VISITED-color: #33a1ff; /* Color of 'page visited' icons in menu */
- --MENU-SECTION-HR-color: #20272b; /* Color of separator in menu */
-
-}
-
-body {
- color: var(--MAIN-TEXT-color) !important;
-}
-
-textarea:focus, input[type="email"]:focus, input[type="number"]:focus, input[type="password"]:focus, input[type="search"]:focus, input[type="tel"]:focus, input[type="text"]:focus, input[type="url"]:focus, input[type="color"]:focus, input[type="date"]:focus, input[type="datetime"]:focus, input[type="datetime-local"]:focus, input[type="month"]:focus, input[type="time"]:focus, input[type="week"]:focus, select[multiple=multiple]:focus {
- border-color: none;
- box-shadow: none;
-}
-
-h2, h3, h4, h5 {
- color: var(--MAIN-TITLES-TEXT-color) !important;
-}
-
-a {
- color: var(--MAIN-LINK-color);
-}
-
-.anchor {
- color: var(--MAIN-ANCHOR-color);
-}
-
-a:hover {
- color: var(--MAIN-LINK-HOVER-color);
-}
-
-#sidebar ul li.visited > a .read-icon {
- color: var(--MENU-VISITED-color);
-}
-
-#body a.highlight:after {
- display: block;
- content: "";
- height: 1px;
- width: 0%;
- -webkit-transition: width 0.5s ease;
- -moz-transition: width 0.5s ease;
- -ms-transition: width 0.5s ease;
- transition: width 0.5s ease;
- background-color: var(--MAIN-LINK-HOVER-color);
-}
-#sidebar {
- background-color: var(--MENU-SECTIONS-BG-color);
-}
-#sidebar #header-wrapper {
- background: var(--MENU-HEADER-BG-color);
- color: var(--MENU-SEARCH-BOX-color);
- border-color: var(--MENU-HEADER-BORDER-color);
-}
-#sidebar .searchbox {
- border-color: var(--MENU-SEARCH-BOX-color);
- background: var(--MENU-SEARCH-BG-color);
-}
-#sidebar ul.topics > li.parent, #sidebar ul.topics > li.active {
- background: var(--MENU-SECTIONS-ACTIVE-BG-color);
-}
-#sidebar .searchbox * {
- color: var(--MENU-SEARCH-BOX-ICONS-color);
-}
-
-#sidebar a {
- color: var(--MENU-SECTIONS-LINK-color);
-}
-
-#sidebar a:hover {
- color: var(--MENU-SECTIONS-LINK-HOVER-color);
-}
-
-#sidebar ul li.active > a {
- background: var(--MENU-SECTION-ACTIVE-CATEGORY-BG-color);
- color: var(--MENU-SECTION-ACTIVE-CATEGORY-color) !important;
-}
-
-#sidebar hr {
- border-color: var(--MENU-SECTION-HR-color);
-}
-```
-
-Then, set the `themeVariant` value with the name of your custom theme file. That's it !
-
-```toml
-[params]
- # Change default color scheme with a variant one. Can be "red", "blue", "green".
- themeVariant = "mine"
-```
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md
deleted file mode 100644
index 6daab9e84..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/_index.fr.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Personnalisation du style
-weight: 25
----
-
-**Hugo-theme-learn** a été conçu pour être aussi configurable que possible en définissant plusieurs [partials](https://gohugo.io/templates/partials/)
-
-Dans `themes/hugo-theme-learn/layouts/partials/`, vous pourrez trouver tous les *partials* définis pour ce thème. Si vous avez besoin d'écraser quelque chose, ne modifiez pas le code directement. A la place, [suivez cette page](https://gohugo.io/themes/customizing/). Vous créerez alors un nouveau *partial* dans le dossier `layouts/partials` de votre site local. Ce *partial* aura la priorité.
-
-Ce thème définit les *partials* suivant :
-
-- *header*: l'en-tête de la page page (contient le fil d'Ariane). _Pas voué à être écrasé_
-- *custom-header*: En-tête personnalisé. Voué à être écrasé quand vous ajoutez des imports CSS. N'oubliez pas d'inclure la balise HTML `style` dans votre fichier
-- *footer*: le pied-de-page de la page (contains les flèches). _Pas voué à être écrasé_
-- *custom-footer*: Pied-de-page personnalisé. Voué à être écrasé quand vous ajoutez du Javascript. N'oubliez pas d'inclure la balise HTML `javascript` dans votre fichier
-- *favicon*: le favicon
-- *logo*: le logo, affiché un haut à gauche.
-- *meta*: les balises HTML meta, que vous pouvez écraser sans problème.
-- *menu*: Le menu à gauche. _Pas voué à être écrasé_
-- *menu-footer*: Le pied-de-page du menu
-- *search*: le champ de recherche
-- *toc*: le sommaire
-
-## Changer le logo
-
-Créez un nouveau fichier dans `layouts/partials/`, nommé `logo.html`. Puis, écrivez le code HTML voulu.
-Vous pourriez utiliser une balise HTML `img` et référencer une image créée dans le dossier *static*, voire même y coller un code SVG !
-
-{{% notice note %}}
-La taille du logo va s'adapter automatiquement
-{{% /notice %}}
-
-## Changer le favicon
-
-Si votre favicon est un png, déposez votre image dans votre dossier local `static/images/` et nommez le `favicon.png`
-
-Si vous avez besoin de changer ce comportement par défaut, créer un nouveau fichier dans `layouts/partials/` et nommez le `favicon.html`. Puis ajoutez quelque chose comme:
-
-```html
-
-```
-
-## Changer les couleurs par défaut {#theme-variant}
-
-**Hugo Learn theme** vous permet de choisir nativement entre 3 schéma de couleurs, mais n'hésitez pas à en ajouter d'autres ! Les couleurs par défaut sont celles de [Grav Learn Theme](https://learn.getgrav.org/).
-
-### Variante rouge
-
-```toml
-[params]
- # Modifier le schéma de couleur par défaut. Peut être "red", "blue", "green".
- themeVariant = "red"
-```
-
-
-
-### Variante bleue
-
-```toml
-[params]
- # Modifier le schéma de couleur par défaut. Peut être "red", "blue", "green".
- themeVariant = "blue"
-```
-
-
-
-### Variante verte
-
-```toml
-[params]
- # Modifier le schéma de couleur par défaut. Peut être "red", "blue", "green".
- themeVariant = "green"
-```
-
-
-
-### Votre variante
-
-Premièrement, créez un nouveau fichier CSS dans votre dossier `static/css`, préfixé par `theme` (ex: avec le theme_lemien_ `static/css/theme-lemien.css`). Copiez le contenu suivant et modifiez les couleurs dans les variables CSS.
-
-```css
-
-:root{
-
- --MAIN-TEXT-color:#323232; /* Color of text by default */
- --MAIN-TITLES-TEXT-color: #5e5e5e; /* Color of titles h2-h3-h4-h5 */
- --MAIN-LINK-color:#1C90F3; /* Color of links */
- --MAIN-LINK-HOVER-color:#167ad0; /* Color of hovered links */
- --MAIN-ANCHOR-color: #1C90F3; /* color of anchors on titles */
-
- --MENU-HEADER-BG-color:#1C90F3; /* Background color of menu header */
- --MENU-HEADER-BORDER-color:#33a1ff; /*Color of menu header border */
-
- --MENU-SEARCH-BG-color:#167ad0; /* Search field background color (by default borders + icons) */
- --MENU-SEARCH-BOX-color: #33a1ff; /* Override search field border color */
- --MENU-SEARCH-BOX-ICONS-color: #a1d2fd; /* Override search field icons color */
-
- --MENU-SECTIONS-ACTIVE-BG-color:#20272b; /* Background color of the active section and its childs */
- --MENU-SECTIONS-BG-color:#252c31; /* Background color of other sections */
- --MENU-SECTIONS-LINK-color: #ccc; /* Color of links in menu */
- --MENU-SECTIONS-LINK-HOVER-color: #e6e6e6; /* Color of links in menu, when hovered */
- --MENU-SECTION-ACTIVE-CATEGORY-color: #777; /* Color of active category text */
- --MENU-SECTION-ACTIVE-CATEGORY-BG-color: #fff; /* Color of background for the active category (only) */
-
- --MENU-VISITED-color: #33a1ff; /* Color of 'page visited' icons in menu */
- --MENU-SECTION-HR-color: #20272b; /* Color of separator in menu */
-
-}
-
-body {
- color: var(--MAIN-TEXT-color) !important;
-}
-
-textarea:focus, input[type="email"]:focus, input[type="number"]:focus, input[type="password"]:focus, input[type="search"]:focus, input[type="tel"]:focus, input[type="text"]:focus, input[type="url"]:focus, input[type="color"]:focus, input[type="date"]:focus, input[type="datetime"]:focus, input[type="datetime-local"]:focus, input[type="month"]:focus, input[type="time"]:focus, input[type="week"]:focus, select[multiple=multiple]:focus {
- border-color: none;
- box-shadow: none;
-}
-
-h2, h3, h4, h5 {
- color: var(--MAIN-TITLES-TEXT-color) !important;
-}
-
-a {
- color: var(--MAIN-LINK-color);
-}
-
-.anchor {
- color: var(--MAIN-ANCHOR-color);
-}
-
-a:hover {
- color: var(--MAIN-LINK-HOVER-color);
-}
-
-#sidebar ul li.visited > a .read-icon {
- color: var(--MENU-VISITED-color);
-}
-
-#body a.highlight:after {
- display: block;
- content: "";
- height: 1px;
- width: 0%;
- -webkit-transition: width 0.5s ease;
- -moz-transition: width 0.5s ease;
- -ms-transition: width 0.5s ease;
- transition: width 0.5s ease;
- background-color: var(--MAIN-LINK-HOVER-color);
-}
-#sidebar {
- background-color: var(--MENU-SECTIONS-BG-color);
-}
-#sidebar #header-wrapper {
- background: var(--MENU-HEADER-BG-color);
- color: var(--MENU-SEARCH-BOX-color);
- border-color: var(--MENU-HEADER-BORDER-color);
-}
-#sidebar .searchbox {
- border-color: var(--MENU-SEARCH-BOX-color);
- background: var(--MENU-SEARCH-BG-color);
-}
-#sidebar ul.topics > li.parent, #sidebar ul.topics > li.active {
- background: var(--MENU-SECTIONS-ACTIVE-BG-color);
-}
-#sidebar .searchbox * {
- color: var(--MENU-SEARCH-BOX-ICONS-color);
-}
-
-#sidebar a {
- color: var(--MENU-SECTIONS-LINK-color);
-}
-
-#sidebar a:hover {
- color: var(--MENU-SECTIONS-LINK-HOVER-color);
-}
-
-#sidebar ul li.active > a {
- background: var(--MENU-SECTION-ACTIVE-CATEGORY-BG-color);
- color: var(--MENU-SECTION-ACTIVE-CATEGORY-color) !important;
-}
-
-#sidebar hr {
- border-color: var(--MENU-SECTION-HR-color);
-}
-```
-
-Puis, configurez le paramètre `themeVariant` avec le nom de votre variante. C'est tout !
-
-```toml
-[params]
- # Modifier le schéma de couleur par défaut. Peut être "red", "blue", "green".
- themeVariant = "lemien"
-```
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png b/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png
deleted file mode 100644
index 4f79d58b1..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/blue-variant.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png b/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png
deleted file mode 100644
index a4b73b58e..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/green-variant.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png b/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png
deleted file mode 100644
index 6af77497d..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/basics/style-customization/images/red-variant.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/_index.en.md
deleted file mode 100644
index cbdc696a1..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/_index.en.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Content
-weight: 10
-chapter: true
-pre: "2. "
----
-
-### Chapter 2
-
-# Content
-
-Find out how to create and organize your content quickly and intuitively.
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/_index.fr.md
deleted file mode 100644
index dae5873c8..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/_index.fr.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Contenu
-weight: 10
-chapter: true
-pre: "2. "
----
-
-### Chapitre 2
-
-# Contenu
-
-Découvrez comment créer et organiser votre contenu facilement et intuitivement.
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.en.md
deleted file mode 100644
index d5fd99702..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.en.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Archetypes
-weight: 10
----
-
-Using the command: `hugo new [relative new content path]`, you can start a content file with the date and title automatically set. While this is a welcome feature, active writers need more: [archetypes](https://gohugo.io/content/archetypes/).
-
-It is pre-configured skeleton pages with default front matter. Please refer to the documentation for types of page to understand the differences.
-
-## Chapter {#archetypes-chapter}
-
-To create a Chapter page, run the following commands
-
-```
-hugo new --kind chapter /_index.md
-```
-
-It will create a page with predefined Front-Matter:
-
-```markdown
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-chapter = true
-pre = "X. "
-+++
-
-### Chapter X
-
-# Some Chapter title
-
-Lorem Ipsum.
-```
-
-## Default
-
-To create a default page, run either one of the following commands
-
-```
-# Either
-hugo new //_index.md
-# Or
-hugo new /.md
-```
-
-It will create a page with predefined Front-Matter:
-
-```markdown
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-+++
-
-Lorem Ipsum.
-```
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.fr.md
deleted file mode 100644
index 883c41865..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/archetypes.fr.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Archétypes
-weight: 10
----
-
-En utilisant la commande: `hugo new [chemin vers nouveau contenu]`, vous pouvez créer un nouveau fichier avec la date et le title automatiquement initialisé. Même si c'est une fonctionnalité intéressante, elle reste limitée pour les auteurs actifs qui ont besoin de mieux : les [archetypes](https://gohugo.io/content/archetypes/).
-
-Les archétypes sont des squelettes de pages préconfigurées avec un Front Matter par défaut. Merci de vous référer à la documentation pour connaitre les différents types de page.
-
-## Chapitre {#archetypes-chapter}
-
-Pour créer un chapitre, lancez les commandes suivantes
-
-```
-hugo new --kind chapter /_index.md
-```
-
-Cela crééra une page avec le Front Matter suivant:
-
-```markdown
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-chapter = true
-pre = "X. "
-+++
-
-### Chapter X
-
-# Some Chapter title
-
-Lorem Ipsum.
-```
-
-## Défaut
-
-Pour créer une page classique, lancer l'une des deux commandes suivantes
-
-```
-# Soit
-hugo new //_index.md
-# Ou
-hugo new /.md
-```
-
-Cela crééra une page avec le Front Matter suivant:
-
-```markdown
-+++
-title = "{{ replace .Name "-" " " | title }}"
-date = {{ .Date }}
-weight = 5
-+++
-
-Lorem Ipsum.
-```
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.en.md
deleted file mode 100644
index c35327582..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.en.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Multilingual and i18n
-weight: 30
----
-
-**Learn theme** is fully compatible with Hugo multilingual mode.
-
-It provides:
-
-- Translation strings for default values (English and French). Feel free to contribute !
-- Automatic menu generation from multilingual content
-- In-browser language switching
-
-
-
-## Basic configuration
-
-After learning [how Hugo handle multilingual websites](https://gohugo.io/content-management/multilingual), define your languages in your `config.toml` file.
-
-For example with current French and English website.
-
-```toml
-# English is the default language
-defaultContentLanguage = "en"
-# Force to have /en/my-page and /fr/my-page routes, even for default language.
-defaultContentLanguageInSubdir= true
-
-[Languages]
-[Languages.en]
-title = "Documentation for Hugo Learn Theme"
-weight = 1
-languageName = "English"
-
-[Languages.fr]
-title = "Documentation du thème Hugo Learn"
-weight = 2
-languageName = "Français"
-```
-
-Then, for each new page, append the *id* of the language to the file.
-
-- Single file `my-page.md` is split in two files:
- - in English: `my-page.en.md`
- - in French: `my-page.fr.md`
-- Single file `_index.md` is split in two files:
- - in English: `_index.en.md`
- - in French: `_index.fr.md`
-
-{{% notice info %}}
-Be aware that only translated pages are displayed in menu. It's not replaced with default language content.
-{{% /notice %}}
-
-{{% notice tip %}}
-Use [slug](https://gohugo.io/content-management/multilingual/#translate-your-content) Front Matter parameter to translate urls too.
-{{% /notice %}}
-
-## Overwrite translation strings
-
-Translations strings are used for common default values used in the theme (*Edit this page* button, *Search placeholder* and so on). Translations are available in french and english but you may use another language or want to override default values.
-
-To override these values, create a new file in your local i18n folder `i18n/.toml` and inspire yourself from the theme `themes/hugo-theme-learn/i18n/en.toml`
-
-By the way, as these translations could be used by other people, please take the time to propose a translation by [making a PR](https://github.com/matcornic/hugo-theme-learn/pulls) to the theme !
-
-## Disable language switching
-
-Switching the language in the browser is a great feature, but for some reasons you may want to disable it.
-
-Just set `disableLanguageSwitchingButton=true` in your `config.toml`
-
-```toml
-[params]
- # When using mulitlingual website, disable the switch language button.
- disableLanguageSwitchingButton = true
-```
-
-
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.fr.md
deleted file mode 100644
index 6503abf4c..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/_index.fr.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Multi-langue et i18n
-weight: 30
----
-
-**Learn** est complètement compatible avec le mode multi-langue d'Hugo.
-
-Il fournit :
-
-- Des *translation strings* pour les valeurs par défaut utilisées par le thème (Anglais et Français). N'hésitez pas à contribuer !
-- Génération automatique du menu avec le contenu multi-langue
-- Modification de la langue dans le navigateur
-
-
-
-## Configuration simple
-
-Après avoir appris [comment Hugo gère les sites multi-langue](https://gohugo.io/content-management/multilingual), définissez vos langues dans votre fichier `config.toml`.
-
-Par exemple, pour ce site, avec du contenu en français et en anglais.
-
-```toml
-# Anglais est la langue par défaut
-defaultContentLanguage = "en"
-# Force d'avoir /en/ma-page et /fr/ma-page routes, même avec la langue par défaut.
-defaultContentLanguageInSubdir= true
-
-[Languages]
-[Languages.en]
-title = "Documentation for Hugo Learn Theme"
-weight = 1
-languageName = "English"
-
-[Languages.fr]
-title = "Documentation du thème Hugo Learn"
-weight = 2
-languageName = "Français"
-```
-
-Puis, pour chaque nouvelle page, ajoutez *l'id* de la langue du fichier.
-
-- Le fichier `my-page.md` est découpé en deux fichiers :
- - en anglais : `my-page.en.md`
- - en français : `my-page.fr.md`
-- Le fichier `_index.md` est découpé en deux fichiers :
- - en anglais: `_index.en.md`
- - en français: `_index.fr.md`
-
-{{% notice info %}}
-Attention, seulement les pages traduites sont affichées dans le menu. Le contenu n'est pas remplacé par les pages de la langue par défaut.
-{{% /notice %}}
-
-{{% notice tip %}}
-Utilisez le paramètre du Front Matter [slug](https://gohugo.io/content-management/multilingual/#translate-your-content) pour traduire également les URLs.
-{{% /notice %}}
-
-## Surcharger les *translation strings*
-
-Les *Translations strings* sont utilisées comme valeurs par défaut dans le thème (Bouton *Modifier la page*, Element de subsitution *Recherche*, etc.). Les traductions sont disponibles en français et en anglais mais vous pouvez utiliser n'importe quelle autre langue et surcharger avec vos propres valeurs.
-
-Pour surcharger ces valeurs, créer un nouveau fichier dans votre dossier i18n local `i18n/.toml` et inspirez vous du thème `themes/hugo-theme-learn/i18n/en.toml`
-
-D'ailleurs, ces traductions pour servir à tout le monde, donc svp prenez le temps de [proposer une Pull Request](https://github.com/matcornic/hugo-theme-learn/pulls) !
-
-## Désactiver le changement de langue
-
-Vous pouvez changer de langue directement dans le navigateur. C'est une super fonctionnalité, mais vous avez peut-être besoin de la désactiver.
-
-Pour ce faire, ajouter le paramètre `disableLanguageSwitchingButton=true` dans votre `config.toml`
-
-```toml
-[params]
- # Quand vous utilisez un site en multi-langue, désactive le bouton de changment de langue.
- disableLanguageSwitchingButton = true
-```
-
-
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif b/documentation/staging/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif
deleted file mode 100644
index 99ee22267..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/cont/i18n/images/i18n-menu.gif and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/icons.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/icons.en.md
deleted file mode 100644
index ad769c6c1..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/icons.en.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Icons and logos
-weight: 27
----
-
-The Learn theme for Hugo loads the [**Font Awesome**](https://fontawesome.com) library, allowing you to easily display any icon or logo available in the Font Awesome free collection.
-
-## Finding an icon
-
-Browse through the available icons in the [Font Awesome Gallery](https://fontawesome.com/icons?d=gallery&m=free). Notice that the **free** filter is enabled, as only the free icons are available by default.
-
-Once on the Font Awesome page for a specific icon, for example the page for the [heart](https://fontawesome.com/icons/heart?style=solid), copy the HTML reference and paste into the markdown content.
-
-The HTML to include the heart icon is:
-
-```
-
-```
-
-## Including in markdown
-
-Paste the `` HTML into markup and Font Awesome will load the relevant icon.
-
-```
-Built with from Grav and Hugo
-```
-
-Which appears as
-
-Built with from Grav and Hugo
-
-## Customising icons
-
-Font Awesome provides many ways to modify the icon
-
-* Change colour (by default the icon will inherit the parent colour)
-* Increase or decrease size
-* Rotate
-* Combine with other icons
-
-Check the full documentation on [web fonts with CSS](https://fontawesome.com/how-to-use/web-fonts-with-css) for more.
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/markdown.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/markdown.en.md
deleted file mode 100644
index c97701e01..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/markdown.en.md
+++ /dev/null
@@ -1,692 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Markdown syntax
-weight: 15
----
-
-{{% notice note %}}
-This page is a shameful copy of the great [Grav original page](http://learn.getgrav.org/content/markdown).
-Only difference is information about image customization ([resizing]({{< relref "#resizing-image" >}}), [add CSS classes]({{< relref "#add-css-classes" >}})...)
-{{% /notice%}}
-
-Let's face it: Writing content for the Web is tiresome. WYSIWYG editors help alleviate this task, but they generally result in horrible code, or worse yet, ugly web pages.
-
-**Markdown** is a better way to write **HTML**, without all the complexities and ugliness that usually accompanies it.
-
-Some of the key benefits are:
-
-1. Markdown is simple to learn, with minimal extra characters so it's also quicker to write content.
-2. Less chance of errors when writing in markdown.
-3. Produces valid XHTML output.
-4. Keeps the content and the visual display separate, so you cannot mess up the look of your site.
-5. Write in any text editor or Markdown application you like.
-6. Markdown is a joy to use!
-
-John Gruber, the author of Markdown, puts it like this:
-
-> The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. While Markdown’s syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown’s syntax is the format of plain text email.
-> -- John Gruber
-
-Grav ships with built-in support for [Markdown](http://daringfireball.net/projects/markdown/) and [Markdown Extra](https://michelf.ca/projects/php-markdown/extra/). You must enable **Markdown Extra** in your `system.yaml` configuration file
-
-Without further delay, let us go over the main elements of Markdown and what the resulting HTML looks like:
-
-{{% notice info %}}
- Bookmark this page for easy future reference!
-{{% /notice %}}
-
-## Headings
-
-Headings from `h1` through `h6` are constructed with a `#` for each level:
-
-```markdown
-# h1 Heading
-## h2 Heading
-### h3 Heading
-#### h4 Heading
-##### h5 Heading
-###### h6 Heading
-```
-
-Renders to:
-
-# h1 Heading
-
-
-## h2 Heading
-
-### h3 Heading
-
-#### h4 Heading
-
-##### h5 Heading
-
-###### h6 Heading
-
-HTML:
-
-```html
-
h1 Heading
-
h2 Heading
-
h3 Heading
-
h4 Heading
-
h5 Heading
-
h6 Heading
-```
-
-## Comments
-
-Comments should be HTML compatible
-
-```html
-
-```
-
-Comment below should **NOT** be seen:
-
-
-
-## Horizontal Rules
-
-The HTML `` element is for creating a "thematic break" between paragraph-level elements. In markdown, you can create a `` with any of the following:
-
-* `___`: three consecutive underscores
-* `---`: three consecutive dashes
-* `***`: three consecutive asterisks
-
-renders to:
-
-___
-
-## Body Copy
-
-Body copy written as normal, plain text will be wrapped with `` tags in the rendered HTML.
-
-So this body copy:
-
-```markdown
-Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
-```
-
-renders to this HTML:
-
-```html
-
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
-```
-
-## Emphasis
-
-### Bold
-
-For emphasizing a snippet of text with a heavier font-weight.
-
-The following snippet of text is **rendered as bold text**.
-
-```markdown
-**rendered as bold text**
-```
-
-renders to:
-
-
-**rendered as bold text**
-
-
-and this HTML
-
-```html
-rendered as bold text
-```
-
-### Italics
-
-For emphasizing a snippet of text with italics.
-
-The following snippet of text is _rendered as italicized text_.
-
-```markdown
-_rendered as italicized text_
-```
-
-renders to:
-
-
-_rendered as italicized text_
-
-
-and this HTML:
-
-```html
-rendered as italicized text
-```
-
-### Strikethrough
-
-In GFM (GitHub flavored Markdown) you can do strikethroughs.
-
-```markdown
-~~Strike through this text.~~
-```
-
-Which renders to:
-
-~~Strike through this text.~~
-
-HTML:
-
-```html
-Strike through this text.
-```
-
-## Blockquotes
-
-For quoting blocks of content from another source within your document.
-
-Add `>` before any text you want to quote.
-
-```markdown
-> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-```
-
-Renders to:
-
-> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-
-and this HTML:
-
-```html
-
-
Fusion Drive combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-
-```
-
-Blockquotes can also be nested:
-
-```markdown
-> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
->
-> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
->
-> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
-```
-
-Renders to:
-
-> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
->
-> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
->
-> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
-
-## Notices
-
-{{% notice note %}}
-The old mechanism for notices overriding the block quote syntax (`>>>`) has been deprecated. Notices are now handled via a dedicated plugin called [Markdown Notices](https://github.com/getgrav/grav-plugin-markdown-notices)
-{{% /notice %}}
-
-## Lists
-
-### Unordered
-
-A list of items in which the order of the items does not explicitly matter.
-
-You may use any of the following symbols to denote bullets for each list item:
-
-```markdown
-* valid bullet
-- valid bullet
-+ valid bullet
-```
-
-For example
-
-```markdown
-+ Lorem ipsum dolor sit amet
-+ Consectetur adipiscing elit
-+ Integer molestie lorem at massa
-+ Facilisis in pretium nisl aliquet
-+ Nulla volutpat aliquam velit
- - Phasellus iaculis neque
- - Purus sodales ultricies
- - Vestibulum laoreet porttitor sem
- - Ac tristique libero volutpat at
-+ Faucibus porta lacus fringilla vel
-+ Aenean sit amet erat nunc
-+ Eget porttitor lorem
-```
-
-Renders to:
-
-
-+ Lorem ipsum dolor sit amet
-+ Consectetur adipiscing elit
-+ Integer molestie lorem at massa
-+ Facilisis in pretium nisl aliquet
-+ Nulla volutpat aliquam velit
- - Phasellus iaculis neque
- - Purus sodales ultricies
- - Vestibulum laoreet porttitor sem
- - Ac tristique libero volutpat at
-+ Faucibus porta lacus fringilla vel
-+ Aenean sit amet erat nunc
-+ Eget porttitor lorem
-
-
-And this HTML
-
-```html
-
-
Lorem ipsum dolor sit amet
-
Consectetur adipiscing elit
-
Integer molestie lorem at massa
-
Facilisis in pretium nisl aliquet
-
Nulla volutpat aliquam velit
-
-
Phasellus iaculis neque
-
Purus sodales ultricies
-
Vestibulum laoreet porttitor sem
-
Ac tristique libero volutpat at
-
-
-
Faucibus porta lacus fringilla vel
-
Aenean sit amet erat nunc
-
Eget porttitor lorem
-
-```
-
-### Ordered
-
-A list of items in which the order of items does explicitly matter.
-
-```markdown
-1. Lorem ipsum dolor sit amet
-4. Consectetur adipiscing elit
-2. Integer molestie lorem at massa
-8. Facilisis in pretium nisl aliquet
-4. Nulla volutpat aliquam velit
-99. Faucibus porta lacus fringilla vel
-21. Aenean sit amet erat nunc
-6. Eget porttitor lorem
-```
-
-Renders to:
-
-1. Lorem ipsum dolor sit amet
-2. Consectetur adipiscing elit
-3. Integer molestie lorem at massa
-4. Facilisis in pretium nisl aliquet
-5. Nulla volutpat aliquam velit
-6. Faucibus porta lacus fringilla vel
-7. Aenean sit amet erat nunc
-8. Eget porttitor lorem
-
-And this HTML:
-
-```html
-
-
Lorem ipsum dolor sit amet
-
Consectetur adipiscing elit
-
Integer molestie lorem at massa
-
Facilisis in pretium nisl aliquet
-
Nulla volutpat aliquam velit
-
Faucibus porta lacus fringilla vel
-
Aenean sit amet erat nunc
-
Eget porttitor lorem
-
-```
-
-**TIP**: If you just use `1.` for each number, Markdown will automatically number each item. For example:
-
-```markdown
-1. Lorem ipsum dolor sit amet
-1. Consectetur adipiscing elit
-1. Integer molestie lorem at massa
-1. Facilisis in pretium nisl aliquet
-1. Nulla volutpat aliquam velit
-1. Faucibus porta lacus fringilla vel
-1. Aenean sit amet erat nunc
-1. Eget porttitor lorem
-```
-
-Renders to:
-
-1. Lorem ipsum dolor sit amet
-2. Consectetur adipiscing elit
-3. Integer molestie lorem at massa
-4. Facilisis in pretium nisl aliquet
-5. Nulla volutpat aliquam velit
-6. Faucibus porta lacus fringilla vel
-7. Aenean sit amet erat nunc
-8. Eget porttitor lorem
-
-## Code
-
-### Inline code
-
-Wrap inline snippets of code with `` ` ``.
-
-```markdown
-In this example, `` should be wrapped as **code**.
-```
-
-Renders to:
-
-In this example, `` should be wrapped as **code**.
-
-HTML:
-
-```html
-
In this example, <section></section> should be wrapped as code.
-```
-
-### Indented code
-
-Or indent several lines of code by at least two spaces, as in:
-
-```markdown
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-```
-
-Renders to:
-
-
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-
-
-HTML:
-
-```html
-
-
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-
-
-```
-
-### Block code "fences"
-
-Use "fences" ```` ``` ```` to block in multiple lines of code.
-
-```markdown
-Sample text here...
-```
-
-HTML:
-
-```html
-
- Sample text here...
-
-```
-
-### Syntax highlighting
-
-GFM, or "GitHub Flavored Markdown" also supports syntax highlighting. To activate it, simply add the file extension of the language you want to use directly after the first code "fence", ` ```js `, and syntax highlighting will automatically be applied in the rendered HTML.
-
-See [Code Highlighting]({{< ref "syntaxhighlight.md" >}}) for additional documentation.
-
-For example, to apply syntax highlighting to JavaScript code:
-
-```plaintext
- ```js
- grunt.initConfig({
- assemble: {
- options: {
- assets: 'docs/assets',
- data: 'src/data/*.{json,yml}',
- helpers: 'src/custom-helpers.js',
- partials: ['src/partials/**/*.{hbs,md}']
- },
- pages: {
- options: {
- layout: 'default.hbs'
- },
- files: {
- './': ['src/templates/pages/index.hbs']
- }
- }
- }
- };
- ```
-```
-
-Renders to:
-
-```js
-grunt.initConfig({
- assemble: {
- options: {
- assets: 'docs/assets',
- data: 'src/data/*.{json,yml}',
- helpers: 'src/custom-helpers.js',
- partials: ['src/partials/**/*.{hbs,md}']
- },
- pages: {
- options: {
- layout: 'default.hbs'
- },
- files: {
- './': ['src/templates/pages/index.hbs']
- }
- }
- }
-};
-```
-
-## Tables
-
-Tables are created by adding pipes as dividers between each cell, and by adding a line of dashes (also separated by bars) beneath the header. Note that the pipes do not need to be vertically aligned.
-
-```markdown
-| Option | Description |
-| ------ | ----------- |
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-```
-
-Renders to:
-
-| Option | Description |
-| ------ | ----------- |
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-
-And this HTML:
-
-```html
-
-
-
Option
-
Description
-
-
-
data
-
path to data files to supply the data that will be passed into templates.
-
-
-
engine
-
engine to be used for processing templates. Handlebars is the default.
-
-
-
ext
-
extension to be used for dest files.
-
-
-```
-
-### Right aligned text
-
-Adding a colon on the right side of the dashes below any heading will right align text for that column.
-
-```markdown
-| Option | Description |
-| ------:| -----------:|
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-```
-
-| Option | Description |
-| ------:| -----------:|
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-
-## Links
-
-### Basic link
-
-```markdown
-[Assemble](http://assemble.io)
-```
-
-Renders to (hover over the link, there is no tooltip):
-
-[Assemble](http://assemble.io)
-
-HTML:
-
-```html
-Assemble
-```
-
-### Add a tooltip
-
-```markdown
-[Upstage](https://github.com/upstage/ "Visit Upstage!")
-```
-
-Renders to (hover over the link, there should be a tooltip):
-
-[Upstage](https://github.com/upstage/ "Visit Upstage!")
-
-HTML:
-
-```html
-Upstage
-```
-
-### Named Anchors
-
-Named anchors enable you to jump to the specified anchor point on the same page. For example, each of these chapters:
-
-```markdown
-# Table of Contents
- * [Chapter 1](#chapter-1)
- * [Chapter 2](#chapter-2)
- * [Chapter 3](#chapter-3)
-```
-
-will jump to these sections:
-
-```markdown
-## Chapter 1
-Content for chapter one.
-
-## Chapter 2
-Content for chapter one.
-
-## Chapter 3
-Content for chapter one.
-```
-**NOTE** that specific placement of the anchor tag seems to be arbitrary. They are placed inline here since it seems to be unobtrusive, and it works.
-
-## Images {#images}
-Images have a similar syntax to links but include a preceding exclamation point.
-
-```markdown
-
-```
-
-
-
-or
-
-```markdown
-
-```
-
-
-
-Like links, Images also have a footnote style syntax
-
-### Alternative usage : note images
-
-```markdown
-![Alt text][id]
-```
-
-![Alt text][id]
-
-With a reference later in the document defining the URL location:
-
-[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
-
- [id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
-
-### Resizing image
-
-Add HTTP parameters `width` and/or `height` to the link image to resize the image. Values are CSS values (default is `auto`).
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-### Add CSS classes
-
-Add a HTTP `classes` parameter to the link image to add CSS classes. `shadow`and `border` are available but you could define other ones.
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-### Lightbox
-
-Add a HTTP `featherlight` parameter to the link image to disable lightbox. By default lightbox is enabled using the featherlight.js plugin. You can disable this by defining `featherlight` to `false`.
-
-```markdown
-
-```
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/markdown.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/markdown.fr.md
deleted file mode 100644
index e734b31cd..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/markdown.fr.md
+++ /dev/null
@@ -1,666 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Syntaxe Markdown
-weight: 15
----
-
-{{% notice note %}}
-Cette page est une copie de la [doc de Grav](http://learn.getgrav.org/content/markdown).
-La seule différence porte sur la personalisation des images ([taille]({{< relref "#resizing-image" >}}), [ajout de classes CSS]({{< relref "#add-css-classes" >}})...)
-Pour des raisons évidentes, cette page n'a pas été traduites en français 😁
-{{% /notice%}}
-
-Let's face it: Writing content for the Web is tiresome. WYSIWYG editors help alleviate this task, but they generally result in horrible code, or worse yet, ugly web pages.
-
-**Markdown** is a better way to write **HTML**, without all the complexities and ugliness that usually accompanies it.
-
-Some of the key benefits are:
-
-1. Markdown is simple to learn, with minimal extra characters so it's also quicker to write content.
-2. Less chance of errors when writing in markdown.
-3. Produces valid XHTML output.
-4. Keeps the content and the visual display separate, so you cannot mess up the look of your site.
-5. Write in any text editor or Markdown application you like.
-6. Markdown is a joy to use!
-
-John Gruber, the author of Markdown, puts it like this:
-
-> The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. While Markdown’s syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown’s syntax is the format of plain text email.
-> -- John Gruber
-
-
-Grav ships with built-in support for [Markdown](http://daringfireball.net/projects/markdown/) and [Markdown Extra](https://michelf.ca/projects/php-markdown/extra/). You must enable **Markdown Extra** in your `system.yaml` configuration file
-
-Without further delay, let us go over the main elements of Markdown and what the resulting HTML looks like:
-
-{{% notice info %}}
- Bookmark this page for easy future reference!
-{{% /notice %}}
-
-## Headings
-
-Headings from `h1` through `h6` are constructed with a `#` for each level:
-
-```markdown
-# h1 Heading
-## h2 Heading
-### h3 Heading
-#### h4 Heading
-##### h5 Heading
-###### h6 Heading
-```
-
-Renders to:
-
-# h1 Heading
-## h2 Heading
-### h3 Heading
-#### h4 Heading
-##### h5 Heading
-###### h6 Heading
-
-HTML:
-
-```html
-
h1 Heading
-
h2 Heading
-
h3 Heading
-
h4 Heading
-
h5 Heading
-
h6 Heading
-```
-
-## Comments
-
-Comments should be HTML compatible
-
-```html
-
-```
-Comment below should **NOT** be seen:
-
-
-
-
-## Horizontal Rules
-
-The HTML `` element is for creating a "thematic break" between paragraph-level elements. In markdown, you can create a `` with any of the following:
-
-* `___`: three consecutive underscores
-* `---`: three consecutive dashes
-* `***`: three consecutive asterisks
-
-renders to:
-
-___
-
----
-
-***
-
-
-## Body Copy
-
-Body copy written as normal, plain text will be wrapped with `` tags in the rendered HTML.
-
-So this body copy:
-
-```markdown
-Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
-```
-renders to this HTML:
-
-```html
-
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
-```
-
-## Emphasis
-
-### Bold
-For emphasizing a snippet of text with a heavier font-weight.
-
-The following snippet of text is **rendered as bold text**.
-
-```markdown
-**rendered as bold text**
-```
-renders to:
-
-**rendered as bold text**
-
-and this HTML
-
-```html
-rendered as bold text
-```
-
-### Italics
-For emphasizing a snippet of text with italics.
-
-The following snippet of text is _rendered as italicized text_.
-
-```markdown
-_rendered as italicized text_
-```
-
-renders to:
-
-_rendered as italicized text_
-
-and this HTML:
-
-```html
-rendered as italicized text
-```
-
-
-### strikethrough
-In GFM (GitHub flavored Markdown) you can do strikethroughs.
-
-```markdown
-~~Strike through this text.~~
-```
-Which renders to:
-
-~~Strike through this text.~~
-
-HTML:
-
-```html
-Strike through this text.
-```
-
-## Blockquotes
-
-For quoting blocks of content from another source within your document.
-
-Add `>` before any text you want to quote.
-
-```markdown
-> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-```
-
-Renders to:
-
-> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-
-and this HTML:
-
-```html
-
-
Fusion Drive combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
-
-```
-
-Blockquotes can also be nested:
-
-```markdown
-> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
->
-> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
->
-> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
-```
-
-Renders to:
-
-> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
->
-> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
->
-> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
-
-## Notices
-
-{{% notice note %}}
-The old mechanism for notices overriding the block quote syntax (`>>>`) has been deprecated. Notices are now handled via a dedicated plugin called [Markdown Notices](https://github.com/getgrav/grav-plugin-markdown-notices)
-{{% /notice %}}
-
-## Lists
-
-### Unordered
-A list of items in which the order of the items does not explicitly matter.
-
-You may use any of the following symbols to denote bullets for each list item:
-
-```markdown
-* valid bullet
-- valid bullet
-+ valid bullet
-```
-
-For example
-
-```markdown
-+ Lorem ipsum dolor sit amet
-+ Consectetur adipiscing elit
-+ Integer molestie lorem at massa
-+ Facilisis in pretium nisl aliquet
-+ Nulla volutpat aliquam velit
- - Phasellus iaculis neque
- - Purus sodales ultricies
- - Vestibulum laoreet porttitor sem
- - Ac tristique libero volutpat at
-+ Faucibus porta lacus fringilla vel
-+ Aenean sit amet erat nunc
-+ Eget porttitor lorem
-```
-Renders to:
-
-+ Lorem ipsum dolor sit amet
-+ Consectetur adipiscing elit
-+ Integer molestie lorem at massa
-+ Facilisis in pretium nisl aliquet
-+ Nulla volutpat aliquam velit
- - Phasellus iaculis neque
- - Purus sodales ultricies
- - Vestibulum laoreet porttitor sem
- - Ac tristique libero volutpat at
-+ Faucibus porta lacus fringilla vel
-+ Aenean sit amet erat nunc
-+ Eget porttitor lorem
-
-And this HTML
-
-```html
-
-
Lorem ipsum dolor sit amet
-
Consectetur adipiscing elit
-
Integer molestie lorem at massa
-
Facilisis in pretium nisl aliquet
-
Nulla volutpat aliquam velit
-
-
Phasellus iaculis neque
-
Purus sodales ultricies
-
Vestibulum laoreet porttitor sem
-
Ac tristique libero volutpat at
-
-
-
Faucibus porta lacus fringilla vel
-
Aenean sit amet erat nunc
-
Eget porttitor lorem
-
-```
-
-### Ordered
-
-A list of items in which the order of items does explicitly matter.
-
-```markdown
-1. Lorem ipsum dolor sit amet
-2. Consectetur adipiscing elit
-3. Integer molestie lorem at massa
-4. Facilisis in pretium nisl aliquet
-5. Nulla volutpat aliquam velit
-6. Faucibus porta lacus fringilla vel
-7. Aenean sit amet erat nunc
-8. Eget porttitor lorem
-```
-Renders to:
-
-1. Lorem ipsum dolor sit amet
-2. Consectetur adipiscing elit
-3. Integer molestie lorem at massa
-4. Facilisis in pretium nisl aliquet
-5. Nulla volutpat aliquam velit
-6. Faucibus porta lacus fringilla vel
-7. Aenean sit amet erat nunc
-8. Eget porttitor lorem
-
-And this HTML:
-
-```html
-
-
Lorem ipsum dolor sit amet
-
Consectetur adipiscing elit
-
Integer molestie lorem at massa
-
Facilisis in pretium nisl aliquet
-
Nulla volutpat aliquam velit
-
Faucibus porta lacus fringilla vel
-
Aenean sit amet erat nunc
-
Eget porttitor lorem
-
-```
-
-**TIP**: If you just use `1.` for each number, Markdown will automatically number each item. For example:
-
-```markdown
-1. Lorem ipsum dolor sit amet
-1. Consectetur adipiscing elit
-1. Integer molestie lorem at massa
-1. Facilisis in pretium nisl aliquet
-1. Nulla volutpat aliquam velit
-1. Faucibus porta lacus fringilla vel
-1. Aenean sit amet erat nunc
-1. Eget porttitor lorem
-```
-
-Renders to:
-
-1. Lorem ipsum dolor sit amet
-2. Consectetur adipiscing elit
-3. Integer molestie lorem at massa
-4. Facilisis in pretium nisl aliquet
-5. Nulla volutpat aliquam velit
-6. Faucibus porta lacus fringilla vel
-7. Aenean sit amet erat nunc
-8. Eget porttitor lorem
-
-## Code
-
-### Inline code
-Wrap inline snippets of code with `` ` ``.
-
-```markdown
-In this example, `` should be wrapped as **code**.
-```
-
-Renders to:
-
-In this example, `` should be wrapped with **code**.
-
-HTML:
-
-```html
-
In this example, <section></section> should be wrapped with code.
-```
-
-### Indented code
-
-Or indent several lines of code by at least four spaces, as in:
-
-
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-
-
-Renders to:
-
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-
-HTML:
-
-```html
-
-
- // Some comments
- line 1 of code
- line 2 of code
- line 3 of code
-
-
-```
-
-
-### Block code "fences"
-
-Use "fences" ```` ``` ```` to block in multiple lines of code.
-
-
-```
-
-### Syntax highlighting
-
-GFM, or "GitHub Flavored Markdown" also supports syntax highlighting. To activate it, simply add the file extension of the language you want to use directly after the first code "fence", ` ```js `, and syntax highlighting will automatically be applied in the rendered HTML. For example, to apply syntax highlighting to JavaScript code:
-
-
-
-Renders to:
-
-```js
-grunt.initConfig({
- assemble: {
- options: {
- assets: 'docs/assets',
- data: 'src/data/*.{json,yml}',
- helpers: 'src/custom-helpers.js',
- partials: ['src/partials/**/*.{hbs,md}']
- },
- pages: {
- options: {
- layout: 'default.hbs'
- },
- files: {
- './': ['src/templates/pages/index.hbs']
- }
- }
- }
-};
-```
-
-## Tables
-Tables are created by adding pipes as dividers between each cell, and by adding a line of dashes (also separated by bars) beneath the header. Note that the pipes do not need to be vertically aligned.
-
-
-```markdown
-| Option | Description |
-| ------ | ----------- |
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-```
-
-Renders to:
-
-| Option | Description |
-| ------ | ----------- |
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-
-And this HTML:
-
-```html
-
-
-
Option
-
Description
-
-
-
data
-
path to data files to supply the data that will be passed into templates.
-
-
-
engine
-
engine to be used for processing templates. Handlebars is the default.
-
-
-
ext
-
extension to be used for dest files.
-
-
-```
-
-### Right aligned text
-
-Adding a colon on the right side of the dashes below any heading will right align text for that column.
-
-```markdown
-| Option | Description |
-| ------:| -----------:|
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-```
-
-| Option | Description |
-| ------:| -----------:|
-| data | path to data files to supply the data that will be passed into templates. |
-| engine | engine to be used for processing templates. Handlebars is the default. |
-| ext | extension to be used for dest files. |
-
-## Links
-
-### Basic link
-
-```markdown
-[Assemble](http://assemble.io)
-```
-
-Renders to (hover over the link, there is no tooltip):
-
-[Assemble](http://assemble.io)
-
-HTML:
-
-```html
-Assemble
-```
-
-
-### Add a title
-
-```markdown
-[Upstage](https://github.com/upstage/ "Visit Upstage!")
-```
-
-Renders to (hover over the link, there should be a tooltip):
-
-[Upstage](https://github.com/upstage/ "Visit Upstage!")
-
-HTML:
-
-```html
-Upstage
-```
-
-### Named Anchors
-
-Named anchors enable you to jump to the specified anchor point on the same page. For example, each of these chapters:
-
-```markdown
-# Table of Contents
- * [Chapter 1](#chapter-1)
- * [Chapter 2](#chapter-2)
- * [Chapter 3](#chapter-3)
-```
-will jump to these sections:
-
-```markdown
-## Chapter 1
-Content for chapter one.
-
-## Chapter 2
-Content for chapter one.
-
-## Chapter 3
-Content for chapter one.
-```
-**NOTE** that specific placement of the anchor tag seems to be arbitrary. They are placed inline here since it seems to be unobtrusive, and it works.
-
-
-## Images {#images}
-Images have a similar syntax to links but include a preceding exclamation point.
-
-```markdown
-
-```
-
-
-or
-```markdown
-
-```
-
-
-Like links, Images also have a footnote style syntax
-
-### Alternative usage : note images
-
-```markdown
-![Alt text][id]
-```
-![Alt text][id]
-
-With a reference later in the document defining the URL location:
-
-[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
-
- [id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
-
-### Resizing image
-
-Add HTTP parameters `width` and/or `height` to the link image to resize the image. Values are CSS values (default is `auto`).
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-```markdown
-
-```
-
-
-
-### Add CSS classes
-
-Add a HTTP `classes` parameter to the link image to add CSS classes. `shadow`and `border` are available but you could define other ones.
-
-```markdown
-
-```
-
-
-```markdown
-
-```
-
-
-```markdown
-
-```
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.en.md
deleted file mode 100644
index e59d6fdb6..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.en.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Menu extra shortcuts
-weight: 25
----
-
-You can define additional menu entries or shortcuts in the navigation menu without any link to content.
-
-## Basic configuration
-
-Edit the website configuration `config.toml` and add a `[[menu.shortcuts]]` entry for each link your want to add.
-
-Example from the current website:
-
- [[menu.shortcuts]]
- name = " Github repo"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[menu.shortcuts]]
- name = " Showcases"
- url = "/showcase"
- weight = 11
-
- [[menu.shortcuts]]
- name = " Hugo Documentation"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[menu.shortcuts]]
- name = " Credits"
- url = "/credits"
- weight = 30
-
-By default, shortcuts are preceded by a title. This title can be disabled by setting `disableShortcutsTitle=true`.
-However, if you want to keep the title but change its value, it can be overriden by changing your local i18n translation string configuration.
-
-For example, in your local `i18n/en.toml` file, add the following content
-
- [Shortcuts-Title]
- other = ""
-
-Read more about [hugo menu](https://gohugo.io/extras/menus/) and [hugo i18n translation strings](https://gohugo.io/content-management/multilingual/#translation-of-strings)
-
-## Configuration for Multilingual mode {#i18n}
-
-When using a multilingual website, you can set different menus for each language. In the `config.toml` file, prefix your menu configuration by `Languages.`.
-
-
-Example from the current website:
-
- [Languages]
- [Languages.en]
- title = "Documentation for Hugo Learn Theme"
- weight = 1
- languageName = "English"
-
- [[Languages.en.menu.shortcuts]]
- name = " Github repo"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[Languages.en.menu.shortcuts]]
- name = " Showcases"
- url = "/showcase"
- weight = 11
-
- [[Languages.en.menu.shortcuts]]
- name = " Hugo Documentation"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[Languages.en.menu.shortcuts]]
- name = " Credits"
- url = "/credits"
- weight = 30
-
- [Languages.fr]
- title = "Documentation du thème Hugo Learn"
- weight = 2
- languageName = "Français"
-
- [[Languages.fr.menu.shortcuts]]
- name = " Repo Github"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[Languages.fr.menu.shortcuts]]
- name = " Vitrine"
- url = "/showcase"
- weight = 11
-
- [[Languages.fr.menu.shortcuts]]
- name = " Documentation Hugo"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[Languages.fr.menu.shortcuts]]
- name = " Crédits"
- url = "/credits"
- weight = 30
-
-Read more about [hugo menu](https://gohugo.io/extras/menus/) and [hugo multilingual menus](https://gohugo.io/content-management/multilingual/#menus)
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.fr.md
deleted file mode 100644
index 886067906..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/menushortcuts.fr.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Raccourcis du menu
-weight: 25
----
-
-Vous pouvez définir des entrées ou raccourcis supplémentaires dans le menu sans avoir besoin d'être lié à un contenu du site.
-
-## Configuration simple
-
-Editez le fichier de configuration `config.toml` et ajoutez une entrée `[[menu.shortcuts]]` pour chaque lien que vous voulez ajouter.
-
-Exemple pour ce site:
-
- [[menu.shortcuts]]
- name = " Github repo"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[menu.shortcuts]]
- name = " Showcases"
- url = "/showcase"
- weight = 11
-
- [[menu.shortcuts]]
- name = " Hugo Documentation"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[menu.shortcuts]]
- name = " Credits"
- url = "/credits"
- weight = 30
-
-Par défaut, les raccourcis sont précédés par un titre. Ce titre peut être désactivé en ajouter le paramètre `disableShortcutsTitle=true` dans la section `params` de votre `config.toml`.
-Cependant, si vous voulez garder le titre mais changer sa valeur, vous pouvez modifier votre configuration multilangue locale en changeant les *translation string*.
-
-Par exemple, dans votre fichier local `i18n/en.toml`, ajouter le contenu
-
- [Shortcuts-Title]
- other = ""
-
-Plus d'infos sur [les menus Hugo](https://gohugo.io/extras/menus/) et sur [les translations strings](https://gohugo.io/content-management/multilingual/#translation-of-strings)
-
-## Configuration pour le mode multi-langue {#i18n}
-
-Quand vous utilisez un site multi-langue, vous pouvez avoir des menus différents pour chaque langage. Dans le fichier de configuration `config.toml`, préfixez votre configuration par `Languages.`.
-
-
-Par exemple, avec ce site :
-
- [Languages]
- [Languages.en]
- title = "Documentation for Hugo Learn Theme"
- weight = 1
- languageName = "English"
-
- [[Languages.en.menu.shortcuts]]
- name = " Github repo"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[Languages.en.menu.shortcuts]]
- name = " Showcases"
- url = "/showcase"
- weight = 11
-
- [[Languages.en.menu.shortcuts]]
- name = " Hugo Documentation"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[Languages.en.menu.shortcuts]]
- name = " Credits"
- url = "/credits"
- weight = 30
-
- [Languages.fr]
- title = "Documentation du thème Hugo Learn"
- weight = 2
- languageName = "Français"
-
- [[Languages.fr.menu.shortcuts]]
- name = " Repo Github"
- identifier = "ds"
- url = "https://github.com/matcornic/hugo-theme-learn"
- weight = 10
-
- [[Languages.fr.menu.shortcuts]]
- name = " Vitrine"
- url = "/showcase"
- weight = 11
-
- [[Languages.fr.menu.shortcuts]]
- name = " Documentation Hugo"
- identifier = "hugodoc"
- url = "https://gohugo.io/"
- weight = 20
-
- [[Languages.fr.menu.shortcuts]]
- name = " Crédits"
- url = "/credits"
- weight = 30
-
-Plus d'infos sur [les menus Hugo](https://gohugo.io/extras/menus/) et les [menus multi-langue Hugo](https://gohugo.io/content-management/multilingual/#menus)
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.en.md
deleted file mode 100644
index ad6a1b5a8..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.en.md
+++ /dev/null
@@ -1,166 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Pages organization
-weight: 5
----
-
-In **Hugo**, pages are the core of your site. Once it is configured, pages are definitely the added value to your documentation site.
-
-## Folders
-
-Organize your site like [any other Hugo project](https://gohugo.io/content/organization/). Typically, you will have a *content* folder with all your pages.
-
- content
- ├── level-one
- │ ├── level-two
- │ │ ├── level-three
- │ │ │ ├── level-four
- │ │ │ │ ├── _index.md <-- /level-one/level-two/level-three/level-four
- │ │ │ │ ├── page-4-a.md <-- /level-one/level-two/level-three/level-four/page-4-a
- │ │ │ │ ├── page-4-b.md <-- /level-one/level-two/level-three/level-four/page-4-b
- │ │ │ │ └── page-4-c.md <-- /level-one/level-two/level-three/level-four/page-4-c
- │ │ │ ├── _index.md <-- /level-one/level-two/level-three
- │ │ │ ├── page-3-a.md <-- /level-one/level-two/level-three/page-3-a
- │ │ │ ├── page-3-b.md <-- /level-one/level-two/level-three/page-3-b
- │ │ │ └── page-3-c.md <-- /level-one/level-two/level-three/page-3-c
- │ │ ├── _index.md <-- /level-one/level-two
- │ │ ├── page-2-a.md <-- /level-one/level-two/page-2-a
- │ │ ├── page-2-b.md <-- /level-one/level-two/page-2-b
- │ │ └── page-2-c.md <-- /level-one/level-two/page-2-c
- │ ├── _index.md <-- /level-one
- │ ├── page-1-a.md <-- /level-one/page-1-a
- │ ├── page-1-b.md <-- /level-one/page-1-b
- │ └── page-1-c.md <-- /level-one/page-1-c
- ├── _index.md <-- /
- └── page-top.md <-- /page-top
-
-{{% notice note %}}
-`_index.md` is required in each folder, it’s your “folder home page”
-{{% /notice %}}
-
-## Types
-
-**Hugo-theme-learn** defines two types of pages. *Default* and *Chapter*. Both can be used at any level of the documentation, the only difference being layout display.
-
-A **Chapter** displays a page meant to be used as introduction for a set of child pages. Commonly, it contains a simple title and a catch line to define content that can be found under it.
-You can define any HTML as prefix for the menu. In the example below, it's just a number but that could be an [icon](https://fortawesome.github.io/Font-Awesome/).
-
-
-
-```markdown
-+++
-title = "Basics"
-chapter = true
-weight = 5
-pre = "1. "
-+++
-
-### Chapter 1
-
-# Basics
-
-Discover what this Hugo theme is all about and the core-concepts behind it.
-```
-
-To tell **Hugo-theme-learn** to consider a page as a chapter, set `chapter=true` in the Front Matter of the page.
-
-A **Default** page is any other content page.
-
-
-
-```toml
-+++
-title = "Installation"
-weight = 15
-+++
-```
-
-The following steps are here to help you initialize your new website. If you don't know Hugo at all, we strongly suggest you to train by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
-
-## Create your project
-
-Hugo provides a `new` command to create a new website.
-
-```
-hugo new site
-```
-
-**Hugo-theme-learn** provides [archetypes]({{< relref "cont/archetypes.en.md" >}}) to help you create this kind of pages.
-
-## Front Matter configuration
-
-Each Hugo page has to define a [Front Matter](https://gohugo.io/content/front-matter/) in *yaml*, *toml* or *json*.
-
-**Hugo-theme-learn** uses the following parameters on top of Hugo ones :
-
-```toml
-+++
-# Table of content (toc) is enabled by default. Set this parameter to true to disable it.
-# Note: Toc is always disabled for chapter pages
-disableToc = "false"
-# If set, this will be used for the page's menu entry (instead of the `title` attribute)
-menuTitle = ""
-# The title of the page in menu will be prefixed by this HTML content
-pre = ""
-# The title of the page in menu will be postfixed by this HTML content
-post = ""
-# Set the page as a chapter, changing the way it's displayed
-chapter = false
-# Hide a menu entry by setting this to true
-hidden = false
-# Display name of this page modifier. If set, it will be displayed in the footer.
-LastModifierDisplayName = ""
-# Email of this page modifier. If set with LastModifierDisplayName, it will be displayed in the footer
-LastModifierEmail = ""
-+++
-```
-
-### Add icon to a menu entry
-
-In the page frontmatter, add a `pre` param to insert any HTML code before the menu label. The example below uses the Github icon.
-
-```toml
-+++
-title = "Github repo"
-pre = " "
-+++
-```
-
-
-
-### Ordering sibling menu/page entries
-
-Hugo provides a [flexible way](https://gohugo.io/content/ordering/) to handle order for your pages.
-
-The simplest way is to set `weight` parameter to a number.
-
-```toml
-+++
-title = "My page"
-weight = 5
-+++
-```
-
-### Using a custom title for menu entries
-
-By default, **Hugo-theme-learn** will use a page's `title` attribute for the menu item (or `linkTitle` if defined).
-
-But a page's title has to be descriptive on its own while the menu is a hierarchy.
-We've added the `menuTitle` parameter for that purpose:
-
-For example (for a page named `content/install/linux.md`):
-
-```toml
-+++
-title = "Install on Linux"
-menuTitle = "Linux"
-+++
-```
-
-## Homepage
-
-To configure your home page, you basically have three choices:
-
-1. Create an `_index.md` document in `content` folder and fill the file with *Markdown content*
-2. Create an `index.html` file in the `static` folder and fill the file with *HTML content*
-3. Configure your server to automatically redirect home page to one your documentation page
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.fr.md
deleted file mode 100644
index 50c6f256b..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/pages/_index.fr.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Organisation des pages
-weight: 5
----
-
-Dans **Hugo**, les pages sont le cœur de votre site. Une fois configurées, les pages sont la valeur ajoutée de votre site de documentation.
-
-## Dossiers
-
-Organisez votre site comme n'importe quel autre [projet Hugo](https://gohugo.io/content/organization/). Typiquement, vous allez avoir un dossier *content* avec vos pages.
-
- content
- ├── niveau-un
- │ ├── niveau-deux
- │ │ ├── niveau-trois
- │ │ │ ├── niveau-quatre
- │ │ │ │ ├── _index.md <-- /niveau-un/niveau-deux/niveau-trois/niveau-quatre
- │ │ │ │ ├── page-4-a.md <-- /niveau-un/niveau-deux/niveau-trois/niveau-quatre/page-4-a
- │ │ │ │ ├── page-4-b.md <-- /niveau-un/niveau-deux/niveau-trois/niveau-quatre/page-4-b
- │ │ │ │ └── page-4-c.md <-- /niveau-un/niveau-deux/niveau-trois/niveau-quatre/page-4-c
- │ │ │ ├── _index.md <-- /niveau-un/niveau-deux/niveau-trois
- │ │ │ ├── page-3-a.md <-- /niveau-un/niveau-deux/niveau-trois/page-3-a
- │ │ │ ├── page-3-b.md <-- /niveau-un/niveau-deux/niveau-trois/page-3-b
- │ │ │ └── page-3-c.md <-- /niveau-un/niveau-deux/niveau-trois/page-3-c
- │ │ ├── _index.md <-- /niveau-un/niveau-deux
- │ │ ├── page-2-a.md <-- /niveau-un/niveau-deux/page-2-a
- │ │ ├── page-2-b.md <-- /niveau-un/niveau-deux/page-2-b
- │ │ └── page-2-c.md <-- /niveau-un/niveau-deux/page-2-c
- │ ├── _index.md <-- /niveau-un
- │ ├── page-1-a.md <-- /niveau-un/page-1-a
- │ ├── page-1-b.md <-- /niveau-un/page-1-b
- │ └── page-1-c.md <-- /niveau-un/page-1-c
- ├── _index.md <-- /
- └── premiere-page.md <-- /premiere-page
-
-{{% notice note %}}
-Le fichier `_index.md` est obligatoire dans chaque dossier, c'est en quelque sorte votre page d'accueil pour le dossier.
-{{% /notice %}}
-
-## Types
-
-**Hugo-theme-learn** définit deux types de pages. *Défaut* et *Chapitre*. Les deux sont utilisables à n'importe quel niveau du site, la seule différence est dans l'affichage.
-
-Un **Chapitre** affiche une page vouée à être une introduction pour un ensemble de pages filles. Habituellement, il va seulement contenir un titre et un résumé de la section.
-Vous pouvez définir n'importe quel contenu HTML comme préfixe de l'entrée du menu. Dans l'exemple ci-dessous, c'est juste un nombre mais vous pourriez utiliser une [icône](https://fortawesome.github.io/Font-Awesome/).
-
-
-
-```markdown
-+++
-title = "Démarrage"
-weight = 5
-pre = "1. "
-chapter = true
-+++
-
-### Chapitre 1
-
-# Démarrage
-
-Découvrez comment utiliser ce thème Hugo et apprenez en les concepts
-```
-
-Pour dire à **Hugo-theme-learn** de considérer la page comme un chapitre, configure `chapter=true` dans le Front Matter de la page.
-
-Une page **Défaut** est n'importe quelle autre page.
-
-
-
- +++
- title = "Installation"
- weight = 15
- +++
-
- The following steps are here to help you initialize your new website. If you don't know Hugo at all, we strongly suggest you to train by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
-
- ## Create your project
-
- Hugo provides a `new` command to create a new website.
-
- ```
- hugo new site
- ```
-
-**Hugo-theme-learn** fournit des [archétypes]({{< relref "cont/archetypes.fr.md" >}}) pour vous aider à créer ce type de pages.
-
-## Configuration des Front Matter
-
-Chaque page Hugo doit définir un [Front Matter](https://gohugo.io/content/front-matter/) dans le format *yaml*, *toml* ou *json*.
-
-**Hugo-theme-learn** utilise les paramètres suivant en plus de ceux définis par Hugo:
-
-```toml
-+++
-# Le Sommaire (table of content = toc) est activé par défaut. Modifier ce paramètre à true pour le désactiver.
-# Note: Le sommaire est toujours désactivé pour les chapitres
-disableToc = "false"
-# Le titre de la page dans le menu sera préfixé par ce contentu HTML
-pre = ""
-# Le titre de la page dans le menu sera suffixé par ce contentu HTML
-post = ""
-# Modifier le type de la page pour changer l'affichage
-chapter = false
-# Cache la page du menu
-hidden = false
-# Nom de la personne qui a modifié la page. Quand configuré, sera affiché dans le pied de page.
-LastModifierDisplayName = ""
-# Email de la personne qui a modifié la page. Quand configuré, sera affiché dans le pied de page.
-LastModifierEmail = ""
-+++
-```
-
-### Ajouter une icône à une entrée du menu
-
-Dans le Front Matter, ajouter un paramètre `pre` pour insérer du code HTML qui s'affichera avant le label du menu. L'exemple ci-dessous utilise l'icône de Github.
-
-```toml
-+++
-title = "Repo Github"
-pre = " "
-+++
-```
-
-
-
-### Ordonner les entrées dans le menu
-
-Hugo permet de modifier facilement [l'ordre des menu](https://gohugo.io/content/ordering/).
-
-La manière la plus simple est de configurer le paramètre `weight` avec un nombre.
-
-```toml
-+++
-title = "Ma page"
-weight = 5
-+++
-```
-
-## Page d'accueil
-
-Pour configurer votre page d'accueil, vous avez trois choix:
-
-1. Créer une page `_index.md` dans le dossier `content` et remplissez le fichier avec du *contenu Markdown*
-2. Créer une page `index.html` dans le dossier `static` et remplissez le fichier avec du *contenu HTML*
-3. Configurez votre serveur pour automatiquement rediriger la page d'accueil vers l'une de vos pages.
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png b/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png
deleted file mode 100644
index a8dd653ab..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/frontmatter-icon.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png b/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png
deleted file mode 100644
index 593d7e229..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-chapter.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-default.png b/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-default.png
deleted file mode 100644
index 396e788ec..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/cont/pages/images/pages-default.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md
deleted file mode 100644
index ed1fe72c3..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/syntaxhighlight.en.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-date: 2020-06-01T13:31:12+01:00
-title: Code highlighting
-weight: 16
----
-
-Learn theme uses [highlight.js](https://highlightjs.org/) to provide code syntax highlighting.
-
-## Markdown syntax
-
-Wrap the code block with three backticks and the name of the language. Highlight will try to auto detect the language if one is not provided.
-
-
-```plaintext
- ```json
- [
- {
- "title": "apples",
- "count": [12000, 20000],
- "description": {"text": "...", "sensitive": false}
- },
- {
- "title": "oranges",
- "count": [17500, null],
- "description": {"text": "...", "sensitive": false}
- }
- ]
- ```
-```
-
-
-Renders to:
-
-```json
-[
- {
- "title": "apples",
- "count": [12000, 20000],
- "description": {"text": "...", "sensitive": false}
- },
- {
- "title": "oranges",
- "count": [17500, null],
- "description": {"text": "...", "sensitive": false}
- }
-]
-```
-
-## Supported languages
-
-Learn theme ships with its own version of highlight.js to support offline browsing. The included package supports 38 common languages, as described on the [highlight.js download page](https://highlightjs.org/download/).
-
-## Identifying failed language detection
-
-Highlight will write a warning to the browser console if a requested language was not found. For example, the following code block references an imaginary language `foo`. An error will be output to the console on this page.
-
-```plaintext
- ```foo
- bar
- ```
-```
-
-```nohighlight
-Could not find the language 'foo', did you forget to load/include a language module?(anonymous) @ highlight.pack.js
-```
-
-## Supporting additional languages
-
-To support languages other than the 38 common languages included in the default highlight.js you will need to download your own version of highlight.js and add it to your site content.
-
-### Download custom highlight.js
-
-Visit [https://highlightjs.org/download/](https://highlightjs.org/download/) and select your desired language support. Note that more languages means greater package size.
-
-### Add custom highlight.js to static resources
-
-Inside the zip archive downloaded from highlight.js extract the file named `highlight.pack.js`. Move this file to the **new** location
-
-```nohighlight
-static/js/highlight.pack.js
-```
-
-**Do not** replace the existing file at `themes/hugo-theme-learn/static/js/highlight.pack.js`.
-
-Including the file in the correct path will override the theme default highlight.pack.js and prevent issues caused in the future if the theme default file is updated.
-
-## Further usage information
-
-See [https://highlightjs.org/usage/](https://highlightjs.org/usage/)
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/tags.en.md b/documentation/staging/themes/learn/exampleSite/content/cont/tags.en.md
deleted file mode 100644
index 02972bb6b..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/tags.en.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-date: 2018-11-29T08:41:44+01:00
-title: Tags
-weight: 40
-tags: ["documentation", "tutorial"]
----
-
-*Learn theme* support one default taxonomy of gohugo: the *tag* feature.
-
-## Configuration
-
-Just add tags to any page:
-
-```markdown
----
-date: 2018-11-29T08:41:44+01:00
-title: Theme tutorial
-weight: 15
-tags: ["tutorial", "theme"]
----
-```
-
-## Behavior
-
-
-The tags are displayed at the top of the page, in their insertion order.
-
-Each tag is a link to a *Taxonomy* page displaying all the articles with the given tag.
-
-## List all the tags
-
-In the `config.toml` file you can add a shortcut to display all the tags
-
-```toml
-[[menu.shortcuts]]
-name = " Tags"
-url = "/tags"
-weight = 30
-```
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/cont/tags.fr.md b/documentation/staging/themes/learn/exampleSite/content/cont/tags.fr.md
deleted file mode 100644
index d19b396c6..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/cont/tags.fr.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-date: 2018-11-29T08:41:44+01:00
-title: Tags
-weight: 40
-tags: ["documentation", "tutorial"]
----
-
-
-Le *thème Learn* supporte une des taxonomy par défaut de GoHugo : les tags.
-
-## Configuration
-
-Il suffit d'ajouter un tableau de tags sur la page :
-
-```markdown
----
-date: 2018-11-29T08:41:44+01:00
-title: Tutoriel pour le thème
-weight: 15
-tags: ["tutoriel", "theme"]
----
-```
-
-## Comportement
-
-Les tags sont affichés en haut de la page, dans l'ordre dans lequel ils ont été saisis.
-
-Chaque tag est un lien vers une page *Taxonomy*, qui affiche tous les article avec ce tag.
-
-
-## Liste des tags
-
-Il est possible de rajouter un raccourci dans le fichier `config.toml` afin d'afficher une page listant tous les tags
-
-```toml
-[[menu.shortcuts]]
-name = " Tags"
-url = "/tags"
-weight = 30
-```
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/credits.en.md b/documentation/staging/themes/learn/exampleSite/content/credits.en.md
deleted file mode 100644
index 1a489fcfc..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/credits.en.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Credits
-disableToc: true
----
-
-## Contributors
-
-Thanks to them for making Open Source Software a better place !
-
-{{% ghcontributors "https://api.github.com/repos/matcornic/hugo-theme-learn/contributors?per_page=100" %}}
-
-And a special thanks to [@vjeantet](https://github.com/vjeantet) for his work on [docdock](https://github.com/vjeantet/hugo-theme-docdock), a fork of hugo-theme-learn. v2.0.0 of this theme is inspired by his work.
-
-## Packages and libraries
-* [mermaid](https://knsv.github.io/mermaid) - generation of diagram and flowchart from text in a similar manner as markdown
-* [font awesome](http://fontawesome.io/) - the iconic font and CSS framework
-* [jQuery](https://jquery.com) - The Write Less, Do More, JavaScript Library
-* [lunr](https://lunrjs.com) - Lunr enables you to provide a great search experience without the need for external, server-side, search services...
-* [horsey](https://bevacqua.github.io/horsey/) - Progressive and customizable autocomplete component
-* [clipboard.js](https://zenorocha.github.io/clipboard.js) - copy text to clipboard
-* [highlight.js](https://highlightjs.org) - Javascript syntax highlighter
-* [modernizr](https://modernizr.com) - A JavaScript toolkit that allows web developers to use new CSS3 and HTML5 features while maintaining a fine level of control over browsers that don't support
-
-## Tooling
-
-* [Netlify](https://www.netlify.com) - Continuous deployement and hosting of this documentation
-* [Hugo](https://gohugo.io/)
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/credits.fr.md b/documentation/staging/themes/learn/exampleSite/content/credits.fr.md
deleted file mode 100644
index 536f09381..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/credits.fr.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Crédits
-disableToc: true
----
-
-## Contributeurs
-
-Merci à eux de rendre le monde Open Source meilleur !
-
-{{% ghcontributors "https://api.github.com/repos/matcornic/hugo-theme-learn/contributors?per_page=100" %}}
-
-Et un grand merci à [@vjeantet](https://github.com/vjeantet) pour son travail sur [docdock](https://github.com/vjeantet/hugo-theme-docdock), un fork de _hugo-theme-learn_. La v2.0.0 du thème est en grande partie inspirée de son travail.
-
-## Packages et librairies
-* [mermaid](https://knsv.github.io/mermaid) - géneration de diagrames et graphiques à partir de texte similaire à Markdown
-* [font awesome](http://fontawesome.io/) - Le framework de polices iconiques
-* [jQuery](https://jquery.com) - La plus connue des librairies Javascript
-* [lunr](https://lunrjs.com) - Lunr fournit des fonctions de recherche sans service externe
-* [horsey](https://bevacqua.github.io/horsey/) - Autocomplétion de composants (utiliser pour les suggestions de recherche)
-* [clipboard.js](https://zenorocha.github.io/clipboard.js) - Copier le texte dans le presse-papier
-* [highlight.js](https://highlightjs.org) - Mise en valeur de syntaxes
-* [modernizr](https://modernizr.com) - Une boite à outil Javascript qui permet aux développeurs d'utiliser les dernières fonctionnalités de CSS et HTML5, même sur de vieux navigateurs.
-
-## Outils
-
-* [Netlify](https://www.netlify.com) - Déploiement continue et hébergement de cette documentation
-* [Hugo](https://gohugo.io/)
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.en.md
deleted file mode 100644
index 754bb0f0c..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.en.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Shortcodes
-pre: "3. "
-weight: 15
----
-
-Hugo uses Markdown for its simple content format. However, there are a lot of things that Markdown doesn’t support well. You could use pure HTML to expand possibilities.
-
-But this happens to be a bad idea. Everyone uses Markdown because it's pure and simple to read even non-rendered. You should avoid HTML to keep it as simple as possible.
-
-To avoid this limitations, Hugo created [shortcodes](https://gohugo.io/extras/shortcodes/). A shortcode is a simple snippet inside a page.
-
-**Hugo-theme-learn** provides multiple shortcodes on top of existing ones.
-
-{{%children style="h2" description="true" %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.fr.md
deleted file mode 100644
index b084d9bfd..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/_index.fr.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-date: 2016-04-09T16:50:16+02:00
-title: Shortcodes
-pre: "3. "
-weight: 15
----
-
-Hugo utilise Markdown pour son format simple. Cependant, il y a beaucoup de chose que Markdown ne supporte pas bien. On pourrait utiliser du HTML pur pour améliorer les capacité du Markdown.
-
-Mais c'est probablement une mauvaise idée. Tout le monde utilise le Markdown parce que c'est pur et simple à lire même lorsqu'il est affiché en texte brut. Vous devez éviter le HTML autant que possible pour garder le contenu simple.
-
-Cependant, pour éviter les limitations, Hugo a créé les [shortcodes](https://gohugo.io/extras/shortcodes/). Un shortcode est un bout de code (*snippet*) dans une page.
-
-**Hugo-theme-learn** fournit de multiple shortcodes en plus de ceux existant.
-
-{{%children style="h2" description="true" %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3 b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3
deleted file mode 100644
index 94e3d0e53..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/BachGavotteShort.mp3 and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf
deleted file mode 100644
index 97377e99b..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/Carroll_AliceAuPaysDesMerveilles.pdf and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf
deleted file mode 100644
index e589c73e9..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/adivorciarsetoca00cape.pdf and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png
deleted file mode 100644
index 48acf346c..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/hugo.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4 b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4
deleted file mode 100644
index 9f1fe5645..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.files/movieselectricsheep-flock-244-32500-2.mp4 and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.md
deleted file mode 100644
index 8a2429cf3..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.en.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Attachments
-description : "The Attachments shortcode displays a list of files attached to a page."
----
-
-The Attachments shortcode displays a list of files attached to a page.
-
-{{% attachments /%}}
-
-## Usage
-
-The shortcurt lists files found in a **specific folder**.
-Currently, it support two implementations for pages
-
-1. If your page is a markdown file, attachements must be placed in a **folder** named like your page and ending with **.files**.
-
- > * content
- > * _index.md
- > * page.files
- > * attachment.pdf
- > * page.md
-
-2. If your page is a **folder**, attachements must be placed in a nested **'files'** folder.
-
- > * content
- > * _index.md
- > * page
- > * index.md
- > * files
- > * attachment.pdf
-
-Be aware that if you use a multilingual website, you will need to have as many folders as languages.
-
-That's all!
-
-### Parameters
-
-| Parameter | Default | Description |
-|:--|:--|:--|
-| title | "Attachments" | List's title |
-| style | "" | Choose between "orange", "grey", "blue" and "green" for nice style |
-| pattern | ".*" | A regular expressions, used to filter the attachments by file name.
The **pattern** parameter value must be [regular expressions](https://en.wikipedia.org/wiki/Regular_expression).
-
-For example:
-
-* To match a file suffix of 'jpg', use **.*jpg** (not *.jpg).
-* To match file names ending in 'jpg' or 'png', use **.*(jpg|png)**
-
-### Examples
-
-#### List of attachments ending in pdf or mp4
-
-
- {{%/*attachments title="Related files" pattern=".*(pdf|mp4)"/*/%}}
-
-renders as
-
-{{%attachments title="Related files" pattern=".*(pdf|mp4)"/%}}
-
-#### Colored styled box
-
- {{%/*attachments style="orange" /*/%}}
-
-renders as
-
-{{% attachments style="orange" /%}}
-
-
- {{%/*attachments style="grey" /*/%}}
-
-renders as
-
-{{% attachments style="grey" /%}}
-
- {{%/*attachments style="blue" /*/%}}
-
-renders as
-
-{{% attachments style="blue" /%}}
-
- {{%/*attachments style="green" /*/%}}
-
-renders as
-
-{{% attachments style="green" /%}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3 b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3
deleted file mode 100644
index 94e3d0e53..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/BachGavotteShort.mp3 and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf
deleted file mode 100644
index 97377e99b..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/Carroll_AliceAuPaysDesMerveilles.pdf and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf
deleted file mode 100644
index e589c73e9..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/adivorciarsetoca00cape.pdf and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png
deleted file mode 100644
index 48acf346c..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/hugo.png and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4 b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4
deleted file mode 100644
index 9f1fe5645..000000000
Binary files a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.files/movieselectricsheep-flock-244-32500-2.mp4 and /dev/null differ
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.md
deleted file mode 100644
index c24093915..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/attachments.fr.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Attachments (Pièces jointes)
-description : "The Attachments shortcode displays a list of files attached to a page."
----
-
-Le shortcode *Attachments* affiche une liste de pièces jointes d'une page.
-
-{{% attachments /%}}
-
-## Utilisation
-
-Le shortcode affiche la liste de fichiers trouvés dans un **dossier spécifique**
-A l'heure actuelle, il supporte deux implémentations
-
-1. Si votre page est un fichier Markdown, les pièces jointes doivent être placée dans un **dossier** nommé comme le nom de la page et suffixé par **.files**.
-
- > * content
- > * _index.md
- > * page.files
- > * attachment.pdf
- > * page.md
-
-2. Si votre page est un **dossier**, les pièces jointes doivent être placées dans un dossier fils **'files'**.
-
- > * content
- > * _index.md
- > * page
- > * index.md
- > * files
- > * attachment.pdf
-
-Attention, si votre site est multi-langue, vous devrez avec autant de dossier qu'il y a de langues.
-
-C'est tout !
-
-### Paramètres
-
-| Paramètre | Défaut | Description |
-|:--|:--|:--|
-| title | "Pièces jointes" | Titre de la liste |
-| style | "" | Choisir entre "orange", "grey", "blue" et "green" pour un style plus sympa |
-| pattern | ".*" | Une expression régulière, utilisée pour filtrer les pièces jointes par leur nom de fichier.
Le paramètre **pattern** doit être une [expression régulière](https://en.wikipedia.org/wiki/Regular_expression).
-
-Par exemple:
-
-* Pour trouver les fichiers avec le suffixe 'jpg', utilisez **.*jpg** (pas *.jpg).
-* Pour trouver les fichiers avec les suffixe 'jpg' ou 'png', utilisez **.*(jpg|png)**
-
-### Exemples
-
-#### Lister les pièces jointes de type pdf ou mp4
-
-
- {{%/*attachments title="Fichiers associés" pattern=".*(pdf|mp4)"/*/%}}
-
-s'affiche comme
-
-{{%attachments title="Fichiers associés" pattern=".*(pdf|mp4)"/%}}
-
-#### Modifier le style
-
- {{%/*attachments style="orange" /*/%}}
-
-s'affiche comme
-
-{{% attachments style="orange" /%}}
-
-
- {{%/*attachments style="grey" /*/%}}
-
-s'affiche comme
-
-{{% attachments style="grey" /%}}
-
- {{%/*attachments style="blue" /*/%}}
-
-s'affiche comme
-
-{{% attachments style="blue" /%}}
-
- {{%/*attachments style="green" /*/%}}
-
-s'affiche comme
-
-{{% attachments style="green" /%}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.en.md
deleted file mode 100644
index 9fb92bd98..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.en.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Button
-description : "Nice buttons on your page."
----
-
-A button is a just a clickable button with optional icon.
-
-```
-{{%/* button href="https://getgrav.org/" */%}}Get Grav{{%/* /button */%}}
-{{%/* button href="https://getgrav.org/" icon="fas fa-download" */%}}Get Grav with icon{{%/* /button */%}}
-{{%/* button href="https://getgrav.org/" icon="fas fa-download" icon-position="right" */%}}Get Grav with icon right{{%/* /button */%}}
-```
-
-{{% button href="https://getgrav.org/" %}}Get Grav{{% /button %}}
-{{% button href="https://getgrav.org/" icon="fas fa-download" %}}Get Grav with icon{{% /button %}}
-{{% button href="https://getgrav.org/" icon="fas fa-download" icon-position="right" %}}Get Grav with icon right{{% /button %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.fr.md
deleted file mode 100644
index 66e55af75..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/button.fr.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Button (Bouton)
-description : "De beaux boutons sur votre page."
----
-
-Le shortcode *button* est simplement un bouton cliquable avec une icône optionnelle.
-
-```
-{{%/* button href="https://getgrav.org/" */%}}Téléchargez Grav{{%/* /button */%}}
-{{%/* button href="https://getgrav.org/" icon="fas fa-download" */%}}Téléchargez Grav avec icône{{%/* /button */%}}
-{{%/* button href="https://getgrav.org/" icon="fas fa-download" icon-position="right" */%}}Téléchargez Grav avec icône à droite{{%/* /button */%}}
-```
-
-{{% button href="https://getgrav.org/" %}}Téléchargez Grav{{% /button %}}
-{{% button href="https://getgrav.org/" icon="fas fa-download" %}}Téléchargez Grav avec icône{{% /button %}}
-{{% button href="https://getgrav.org/" icon="fas fa-download" icon-position="right" %}}Téléchargez Grav avec icône à droite{{% /button %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.en.md
deleted file mode 100644
index 17bdcfb1d..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.en.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title : Children
-description : List the child pages of a page
----
-
-Use the children shortcode to list the child pages of a page and the further descendants (children's children). By default, the shortcode displays links to the child pages.
-
-## Usage
-
-| Parameter | Default | Description |
-|:--|:--|:--|
-| page | _current_ | Specify the page name (section name) to display children for |
-| style | "li" | Choose the style used to display descendants. It could be any HTML tag name |
-| showhidden | "false" | When true, child pages hidden from the menu will be displayed |
-| description | "false" | Allows you to include a short text under each page in the list. When no description exists for the page, children shortcode takes the first 70 words of your content. [Read more info about summaries on gohugo.io](https://gohugo.io/content/summaries/) |
-| depth | 1 | Enter a number to specify the depth of descendants to display. For example, if the value is 2, the shortcode will display 2 levels of child pages. **Tips:** set 999 to get all descendants |
-| sort | none | Sort children by **Weight** - to sort on menu order, **Name** - to sort alphabetically on menu label, **Identifier** - to sort alphabetically on identifier set in frontmatter, and **URL** - to sort by URL |
-
-## Demo
-
- {{%/* children */%}}
-
-{{% children %}}
-
- {{%/* children description="true" */%}}
-
-{{%children description="true" %}}
-
- {{%/* children depth="3" showhidden="true" */%}}
-
-{{% children depth="3" showhidden="true" %}}
-
- {{%/* children style="h2" depth="3" description="true" */%}}
-
-{{% children style="h2" depth="3" description="true" %}}
-
- {{%/* children style="div" depth="999" */%}}
-
-{{% children style="div" depth="999" %}}
-
-
-
-
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md
deleted file mode 100644
index 672c5ad61..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/_index.fr.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title : Children (Pages filles)
-description : Liste les pages filles de la page
----
-
-Utilisez le shortcode *children* pour lister les pages filles de la page et tous ses déscendants (pages filles de pages filles). Par défaut, le shortcode affiche des liens vers les pages filles.
-
-## Utilisation
-
-| Paramètre | Défaut | Description |
-|:--|:--|:--|
-| page | _current_ | Spécifie le nom de la page (nom de la section) à afficher |
-| style | "li" | Choisi le style à utiliser pour afficher les descendants. Cela peut être n'importe quel balise HTML |
-| showhidden | "false" | Quand *true*, pages filles cachées dans le menu seront affichées quand même |
-| description | "false" | Permet d'inclure le texte de la description de la page sous chaque entré de la liste. quand aucune description existe pour la page, le shortcode prend les 70 premiers mots du contenu. [plus d'infos sur gohugo.io](https://gohugo.io/content/summaries/) |
-| depth | 1 | Nombre de descendants à afficher. Par exemple, si la valeur est 2, le shortcode va afficher 2 niveaux de pages filels. **Astuce:** Utilisez 999 pour avoir tous les descendants|
-| sort | | Tri les pages filles par
Weight - Poids
Name - Nom
Identifier - Trier alphabétiquement par identifiant configuré dans le front matter
URL - URL
|
-
-## Démo
-
- {{%/* children */%}}
-
-{{% children %}}
-
- {{%/* children description="true" */%}}
-
-{{%children description="true" %}}
-
- {{%/* children depth="3" showhidden="true" */%}}
-
-{{% children depth="3" showhidden="true" %}}
-
- {{%/* children style="h2" depth="3" description="true" */%}}
-
-{{% children style="h2" depth="3" description="true" %}}
-
- {{%/* children style="div" depth="999" */%}}
-
-{{% children style="div" depth="999" %}}
-
-
-
-
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md
deleted file mode 100644
index d0c5179db..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1"
-description = "This is a demo child page"
-+++
-
-This is a demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md
deleted file mode 100644
index 7737f5034..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md
deleted file mode 100644
index a4982f96e..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1"
-description = "This is a demo child page"
-+++
-
-This is a demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md
deleted file mode 100644
index e39cb5828..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md
deleted file mode 100644
index 5ce56f4da..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1"
-description = "This is a demo child page"
-+++
-
-This is a demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md
deleted file mode 100644
index 31d2cd118..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md
deleted file mode 100644
index d5d9ab277..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1-1"
-description = "This is a demo child page"
-+++
-
-This is a demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md
deleted file mode 100644
index 3b0f7f096..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1-1"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md
deleted file mode 100644
index 883b5b218..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1-1-1"
-description = "This is a demo child page"
-+++
-
-This is a demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md
deleted file mode 100644
index 5a1961725..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-1/children-1-1/children-1-1-1/children-1-1-1-1/children-1-1-1-1-1/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 1-1-1-1-1"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md
deleted file mode 100644
index a96140c25..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.en.md
+++ /dev/null
@@ -1,11 +0,0 @@
-+++
-title = "page 2"
-description = ""
-+++
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
- tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
- quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
- consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
- cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
- proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md
deleted file mode 100644
index a96140c25..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/_index.fr.md
+++ /dev/null
@@ -1,11 +0,0 @@
-+++
-title = "page 2"
-description = ""
-+++
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
- tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
- quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
- consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
- cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
- proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md
deleted file mode 100644
index f603d4c0c..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page test 3"
-description = "This is a page test"
-+++
-
-This is a test 3 demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md
deleted file mode 100644
index 6d649e807..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-2/test3.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page test 3"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo test 3
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md
deleted file mode 100644
index f36f8616e..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 3"
-description = "This is a demo child page"
-+++
-
-This is a demo child page, not displayed in the menu
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md
deleted file mode 100644
index 1501cc82b..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-3/_index.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page 3"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md
deleted file mode 100644
index b9f042d81..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.en.md
+++ /dev/null
@@ -1,7 +0,0 @@
-+++
-title = "page 4"
-description = "This is a demo child page"
-hidden = true
-+++
-
-This is a demo child page, not displayed in the menu
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md
deleted file mode 100644
index 6735e5041..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/children-4/_index.fr.md
+++ /dev/null
@@ -1,7 +0,0 @@
-+++
-title = "page 4"
-description = "Ceci est une page test"
-hidden = true
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.en.md
deleted file mode 100644
index 045f0a1e2..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.en.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page test"
-description = "This is a page test"
-+++
-
-This is a test demo child page
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.fr.md
deleted file mode 100644
index dd6cc3c3e..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/children/test.fr.md
+++ /dev/null
@@ -1,6 +0,0 @@
-+++
-title = "page test"
-description = "Ceci est une page test"
-+++
-
-Ceci est une page de demo
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.en.md
deleted file mode 100644
index dff19061c..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.en.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title : Expand
-description : "Displays an expandable/collapsible section of text on your page"
----
-
-The Expand shortcode displays an expandable/collapsible section of text on your page.
-Here is an example
-
-{{%expand%}}
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-{{%/expand%}}
-
-
-## Usage
-
-
-this shortcode takes exactly one optional parameter to define the text that appears next to the expand/collapse icon. (default is "Expand me...")
-
- {{%/*expand "Is this learn theme rocks ?" */%}}Yes !.{{%/* /expand*/%}}
-
-{{%expand "Is this learn theme rocks ?" %}}Yes !{{% /expand%}}
-
-# Demo
-
- {{%/*expand*/%}}
- Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
- tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
- quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
- consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
- cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
- proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
- {{%/* /expand*/%}}
-
-
-{{%expand%}}Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.{{% /expand%}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.fr.md
deleted file mode 100644
index efb86a3c9..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/expand.fr.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title : Expand
-description : "Affiche une section de texte qui se plie et se déplie"
----
-
-Le shortcode *Expand* affiche une section de texte qui se plie et se déplie.
-Ci-dessous un exemple.
-
-{{%expand%}}
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
-{{%/expand%}}
-
-
-## Utilisation
-
-
-Ce shortcode prends exactement un paramètre optionel pour définir le texte à côté de l'icone. (valeur par défaut est "Déroulez-moi...")
-
- {{%/*expand "Est-ce que ce thème envoie du pâté ?" */%}}Oui !.{{%/* /expand*/%}}
-
-{{%expand "Est-ce que ce thème envoie du pâté ?" %}}Oui !{{% /expand%}}
-
-# Demo
-
- {{%/*expand*/%}}
- Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
- tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
- quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
- consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
- cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
- proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
- {{%/* /expand*/%}}
-
-
-{{%expand%}}Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
-tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
-quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
-consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
-cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
-proident, sunt in culpa qui officia deserunt mollit anim id est laborum.{{% /expand%}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.en.md
deleted file mode 100644
index b5ed111dd..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.en.md
+++ /dev/null
@@ -1,210 +0,0 @@
----
-title : "Mermaid"
-description : "Generation of diagram and flowchart from text in a similar manner as markdown"
----
-
-[Mermaid](https://mermaidjs.github.io/) is a library helping you to generate diagram and flowcharts from text, in a similar manner as Markdown.
-
-Just insert your mermaid code in the `mermaid` shortcode and that's it.
-
-## Flowchart example
-
- {{*mermaid align="left"*/>}}
- graph LR;
- A[Hard edge] -->|Link text| B(Round edge)
- B --> C{Decision}
- C -->|One| D[Result one]
- C -->|Two| E[Result two]
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-graph LR;
- A[Hard edge] -->|Link text| B(Round edge)
- B --> C{Decision}
- C -->|One| D[Result one]
- C -->|Two| E[Result two]
-{{}}
-
-## Sequence example
-
- {{* mermaid */>}}
- sequenceDiagram
- participant Alice
- participant Bob
- Alice->>John: Hello John, how are you?
- loop Healthcheck
- John->John: Fight against hypochondria
- end
- Note right of John: Rational thoughts prevail...
- John-->Alice: Great!
- John->Bob: How about you?
- Bob-->John: Jolly good!
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-sequenceDiagram
- participant Alice
- participant Bob
- Alice->>John: Hello John, how are you?
- loop Healthcheck
- John->John: Fight against hypochondria
- end
- Note right of John: Rational thoughts prevail...
- John-->Alice: Great!
- John->Bob: How about you?
- Bob-->John: Jolly good!
-{{}}
-
-## GANTT Example
-
- {{* mermaid */>}}
- gantt
- dateFormat YYYY-MM-DD
- title Adding GANTT diagram functionality to mermaid
- section A section
- Completed task :done, des1, 2014-01-06,2014-01-08
- Active task :active, des2, 2014-01-09, 3d
- Future task : des3, after des2, 5d
- Future task2 : des4, after des3, 5d
- section Critical tasks
- Completed task in the critical line :crit, done, 2014-01-06,24h
- Implement parser and jison :crit, done, after des1, 2d
- Create tests for parser :crit, active, 3d
- Future task in critical line :crit, 5d
- Create tests for renderer :2d
- Add to mermaid :1d
- {{* /mermaid */>}}
-
-
-renders as
-
-{{}}
-gantt
- dateFormat YYYY-MM-DD
- title Adding GANTT diagram functionality to mermaid
- section A section
- Completed task :done, des1, 2014-01-06,2014-01-08
- Active task :active, des2, 2014-01-09, 3d
- Future task : des3, after des2, 5d
- Future task2 : des4, after des3, 5d
- section Critical tasks
- Completed task in the critical line :crit, done, 2014-01-06,24h
- Implement parser and jison :crit, done, after des1, 2d
- Create tests for parser :crit, active, 3d
- Future task in critical line :crit, 5d
- Create tests for renderer :2d
- Add to mermaid :1d
-{{}}
-
-
-### Class example
-
- {{* mermaid */>}}
- classDiagram
- Class01 <|-- AveryLongClass : Cool
- Class03 *-- Class04
- Class05 o-- Class06
- Class07 .. Class08
- Class09 --> C2 : Where am i?
- Class09 --* C3
- Class09 --|> Class07
- Class07 : equals()
- Class07 : Object[] elementData
- Class01 : size()
- Class01 : int chimp
- Class01 : int gorilla
- Class08 <--> C2: Cool label
- {{* /mermaid */>}}
-
-renders as
-
-
-{{}}
-classDiagram
- Class01 <|-- AveryLongClass : Cool
- Class03 *-- Class04
- Class05 o-- Class06
- Class07 .. Class08
- Class09 --> C2 : Where am i?
- Class09 --* C3
- Class09 --|> Class07
- Class07 : equals()
- Class07 : Object[] elementData
- Class01 : size()
- Class01 : int chimp
- Class01 : int gorilla
- Class08 <--> C2: Cool label
-{{}}
-
-
-### Git example
-
- {{* mermaid */>}}
- gitGraph:
- options
- {
- "nodeSpacing": 150,
- "nodeRadius": 10
- }
- end
- commit
- branch newbranch
- checkout newbranch
- commit
- commit
- checkout master
- commit
- commit
- merge newbranch
- {{* /mermaid*/>}}
-
-renders as
-
-{{}}
-gitGraph:
-options
-{
- "nodeSpacing": 150,
- "nodeRadius": 10
-}
-end
- commit
- branch newbranch
- checkout newbranch
- commit
- commit
- checkout master
- commit
- commit
- merge newbranch
-{{}}
-
-### State Diagrams
-
- {{* mermaid */>}}
- stateDiagram-v2
- open: Open Door
- closed: Closed Door
- locked: Locked Door
- open --> closed: Close
- closed --> locked: Lock
- locked --> closed: Unlock
- closed --> open: Open
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-stateDiagram-v2
- open: Open Door
- closed: Closed Door
- locked: Locked Door
- open --> closed: Close
- closed --> locked: Lock
- locked --> closed: Unlock
- closed --> open: Open
-{{}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md
deleted file mode 100644
index 7798785dd..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/mermaid.fr.md
+++ /dev/null
@@ -1,205 +0,0 @@
----
-title : "Mermaid"
-description : "Génération de diagrammes à partir de texte, dans le même style que Markdown"
----
-
-[Mermaid](https://mermaidjs.github.io/) est une bibliothèque Javascript qui permet de générer des diagrammes (séquence, état, gantt, etc.) à partir de texte, dans le même style que Markdown.
-
-Insérer votre code Mermaid dans un shortcode `mermaid` et c'est tout.
-
-## Flowchart example
- {{*mermaid align="left"*/>}}
- graph LR;
- A[Bords droits] -->|Lien texte| B(Bords arondis)
- B --> C{Décision}
- C -->|Un| D[Résultat un]
- C -->|Deux| E[Résultat deux]
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-graph LR;
- A[Bords droits] -->|Lien texte| B(Bords arondis)
- B --> C{Décision}
- C -->|Un| D[Résultat un]
- C -->|Deux| E[Résultat deux]
-{{< /mermaid >}}
-
-## Sequence example
-
- {{*mermaid*/>}}
- sequenceDiagram
- participant Alice
- participant Bob
- Alice->>John: Salut John, comment vas-tu?
- loop Vérification
- John->John: Se bat contre l'hyponcodrie.
- end
- Note right of John: Les pensées rationnelles prédominent...
- John-->Alice: Super!
- John->Bob: Et toi?
- Bob-->John: Au top!
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-sequenceDiagram
- participant Alice
- participant Bob
- Alice->>John: Salut John, comment vas-tu?
- loop Vérification
- John->John: Se bat contre l'hyponcodrie.
- end
- Note right of John: Les pensées rationnelles prédominent...
- John-->Alice: Super!
- John->Bob: Et toi?
- Bob-->John: Au top!
-{{< /mermaid >}}
-
-## GANTT Example
-
- {{*mermaid*/>}}
- gantt
- dateFormat YYYY-MM-DD
- title Ajout de la fonctionnalité de GANTT à Mermaid
- section Une section
- Tâche complétée :done, des1, 2014-01-06,2014-01-08
- Tâche en cours :active, des2, 2014-01-09, 3d
- Future tâche : des3, after des2, 5d
- Future tâche 2 : des4, after des3, 5d
- section Tâches critiques
- Tâche complétée dans le chemin critique :crit, done, 2014-01-06,24h
- Implémenter le parser et jison :crit, done, after des1, 2d
- Créer des tests pour le parser :crit, active, 3d
- Future tâche dans le chemin critique :crit, 5d
- Créer des tests pour le renderer :2d
- Ajout à Mermaid :1d
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-gantt
- dateFormat YYYY-MM-DD
- title Ajout de la fonctionnalité de GANTT à Mermaid
- section Une section
- Tâche complétée :done, des1, 2014-01-06,2014-01-08
- Tâche en cours :active, des2, 2014-01-09, 3d
- Future tâche : des3, after des2, 5d
- Future tâche 2 : des4, after des3, 5d
- section Tâches critiques
- Tâche complétée dans le chemin critique :crit, done, 2014-01-06,24h
- Implémenter le parser et jison :crit, done, after des1, 2d
- Créer des tests pour le parser :crit, active, 3d
- Future tâche dans le chemin critique :crit, 5d
- Créer des tests pour le renderer :2d
- Ajout à Mermaid :1d
-{{}}
-
-### Class example
-
- {{/* mermaid */}}
- classDiagram
- Class01 <|-- AveryLongClass : Cool
- Class03 *-- Class04
- Class05 o-- Class06
- Class07 .. Class08
- Class09 --> C2 : Where am i?
- Class09 --* C3
- Class09 --|> Class07
- Class07 : equals()
- Class07 : Object[] elementData
- Class01 : size()
- Class01 : int chimp
- Class01 : int gorilla
- Class08 <--> C2: Cool label
- {{/* /mermaid */}}
-
-renders as
-
-{{< mermaid >}}
-classDiagram
- Class01 <|-- AveryLongClass : Cool
- Class03 *-- Class04
- Class05 o-- Class06
- Class07 .. Class08
- Class09 --> C2 : Where am i?
- Class09 --* C3
- Class09 --|> Class07
- Class07 : equals()
- Class07 : Object[] elementData
- Class01 : size()
- Class01 : int chimp
- Class01 : int gorilla
- Class08 <--> C2: Cool label
-{{< /mermaid >}}
-
-### Git example
-
- {{* mermaid */>}}
- gitGraph:
- options
- {
- "nodeSpacing": 150,
- "nodeRadius": 10
- }
- end
- commit
- branch newbranch
- checkout newbranch
- commit
- commit
- checkout master
- commit
- commit
- merge newbranch
- {{* /mermaid */>}}
-
-renders as
-
-{{< mermaid >}}
-gitGraph:
-options
-{
- "nodeSpacing": 150,
- "nodeRadius": 10
-}
-end
- commit
- branch newbranch
- checkout newbranch
- commit
- commit
- checkout master
- commit
- commit
- merge newbranch
-{{< /mermaid >}}
-
-### State Diagrams
-
- {{* mermaid */>}}
- stateDiagram-v2
- ouvert: Ouvert
- clos: Clos
- fermé: Fermé
- ouvert --> clos
- clos --> fermé: Lock
- fermé --> clos: Unlock
- clos --> ouvert: Open
- {{* /mermaid */>}}
-
-renders as
-
-{{}}
-stateDiagram-v2
- ouvert: Ouvert
- clos: Clos
- fermé: Fermé
- ouvert --> clos
- clos --> fermé: Lock
- fermé --> clos: Unlock
- clos --> ouvert: Open
-{{}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.en.md
deleted file mode 100644
index c82a6e9f5..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.en.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Notice
-description : "Disclaimers to help you structure your page"
----
-
-The notice shortcode shows 4 types of disclaimers to help you structure your page.
-
-### Note
-
-```
-{{%/* notice note */%}}
-A notice disclaimer
-{{%/* /notice */%}}
-```
-
-renders as
-
-{{% notice note %}}
-A notice disclaimer
-{{% /notice %}}
-
-### Info
-
-```
-{{%/* notice info */%}}
-An information disclaimer
-{{%/* /notice */%}}
-```
-
-renders as
-
-{{% notice info %}}
-An information disclaimer
-{{% /notice %}}
-
-### Tip
-
-```
-{{%/* notice tip */%}}
-A tip disclaimer
-{{%/* /notice */%}}
-```
-
-renders as
-
-{{% notice tip %}}
-A tip disclaimer
-{{% /notice %}}
-
-### Warning
-
-```
-{{%/* notice warning */%}}
-A warning disclaimer
-{{%/* /notice */%}}
-```
-
-renders as
-
-{{% notice warning %}}
-A warning disclaimer
-{{% /notice %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.fr.md
deleted file mode 100644
index 91e4d7052..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/notice.fr.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Notice
-description : "Message pour vous aider à structurer votre contenu"
----
-
-Le shortcode *Notice* permet d'afficher 4 types de message pour vous aider à structurer votre contenu.
-
-### Note
-
-```
-{{%/* notice note */%}}
-Une notice de type *note*
-{{%/* /notice */%}}
-```
-
-s'affiche comme
-
-{{% notice note %}}
-Une notice de type *note*
-{{% /notice %}}
-
-### Info
-
-```
-{{%/* notice info */%}}
-Une notice de type *info*
-{{%/* /notice */%}}
-```
-
-s'affiche comme
-
-{{% notice info %}}
-Une notice de type *info*
-{{% /notice %}}
-
-### Tip
-
-```
-{{%/* notice tip */%}}
-Une notice de type *tip*
-{{%/* /notice */%}}
-```
-
-s'affiche comme
-
-{{% notice tip %}}
-Une notice de type *tip*
-{{% /notice %}}
-
-### Warning
-
-```
-{{%/* notice warning */%}}
-Une notice de type *warning*
-{{%/* /notice */%}}
-```
-
-s'affiche comme
-
-{{% notice warning %}}
-Une notice de type *warning*
-{{% /notice %}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.en.md
deleted file mode 100644
index f431ffb90..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.en.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Site param
-description : "Get value of site params variables in your page."
----
-
-`siteparam` shortcode is used to help you print values of site params.
-
-For instance, in this current site, the `editURL` variable is used in `config.toml`
-
-```toml
-[params]
- editURL = "https://github.com/matcornic/hugo-theme-learn/edit/master/exampleSite/content/"
-```
-
-Use the `siteparam` shortcode to display its value.
-
-```
-`editURL` Value : {{%/* siteparam "editURL" */%}}
-```
-
-is displayed as
-
-`editURL` Value : {{% siteparam "editURL" %}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md
deleted file mode 100644
index 508100b94..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/siteparam.fr.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Site param
-description : "Afficher la valeur d'un paramètre global du site dans votre page"
----
-
-Les shortcode `siteparam` est utilisé pour vous aider à afficher des valeurs provenant des paramètres globaux du site.
-
-Par exemple, dans ce site, le paramètre `editURL` est utilisé dans le fichier `config.toml`
-
-```toml
-[params]
- editURL = "https://github.com/matcornic/hugo-theme-learn/edit/master/exampleSite/content/"
-```
-
-Utilisez le shortcode `siteparam` pour affichier sa valeur.
-
-```
-Valeur de `editURL` : {{%/* siteparam "editURL" */%}}
-```
-
-s'affiche comme
-
-Valeur de `editURL` : {{% siteparam "editURL" %}}
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/shortcodes/tabs.en.md b/documentation/staging/themes/learn/exampleSite/content/shortcodes/tabs.en.md
deleted file mode 100644
index d664eeaca..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/shortcodes/tabs.en.md
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: Tabbed views
-description : "Synchronize selection of content in different tabbed views"
----
-
-Choose which content to see across the page. Very handy for providing code
-snippets for multiple languages or providing configuration in different formats.
-
-## Code example
-
- {{* tabs */>}}
- {{%/* tab name="python" */%}}
- ```python
- print("Hello World!")
- ```
- {{%/* /tab */%}}
- {{%/* tab name="R" */%}}
- ```R
- > print("Hello World!")
- ```
- {{%/* /tab */%}}
- {{%/* tab name="Bash" */%}}
- ```Bash
- echo "Hello World!"
- ```
- {{%/* /tab */%}}
- {{* /tabs */>}}
-
-Renders as:
-
-{{< tabs >}}
-{{% tab name="python" %}}
-```python
-print("Hello World!")
-```
-{{% /tab %}}
-{{% tab name="R" %}}
-```R
-> print("Hello World!")
-```
-{{% /tab %}}
-{{% tab name="Bash" %}}
-```Bash
-echo "Hello World!"
-```
-{{% /tab %}}
-{{< /tabs >}}
-
-Tab views with the same tabs that belong to the same group sychronize their selection:
-
-{{< tabs >}}
-{{% tab name="python" %}}
-```python
-print("Hello World!")
-```
-{{% /tab %}}
-{{% tab name="R" %}}
-```R
-> print("Hello World!")
-```
-{{% /tab %}}
-{{% tab name="Bash" %}}
-```Bash
-echo "Hello World!"
-```
-{{% /tab %}}
-{{< /tabs >}}
-
-## Config example
-
- {{* tabs groupId="config" */>}}
- {{%/* tab name="json" */%}}
- ```json
- {
- "Hello": "World"
- }
- ```
- {{%/* /tab */%}}
- {{%/* tab name="XML" */%}}
- ```xml
- World
- ```
- {{%/* /tab */%}}
- {{%/* tab name="properties" */%}}
- ```properties
- Hello = World
- ```
- {{%/* /tab */%}}
- {{* /tabs */>}}
-
-Renders as:
-
-{{< tabs groupId="config" >}}
-{{% tab name="json" %}}
-```json
-{
- "Hello": "World"
-}
-```
-{{% /tab %}}
-{{% tab name="XML" %}}
-```xml
-World
-```
-{{% /tab %}}
-{{% tab name="properties" %}}
-```properties
-Hello = World
-```
-{{% /tab %}}
-{{< /tabs >}}
-
-{{% notice warning %}}
-When using tab views with different content sets, make sure to use a common `groupId` for equal sets but distinct
-`groupId` for different sets. The `groupId` defaults to `'default'`.
-**Take this into account across the whole site!**
-The tab selection is restored automatically based on the `groupId` and if it cannot find a tab item because it came
- from the `'default'` group on a different page then all tabs will be empty at first.
-{{% /notice %}}
diff --git a/documentation/staging/themes/learn/exampleSite/content/showcase.en.md b/documentation/staging/themes/learn/exampleSite/content/showcase.en.md
deleted file mode 100644
index 4d06d8b41..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/showcase.en.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Showcase
-disableToc: true
----
-
-#### [TAT](https://ovh.github.io/tat/overview/) by OVH
-
-
-#### [Tshark.dev](https://tshark.dev) by Ross Jacobs
-
-
-#### [inteliver](https://docs.inteliver.com) by Amir Lavasani
-
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/content/showcase.fr.md b/documentation/staging/themes/learn/exampleSite/content/showcase.fr.md
deleted file mode 100644
index fcb9d7f02..000000000
--- a/documentation/staging/themes/learn/exampleSite/content/showcase.fr.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Vitrine
-disableToc: true
-slug: vitrine
----
-
-#### [TAT](https://ovh.github.io/tat/overview/) par OVH
-
-
-#### [Tshark.dev](https://tshark.dev) par Ross Jacobs
-
-
-#### [inteliver](https://docs.inteliver.com) by Amir Lavasani
-
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/layouts/partials/custom-footer.html b/documentation/staging/themes/learn/exampleSite/layouts/partials/custom-footer.html
deleted file mode 100644
index 50e11eb39..000000000
--- a/documentation/staging/themes/learn/exampleSite/layouts/partials/custom-footer.html
+++ /dev/null
@@ -1,10 +0,0 @@
-
\ No newline at end of file
diff --git a/documentation/staging/themes/learn/exampleSite/layouts/partials/logo.html b/documentation/staging/themes/learn/exampleSite/layouts/partials/logo.html
deleted file mode 100644
index e1ef57cab..000000000
--- a/documentation/staging/themes/learn/exampleSite/layouts/partials/logo.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
-
-
diff --git a/documentation/staging/themes/learn/exampleSite/layouts/partials/menu-footer.html b/documentation/staging/themes/learn/exampleSite/layouts/partials/menu-footer.html
deleted file mode 100644
index 5a35bd00f..000000000
--- a/documentation/staging/themes/learn/exampleSite/layouts/partials/menu-footer.html
+++ /dev/null
@@ -1,14 +0,0 @@
-