Further refinements and removal of old tutorials that are being replaced

Author: Donna-Marie Smith

.gitignore

@@ -9,5 +9,4 @@
 /public/
 /resources/
 node_modules/
-tech-doc-hugo
-old-tutorials.md
+tech-doc-hugo

content/en/docs/2025.1/Guides/user-guides/user-interfaces/gateway/Admin/packages/package-definitions-grid.md

@@ -18,6 +18,7 @@ The Package Definitions Grid displays a list of existing [{{% ctx %}} Package][W
 The Package Definitions Grid shows the most recently created version of each package; older versions can be viewed by expanding the package definition. Selecting a package version will display it's details in the [Package Version Editor][].
 
 The Package Definitions Grid also contains buttons to:
+
 * [Create a Package][]
 * [Import a Package][]
 
@@ -33,17 +34,17 @@ If a selected flow has dependent flows, the dependent flow will be automatically
 
 The package may optionally [define LDAP groups][Authorisation] that can execute flows, [schedules][] to run flows at specific times, and [triggers][] to run flows on receipt of specific SNMP Traps.
 
-See the [Create a Package tutorial][] for a step-by-step guide.
+See the [Create a Package][Create a Package tutorial] tutorial for a step-by-step guide.
 
 ### Import a Package
 
-A {{% ctx %}} Package file, with the extension of `.ctxpkg`, may be imported into any {{% ctx %}} Gateway by clicking the `Import` button and selecting the `.ctxpkg` file to import. 
+A {{% ctx %}} Package file, with the extension of `.ctxpkg`, may be imported into any {{% ctx %}} Gateway by clicking the `Import` button and selecting the `.ctxpkg` file to import.
 
 If the imported package already exists in {{% ctx %}} Gateway, a new version of that package will be created; if the imported package does not exist, a new package will be created.
 
 All the flows contained in the package will be saved in the Master Repository of the destination {{% ctx %}} Gateway as the master versions of those flows; if the imported flows already existed, the imported flows would become the new master versions.
 
-See the [Import a Package tutorial][] for a step-by-step guide.
+See the [Import a Package][Import a Package tutorial] tutorial for a step-by-step guide.
 
 ## Remarks
 

content/en/docs/2025.1/Guides/user-guides/user-interfaces/gateway/Admin/packages/package-version-editor.md

@@ -49,23 +49,23 @@ The created {{% ctx %}} Package Version may optionally define Schedules to cause
 
 The new {{% ctx %}} Package Version does not retain any of the flow execution authorisation, schedules, nor any triggers set on the source {{% ctx %}} Package Version.
 
-See the [Create a New Package Version tutorial][] for a step-by-step guide.
+See the [Create a New Package Version][Create a New Package Version tutorial] tutorial for a step-by-step guide.
 
 #### Publish a Package Version
 
 When a {{% ctx %}} Package Version is published it is distributed to the execution nodes. The first execution of a flow on a node will cause the flow to be compiled, cached and executed on that node.
 
 Published {{% ctx %}} Package Versions may be explicitly set as the Default Version for that {{% ctx %}} Package, meaning that a REST Request to execute a flow from that published {{% ctx %}} Package Version does not have to specify the Package Version.
 
-See the [Publish a Package Version tutorial][] for a step-by-step guide.
+See the [Publish a Package Version][Publish a Package Version tutorial] tutorial for a step-by-step guide.
 
 #### Set As Default Package
 
 The Default Package specifies which {{% ctx %}} Package will be used to execute flows if the execution REST Request omits the Package Name specifying the {{% ctx %}} Package to use. There is only one Default Package for each {{% ctx %}} system.
 
 The Default Package can be set on any {{% ctx %}} Package that has a published {{% ctx %}} Package Version. If all the {{% ctx %}} Package Versions associated with the Default Package are unpublished, the Default Package remains unchanged.
 
-See the [Set the Default Package tutorial][] for a step-by-step guide.
+See the [Set the Default Package][Set the Default Package tutorial] tutorial for a step-by-step guide.
 
 #### Set As Default Version
 
@@ -81,29 +81,29 @@ If an unpublished {{% ctx %}} Package Version that was previously set as the Def
 
 If all the {{% ctx %}} Package Versions of a {{% ctx %}} Package are unpublished and then a Package is republished, it will become implicitly set as the Default Version, even if it was explicitly set as the Default Version before unpublishing.
 
-See the [Set the Default Package Version tutorial][] for a step-by-step guide.
+See the [Set the Default Package Version][Set the Default Package Version tutorial] tutorial for a step-by-step guide.
 
 #### Unpublish a Package Version
 
 When a {{% ctx %}} Package Version is unpublished, it is removed from all the execution nodes and flow execution cannot be started for any flows in that package; however, any currently running executions from that Package Version will continue to completion. When all instances of an executing flow in an unpublished package have completed, the cache of the compiled flow discarded.
 
-See the [Unpublish a Package Version tutorial][] for a step-by-step guide.
+See the [Unpublish a Package Version][Unpublish a Package Version tutorial] tutorial for a step-by-step guide.
 
 #### Export a Package Version
 
 Any {{% ctx %}} Package Version can be exported to a file, which can be used for importing the package to another {{% ctx %}} Gateway or for archiving purposes. The export file is automatically downloaded from the browser and has the file name of `<Package Name>.ctxpkg`.
 
 The exported file contains the {{% ctx %}} Package Version definition, and the flow definitions contained in the package. Any authorisation, schedules or triggers set on the {{% ctx %}} Package Version are not included in the exported file.
 
-See the [Export a Package Version tutorial][] for a step-by-step guide.
+See the [Export a Package Version][Export a Package Version tutorial] tutorial for a step-by-step guide.
 
 ### Authorisation
 
 The Authorisation tab on a package version defines which LDAP groups can execute flows contained in that package version, using Token-based OAuth2 authorisation.
 
 The list of Active Directory objects displayed to define flow execution authorisation is filtered by the Base DNs configured in LDAP Connection for {{% ctx %}} Gateway.
 
-See the [Set Authorisation on a Package Version tutorial][] for a step-by-step guide.
+See the [Set Authorisation on a Package Version][Set Authorisation on a Package Version tutorial] tutorial for a step-by-step guide.
 
 ### Schedules
 
@@ -115,7 +115,7 @@ Any data to be passed to the flow’s input variables is entered using Expressio
 
 Creating a new package version will not inherit the schedule configuration from the source package version. Similarly, exporting a package version will not include the package’s Schedule in the {{% ctx %}} Package file.
 
-See the [Create a Schedule on a Package Version tutorial][] for a step-by-step guide.
+See the [Create a Schedule on a Package Version][Create a Schedule on a Package Version tutorial] tutorial for a step-by-step guide.
 
 ### Triggers
 
@@ -145,15 +145,15 @@ Any data to be passed to the flow’s input variables is entered using Expressio
 
 Creating a new package version will not inherit the trigger configuration from the source package version. Similarly, exporting a package version will not include the package’s trigger configuration in the {{% ctx %}} Package file.
 
-See the [Create a Trigger on a Package Version tutorial][] for a step-by-step guide.
+See the [Create a Trigger on a Package Version][Create a Trigger on a Package Version tutorial] tutorial for a step-by-step guide.
 
 ### Running Executions
 
 The Running Executions tab displays a list of currently running flow executions for the selected package version. Each row in the list is a distinct flow execution, and identifies: the Flow Name, its Execution ID, the time the execution Started At, and the duration of that execution; the duration is updated at 10 second intervals.
 
 Any running flow execution may be aborted by selecting the flow and clicking the `Stop the execution` icon. The flow execution will be immediately stopped.
 
-See the [View and Abort Running Flow Executions tutorial][] for a step-by-step guide.
+See the [View and Abort Running Flow Executions][View and Abort Running Flow Executions tutorial] tutorial for a step-by-step guide.
 
 ## Remarks