Merge branch 'main' into extensions-phase-2-rc2

Author: sambhav

config.toml

@@ -81,6 +81,21 @@ featureKatacoda = false
   url        = "https://github.com/buildpacks"
   weight     = 4
 
+  [[menu.docs]]
+  name       = "Application Developer Guide"
+  url        = "/docs/app-developer-guide"
+  weight     = 1
+
+  [[menu.docs]]
+  name       = "Buildpack Author Guide"
+  url        = "/docs/buildpack-author-guide"
+  weight     = 2
+
+  [[menu.docs]]
+  name       = "Platform Operator Guide"
+  url        = "/docs/operator-guide/"
+  weight     = 3
+
 [security]
   enableInlineShortcodes = false
   [security.exec]

content/docs/buildpack-author-guide/build-phases-overview.md

@@ -78,7 +78,7 @@ Now that we understand the example application we can step through each of the B
 
 ## Phases
 
-There are five phases to a buildpacks build.  These logic for each phaze is provided by a binary within [`lifecycle`](https://github.com/buildpacks/lifecycle) and the orchestration of running each of the binaries is the responsibility of the Buildpacks platform.  In this case we are using `pack` as our Buildpacks platform.
+There are five phases to a buildpacks build.  These logic for each phase is provided by a binary within [`lifecycle`](https://github.com/buildpacks/lifecycle) and the orchestration of running each of the binaries is the responsibility of the Buildpacks platform.  In this case we are using `pack` as our Buildpacks platform.
 
 At a high-level each layer:
 
@@ -92,7 +92,7 @@ We consider each of the buildpacks phases in the context of our invocation of `p
 
 ### Phase 1: Analyze
 
-The analyze phase checks a registry for previous images called `example`.  It resolves the image metadata making it available to the subsequent restore phaze.  In addition, analyze verifies that we have write access to the registry to create or update the image called `example`.
+The analyze phase checks a registry for previous images called `example`.  It resolves the image metadata making it available to the subsequent restore phase.  In addition, analyze verifies that we have write access to the registry to create or update the image called `example`.
 
 In our case `pack` tells us that there is no previous `example` image.  It provides the output.
 

themes/buildpacks/layouts/partials/header.html

@@ -30,4 +30,14 @@
       <a class="github-button icon-button bg-blue button d-none d-lg-flex" href="https://github.com/buildpacks">GitHub</a>
     </div>
   </nav>
+
+  <nav id="subnav" class="navbar navbar-expand-sm" role="navigation">
+    <ul class="nav navbar-nav">
+      {{ range $.Site.Menus.docs }}
+      <li class="nav-link text-center">
+        <a class="nav-link py-2 py-lg-0 px-1" href="{{.URL}}">{{.Name}}</a>
+      </li>
+      {{ end }}
+    </ul>
+  </nav>
 </header>

themes/buildpacks/layouts/partials/sidebar.html

@@ -52,7 +52,7 @@
   {{- if ne $numberOfPages 0 }}
   {{- $depth = add (int $depth) 1 }}
   <ul class="ml-2">
-    {{- $expand = (or .Params.expand $isCurrent) -}}
+    {{- $expand = (or $isCurrent) -}}
     {{- $pages := (.Pages | union .Sections) }}
     {{- range $pages.ByWeight }}
     {{- if (not .Params.hidden) }}