Switching to Hugo relearn theme

Author: robertpatrick

.gitignore

@@ -28,5 +28,6 @@ release.properties
 **/*.pyc
 **/.DS_Store
 **/.hugo_build.lock
+documentation/**/docs
 .jython_cache
 .oca

documentation/4.0/config.toml

@@ -1,4 +1,4 @@
-# Copyright (c) 2021, 2023, Oracle and/or its affiliates.
+# Copyright (c) 2021, 2025, Oracle and/or its affiliates.
 # Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl.
 #
 # analytics
@@ -9,7 +9,7 @@ languageCode = "en-us"
 title = "WebLogic Deploy Tooling"
 
 # Change the default theme to be use when building the site with Hugo
-theme = "hugo-theme-learn"
+theme = "hugo-theme-relearn-8.3.0"
 
 publishDir = "docs"
 
@@ -18,10 +18,13 @@ publishDir = "docs"
   home = [ "HTML", "RSS", "JSON"]
 
 [params]
+  hideAuthorDate = true
   # disable the copy to clipboard links
   disableInlineCopyToClipBoard = true
+  themeVariant = "learn"
 
 [markup]
+  defaultMarkdownHandler = 'goldmark'
   [markup.goldmark]
     [markup.goldmark.extensions]
       [markup.goldmark.extensions.extras]

documentation/4.0/content/_index.md

@@ -1,3 +1,8 @@
+---
+pre: "<b> </b>"
+hideHeader: true
+---
+
 ## WebLogic Deploy Tooling
 
 WebLogic Deploy Tooling (WDT) makes it easy to stand up WebLogic environments and perform
@@ -33,7 +38,7 @@ WDT provides several single-purpose tools, all exposed as shell scripts (for bot
 * Tokenize a model with variables.
 * Provide information about the folders and attributes that are valid for sections and folders of a domain model.
 
-For detailed information, see [WDT Tools]({{< relref "/userguide/tools/" >}}).
+For detailed information, see [WDT Tools]({{% relref "/userguide/tools/" %}}).
 
 ***
 ### Current production release
@@ -43,24 +48,23 @@ WebLogic Deploy Tooling version and release information can be found [here](http
 ***
 ### Recent changes and known issues
 
-See the [Release Notes]({{< relref "/release-notes.md" >}}) for known issues and workarounds.
+See the [Release Notes]({{% relref "/release-notes.md" %}}) for known issues and workarounds.
 
 ### About this documentation
 
 This documentation includes sections targeted to different audiences:
 
-* [Concepts]({{< relref "/concepts/" >}}) explains the underlying metadata models and archive files.
-* The [User Guide]({{< relref "/userguide/" >}}) contains detailed usage information, including how to install and configure WebLogic Deploy Tooling, and how to use each tool.
-* The [Samples]({{< relref "/samples/" >}}) provide informative use case scenarios.
-* The [Developer Guide]({{< relref "/developer/" >}}) provides details for people who
+* [Concepts]({{% relref "/concepts/" %}}) explains the underlying metadata models and archive files.
+* The [User Guide]({{% relref "/userguide/" %}}) contains detailed usage information, including how to install and configure WebLogic Deploy Tooling, and how to use each tool.
+* The [Samples]({{% relref "/samples/" %}}) provide informative use case scenarios.
+* The [Developer Guide]({{% relref "/developer/" %}}) provides details for people who
 want to understand how WDT is built, its features mapped and implemented. Those who
-wish to contribute to the WebLogic Deploy Tooling code will find useful information [here]({{< relref "/developer/contribute.md" >}}).
+wish to contribute to the WebLogic Deploy Tooling code will find useful information [here]({{% relref "/developer/contribute.md" %}}).
 
 ### Related projects
 
 * [WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/)
 * [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/)
 * [WebLogic Kubernetes Toolkit UI](https://oracle.github.io/weblogic-toolkit-ui/)
 * [WebLogic Monitoring Exporter](https://github.com/oracle/weblogic-monitoring-exporter)
-* [WebLogic Logging Exporter](https://github.com/oracle/weblogic-logging-exporter)
 * [WebLogic Remote Console](https://oracle.github.io/weblogic-remote-console/)

documentation/4.0/content/concepts/_index.md

@@ -1,9 +1,12 @@
-+++
-title = "Concepts"
-date = 2019-02-22T15:27:54-05:00
-weight = 1
-chapter = true
-pre = "<b> </b>"
-+++
+---
+title: "Concepts"
+date: 2019-02-22T15:27:54-05:00
+weight: 1
+chapter: true
+pre: "<b> </b>"
+hideHeader: true
+---
 
 # Concepts
+
+{{% children type="list" description="true" %}}

documentation/4.0/content/concepts/archive.md

@@ -3,6 +3,7 @@ title: "Archive File"
 date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 2
+description: "The section that discusses the structure and content of the WDT archive file."
 ---
 
 
@@ -41,7 +42,7 @@ file in the specified location, and will be deployed to that directory in the do
 
 These are the paths within the archive that are used for different types of resources. You can create further
 directory structures underneath some of these locations to organize the files and directories as you see fit.  The
-[Archive Helper Tool]({{< relref "/userguide/tools/archive_helper.md" >}}) makes it easy to add, update, and remove entries from the archive file.  
+[Archive Helper Tool]({{% relref "/userguide/tools/archive_helper.md" %}}) makes it easy to add, update, and remove entries from the archive file.  
 
 #### Why are there two separate directory structures?
 
@@ -79,7 +80,7 @@ This is the root directory where your custom files and directories can be stored
 files are not collected by the Discover Domain Tool.   Every file resource under this directory is extracted during
 `createDomain`, `updateDomain`, and `deployApps`.
 
-Some custom files may belong in `wlsdeploy/custom`. To determine which location is preferable for your files, see [Why are there two separate directory structures?]({{< relref "#why-are-there-two-separate-directory-structures" >}}).
+Some custom files may belong in `wlsdeploy/custom`. To determine which location is preferable for your files, see [Why are there two separate directory structures?]({{% relref "#why-are-there-two-separate-directory-structures" %}}).
 
 This location is particularly useful when handling files that live outside an application; for example, a property
 file used to configure the application.  The general steps to make applications that use such files work when
@@ -141,7 +142,7 @@ This is the root directory where your custom files and directories can be stored
 files are not collected by the Discover Domain Tool.   Every file resource under this directory is extracted during
 `createDomain`, `updateDomain`, and `deployApps`.
 
-Some custom files may belong in `config/wlsdeploy/custom`. To determine which location is preferable for your files, see [Why are there two separate directory structures?]({{< relref "#why-are-there-two-separate-directory-structures" >}}).
+Some custom files may belong in `config/wlsdeploy/custom`. To determine which location is preferable for your files, see [Why are there two separate directory structures?]({{% relref "#why-are-there-two-separate-directory-structures" %}}).
 
 #### `wlsdeploy/domainBin`
 The root directory under which `$DOMAIN_HOME/bin` scripts are stored. Only scripts referenced in the

documentation/4.0/content/concepts/model.md

@@ -2,7 +2,8 @@
 title: "Metadata Model"
 date: 2019-02-23T17:19:24-05:00
 draft: false
-weight: 1
+weight: 2
+description: "The section that discusses the high-level concepts of the WDT model."
 ---
 
 ### Contents
@@ -99,7 +100,7 @@ on the target environment.  For more information and a list of available path to
 The example above shows the attribute `SourcePath` of the `simpleear` application with a value of
 `wlsdeploy/applications/simpleear.ear`.  The prefix `wlsdeploy/` indicates that the resource is located in the archive
 file in the specified location, and will be deployed to that directory within the domain, in this case
-`<domain-home>/wlsdeploy/applications/simpleear.ear`. See the [Archive file]({{< relref "/concepts/archive.md" >}})
+`<domain-home>/wlsdeploy/applications/simpleear.ear`. See the [Archive file]({{% relref "/concepts/archive.md" %}})
 for more details about using the archive file.
 
 Users can create further directory structures underneath the above locations to organize the files and directories as
@@ -339,7 +340,7 @@ declared as the default realm:
 
 This feature does not apply to named security providers within a realm. These items follow a special set of rules that
 are required to maintain their ordering. See
-[Modeling security providers]({{< relref "/samples/securityproviders-model.md" >}}) for detailed information.
+[Modeling security providers]({{% relref "/samples/securityproviders-model.md" %}}) for detailed information.
 
 This feature can be used to undeploy applications or remove libraries.
 
@@ -458,7 +459,7 @@ topology:
 
 Beginning in 2.0, WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
 This may require some changes to existing models in order to be parsed correctly.
-   - Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need
+   - Model elements that use [delete notation]({{% relref "/concepts/model#declaring-named-mbeans-to-delete" %}}) need
      to be escaped in single or double quotation marks.
    ```yaml
    topology:

documentation/4.0/content/developer/ReleaseProcess.md

@@ -3,6 +3,7 @@ title: "WDT project release process"
 date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 5
+description: "How releases are created from WDT source code."
 ---
 
 This document describes the process that should be followed to create a WebLogic Deploy Tooling (WDT) release.

documentation/4.0/content/developer/_index.md

@@ -1,12 +1,15 @@
-+++
-title = "Developer Guide"
-date = 2019-02-22T15:27:54-05:00
-weight = 4
-chapter = true
-pre = "<b> </b>"
-+++
+---
+title: "Developer Guide"
+date: 2019-02-22T15:27:54-05:00
+weight: 4
+chapter: true
+pre: "<b> </b>"
+hideHeader: true
+---
 
 
 # Developer Guide
 
 The Developer Guide provides information for developers who want to understand or contribute to the code.
+
+{{% children type="list" description="true" %}}

documentation/4.0/content/developer/alias-definitions.md

@@ -3,6 +3,7 @@ title: "Alias definitions"
 date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 3
+description: "How the WDT aliases work."
 ---
 
 WebLogic Deploy Tool uses a set of JSON configuration files to map folders and attributes in the model to the corresponding WLST MBeans and their attributes. These mappings are referred as 'aliases' throughout the project code and documentation. Each element in the alias definition file has detailed properties that assist in this mapping.

documentation/4.0/content/developer/buildWDT.md

@@ -1,8 +1,9 @@
 ---
-title: "Build WebLogic Deploy Tool"
+title: "Build WebLogic Deploy Tooling"
 date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 4
+description: "How to build WDT from source."
 ---
 
 ### Prerequisites