Skip to content

Clarify nav-v2 styling port scope for #3256 and provide exact commits to cherry-pick#3275

Draft
Copilot wants to merge 7 commits into
demo/findabilityfrom
copilot/sub-pr-2927
Draft

Clarify nav-v2 styling port scope for #3256 and provide exact commits to cherry-pick#3275
Copilot wants to merge 7 commits into
demo/findabilityfrom
copilot/sub-pr-2927

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 8, 2026

This follow-up addresses the request to port the “2927 styling improvements” into the #3256 line. The key outcome is confirming the requested styling work is already present on this branch and documenting the exact commits to apply downstream.

  • Scope clarified

    • Identified the requested “last four commits” tied to the nav-v2 styling/UI adjustments.
    • Confirmed the relevant changes are already in this branch history (not newly reimplemented).
  • Porting guidance provided

    • Shared the precise commit set to apply onto #3256:
      • d842694 — folder click activation / parent state
      • f035fad — sidebar spacing + active/TOC color tuning
      • 5defb05 — TOC font/utility-link weight adjustments
      • 3b6428b — related nav wiring context
  • Reviewer-facing verification artifact

    • Included the preview URL for quick visual confirmation of the styling state.
# apply onto the target #3256 branch
git cherry-pick d842694 f035fad 5defb05 3b6428b

itsalexcm and others added 7 commits May 4, 2026 16:29
Fix CI npm fmt:check on pages-nav-v2.ts and styles.css.

Co-authored-by: Cursor <cursoragent@cursor.com>
Backports the YAML fill from demo/findability (PR #3268). Pure additions
to config/navigation-v2.yml within the existing structure — no schema
changes, no new directives. Closes most of the gap between v1 nav and
the nav-v2 prototype.

- Re-enable the commented Reference label and expand it: docs-content
  reference (top-level fanout), elasticsearch core/plugins/community-
  contributed, kibana, Cloud (cloud + cloud-on-k8s), Elasticsearch
  clients (java/js/dsl-js/.net/php/py/ruby/rs, eland, go-elasticsearch,
  curator), APM (k8s-attacher, aws-lambda, all agent libs), OpenTelemetry
  (opentelemetry root + motlp + edot-cloud-forwarder for AWS/Azure/GCP,
  edot-collector, all EDOT SDKs), ECS Logging (root + all per-language
  libs), beats, logstash, integration-docs, elasticsearch-hadoop,
  elastic-serverless-forwarder, ecs, search-ui, ecctl, plus
  aggregations/enrich-processor/query-languages/scripting-languages/
  text-analysis. ~1,200 pages.

- Wire children of 12 deploy-manage landings (security, users-roles,
  monitor, tools, remote-clusters, upgrade, cloud-organization,
  maintenance, api-keys, autoscaling, license, uninstall) under each
  existing `- group:` to preserve curated titles. ~370 pages.

- Convert distributed-architecture leaf entries into groups with
  canonical children: clusters-nodes-shards (node-roles),
  shard-allocation-relocation-recovery (shard-allocation-awareness +
  index-level-shard-allocation w/ delaying-allocation-when-node-leaves),
  discovery-cluster-formation (6 children).

- Convert production-guidance leaf entries into groups with their
  full canonical structure: Run Elasticsearch in production (Design
  for resilience [3 children], Scaling considerations, Performance
  optimizations [6 children]); Run Kibana in production (6 children).

- Convert ingest-reference-architectures leaf into a group with the
  16 canonical children grouped by architecture (Agent to Elasticsearch,
  Agent with Logstash, Agent with Kafka, Air-gapped, Logstash as input,
  Agent through a proxy). Set ingesting-data-for-elastic-solutions.md
  as the "Ingest by solution" group landing. Surface
  manage-data/ingest/tools.md alongside the existing API/upload entries.

- Add Release notes top-level label with the per-product release-notes
  tree (Elasticsearch + clients + Hadoop, Kibana, Elastic Agent,
  Fleet Server, Logstash, Beats, Serverless, Cloud Hosted, Cloud
  Enterprise, Cloud on K8s, Observability with EDOT SDKs and APM
  agents, Security, ECS, ECCTL).

- Add Troubleshoot top-level label as `- toc: docs-content://troubleshoot`
  (covers ~190 pages). Delete the dead Troubleshooting comment block
  whose entries are all already reachable via that toc.

- Replace 57 `{{templated}}` substitution tokens (in titles AND group
  labels) with their literal expansions per docs-content/docset.yml::
  features. The nav renderer does not expand `{{...}}` so leaving
  them caused literal `{{ece}}` etc. to render in the sidebar.

Skipped (depends on features added in later layers of the stack):
- Liam's Search and query rewrite (PR #3094, against this branch).
- Products section (introduced in hub-pages).
- island: entries (Logstash plugins/versioned plugins; needs
  nav-v2-sections).
- Observability page additions on demo (slot under groups added in
  hub-pages stack).

YAML valid. 173/173 navigation tests pass.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Ensure folder rows stay expanded on first re-activation click and introduce an explicit immediate-parent active marker while preserving full ancestor state styling.

Co-authored-by: Cursor <cursoragent@cursor.com>
Align top-level label spacing and active-row visuals with the latest nav spec, and make the right-side On this page links/border keep the nav text color on hover.

Co-authored-by: Cursor <cursoragent@cursor.com>
Switch sidebar utility links and the On this page heading container to the body font stack and normal weight to match the rest of the navigation typography.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

# Conflicts:
#	src/Elastic.Documentation.Site/Navigation/IsolatedBuildNavigationHtmlWriter.cs
#	src/Elastic.Documentation.Site/Navigation/NavigationViewModel.cs
#	src/Elastic.Documentation.Site/Navigation/_TocTree.cshtml
#	src/Elastic.Documentation.Site/Navigation/_TocTreeNav.cshtml
Copilot AI changed the title [WIP] Prototype nav-v2: new IA with label sections, accordion sidebar Clarify nav-v2 styling port scope for #3256 and provide exact commits to cherry-pick May 8, 2026
Copilot AI requested a review from theletterf May 8, 2026 10:53
@theletterf
Copy link
Copy Markdown
Member

@copilot Target branch is wrong. It should be the one from the 3256 PR...

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 8, 2026

@copilot Target branch is wrong. It should be the one from the 3256 PR...

You’re right — PR #3275 is currently based on nav-v2. I can’t retarget the PR base from this environment, so please switch the base branch in GitHub to the branch used by #3256 (keeping head copilot/sub-pr-2927). No code changes were needed for this (28dc935).

Screenshot/preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/2927/get-started

@theletterf theletterf changed the base branch from nav-v2 to demo/findability May 8, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants