Split Getting Started out of Overview and promote it on the landing page

Move the "Where To Start" and "Modular Components" sections from
overview.md into a new getting-started.md, linked from the hero and
nav/sidebar (matching the directtrust-tools.github.io pattern). Also
move the BareMetal Assembly Project sidebar entry to the top, and
clean up copy (typos, grammar, wording) in Overview and Getting
Started.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TJcNswabKU3zekw6g5ccjF

Author: gm2552

docs/.vitepress/config.mts

@@ -24,13 +24,50 @@ export default defineConfig({
     logo: '/logo.png',
     siteTitle: false,
 
-    nav: [{ text: 'Overview', link: '/overview' }],
+    nav: [
+      { text: 'Overview', link: '/overview' },
+      { text: 'Getting Started', link: '/getting-started' }
+    ],
 
     // Hand-maintained: adding a page in a component repo's docs/ folder also
     // requires a sidebar entry here in the hub repo — the two live in
     // different repos, so this coupling can't be enforced automatically.
     sidebar: [
       { text: 'Overview', link: '/overview' },
+      { text: 'Getting Started', link: '/getting-started' },
+      {
+        text: 'BareMetal Assembly Project',
+        link: '/docs/direct-project-stock/',
+        collapsed: true,
+        items: [
+          {
+            text: 'Deployment Guide',
+            link: '/docs/direct-project-stock/dep-guide',
+            collapsed: true,
+            items: [
+              {
+                text: 'HISP Only Deployment (no source)',
+                link: '/docs/direct-project-stock/dep-hisp-only',
+                collapsed: true,
+                items: [
+                  { text: 'Legacy HISP Deployment Model', link: '/docs/direct-project-stock/legacy-deployment' },
+                  { text: 'Cloud Native HISP Deployment Model', link: '/docs/direct-project-stock/cloud-native-deployment' }
+                ]
+              }
+            ]
+          },
+          {
+            text: 'Deployment Options',
+            link: '/docs/direct-project-stock/imp-options',
+            collapsed: true,
+            items: [
+              { text: 'Configuration and Message Monitor Storage', link: '/docs/direct-project-stock/config-store' },
+              { text: 'Single Use Certificates', link: '/docs/direct-project-stock/single-use-certs' },
+              { text: 'Enhanced Private Key Security', link: '/docs/direct-project-stock/enhanced-key-security' }
+            ]
+          }
+        ]
+      },
       {
         text: 'Security And Trust Agent',
         link: '/docs/agent/',
@@ -163,39 +200,6 @@ export default defineConfig({
           { text: 'DNS Record Configuration', link: '/docs/dns/dns-rec-config' },
           { text: 'Integration With GoDaddy', link: '/docs/dns/godaddy' }
         ]
-      },
-      {
-        text: 'BareMetal Assembly Project',
-        link: '/docs/direct-project-stock/',
-        collapsed: true,
-        items: [
-          {
-            text: 'Deployment Guide',
-            link: '/docs/direct-project-stock/dep-guide',
-            collapsed: true,
-            items: [
-              {
-                text: 'HISP Only Deployment (no source)',
-                link: '/docs/direct-project-stock/dep-hisp-only',
-                collapsed: true,
-                items: [
-                  { text: 'Legacy HISP Deployment Model', link: '/docs/direct-project-stock/legacy-deployment' },
-                  { text: 'Cloud Native HISP Deployment Model', link: '/docs/direct-project-stock/cloud-native-deployment' }
-                ]
-              }
-            ]
-          },
-          {
-            text: 'Deployment Options',
-            link: '/docs/direct-project-stock/imp-options',
-            collapsed: true,
-            items: [
-              { text: 'Configuration and Message Monitor Storage', link: '/docs/direct-project-stock/config-store' },
-              { text: 'Single Use Certificates', link: '/docs/direct-project-stock/single-use-certs' },
-              { text: 'Enhanced Private Key Security', link: '/docs/direct-project-stock/enhanced-key-security' }
-            ]
-          }
-        ]
       }
     ],
 

docs/getting-started.md

@@ -0,0 +1,23 @@
+---
+title: Getting Started
+---
+
+# Getting Started
+
+If you want to stand up an instance of the reference implementation right away, the fastest path is the [BareMetal Assembly Project](/docs/direct-project-stock/) for the Java platform. It bundles the reference implementation's components into a ready-to-deploy stack, so you don't need to build or wire the pieces together yourself.
+
+To build all components, including the BareMetal assembly, from source instead of using a prebuilt package, follow the instructions [here](https://github.com/DirectProjectJavaRI/direct-ri-build).
+
+## Understanding the Modular Components
+
+If you'd rather understand how the reference implementation's components fit together before diving in, start with the module list below. The reference implementation follows a modular design for easy reuse and extensibility, with components available in both .Net and Java.
+
+### Java Components
+
+* [Commons Library](http://api.directproject.info/direct-common/6.0/)
+* [Security And Trust Agent](/docs/agent/)
+* [Gateway](/docs/gateway/)
+* [Message Monitoring](/docs/direct-msg-monitor/)
+* [Policy Enablement](/docs/direct-policy/)
+* [DNS Services](/docs/dns/)
+* [BareMetal Assembly Project](/docs/direct-project-stock/)

docs/index.md

@@ -11,6 +11,6 @@ title: The DirectProject
   <p class="home-hero-tagline">Open source reference implementation of the Direct specifications</p>
   <div class="home-hero-actions">
     <a class="home-hero-btn brand" href="/overview">Overview</a>
-    <a class="home-hero-btn alt" href="/docs/agent/">Security And Trust Agent</a>
+    <a class="home-hero-btn alt" href="/getting-started">Getting Started</a>
   </div>
 </div>

docs/overview.md

@@ -4,32 +4,12 @@ title: Overview
 
 # Overview
 
-The reference implementation is an open source and pre-assembled implementation of the Direct specifications. An implementation exists in both the .Net and Java languages and can be downloaded freely from a handful of websites. A subproject of Direct, called Bare Metal, contains a set of instructions on procuring the reference implementation and standing up a reference HISP from scratch using only the reference implementation assemblies.
+The reference implementation is an open source, pre-assembled implementation of the Direct specifications, available in both .Net and Java. A subproject called BareMetal provides everything needed to procure the reference implementation and stand up a HISP from scratch using only the reference implementation's assemblies.
 
-The reference implementation is a fully working model with all sorts of bells and whistles, but it's just a model. If you've ever delved into the world of embedded hardware or robotics, the starting point is usually a reference board. The board is a cookie cutter model with several modules, inputs, outputs, and maybe an operating system or programmable circuits. However, the reference board is not intended to be the final design that ultimately goes into your finished solution. It is tweaked and extended with custom modules, or some modules may be removed. The end product is a customized board that meets the specific needs of your solution.
+The reference implementation is a fully working model, but it's still just a model. Think of it like a reference board in embedded hardware or robotics: a cookie-cutter design with a standard set of modules, inputs, and outputs. It isn't meant to be the final product — it's tweaked, extended with custom modules, or trimmed down until it becomes a customized board that fits your solution.
 
-The same is true for Direct. The reference implementation comes with a standard deployment model and software components such as the security and trust agent, the messaging gateway, a certificate store and a simple web or command line tool for configuration. However, the model does not meet the requirements of an industry-class production system, such as high availability, failover, scalability and disaster recovery. The only edge protocol supported is XD and POP/SMTP, and although this may work well for email clients, innovative edge clients and workflows may need other protocols such as REST, SOAP, and custom authentication and authorization modules.
+The same is true for Direct. The reference implementation ships with a standard deployment model and a set of software components — the security and trust agent, the messaging gateway, a certificate store, and a simple web or command-line configuration tool. It does not, however, meet the requirements of an industry-class production system: high availability, failover, scalability, and disaster recovery. It also supports only the XDR and POP/SMTP edge protocols; other edge clients and workflows may need additional protocols such as REST or SOAP, along with custom authentication and authorization modules.
 
-Finally, the reference implementation does not meet the policy requirements emerging from the various governance agencies. For example, the private certificate store in the reference implementation does not meet auditing requirements for access to private keys. Another example, the auditing subsystem does not write audit events to a storage mechanism with proper access controls. The reference implementation is stubbed to meet these requirements and supports plugging in custom instances of reference implementation interfaces and/or modules. For a HISP to become fully compliant with industry best practices, certificate policies and required operational procedures, investment in infrastructure and some software development is necessary.
+Nor does the reference implementation meet the policy requirements set by various governance agencies. For example, its private certificate store doesn't meet auditing requirements for access to private keys, and its audit subsystem doesn't write events to a storage mechanism with proper access controls. These areas are intentionally stubbed out so you can plug in custom implementations of the reference interfaces and modules to meet them. Becoming a fully compliant HISP — meeting industry best practices, certificate policies, and required operational procedures — takes additional investment in infrastructure and software development.
 
-## Where To Start
-
-If you want to jump right in with both feet and stand up an instance of the reference implementation, the obvious choice is to go to the BareMetal installation page for the Java platform.
-
-If you want to understand the details of the reference implementation componenst and they how fit together, refer to the list of modules in the section below.
-
-If you would like build all components including the BareMetal assembly from source code vs using a prebuilt BareMetal assembly, use the instuctions [here](https://github.com/DirectProjectJavaRI/direct-ri-build)
-
-## Modular Components
-
-The reference implementation adopts a modular design for easy asset reuse and extensibility. Components are available in both .Net and Java.
-
-### Java Components
-
-* [Commons Library](http://api.directproject.info/direct-common/6.0/)
-* [Security And Trust Agent](/docs/agent/)
-* [Gateway](/docs/gateway/)
-* [Message Monitoring](/docs/direct-msg-monitor/)
-* [Policy Enablement](/docs/direct-policy/)
-* [DNS Services](/docs/dns/)
-* [BareMetal Assembly Project](/docs/direct-project-stock/)
+Ready to stand up an instance or explore the individual components? Head over to [Getting Started](/getting-started).