Files

T

Patrik Oldsberg 10e5d6f8aa Remove NavItemBlueprint in favor of page-based nav discovery

Drop the deprecated NavItemBlueprint from the public API and migrate core
plugins to set title and icon on PageBlueprint instead. AppNav keeps
backward compatibility for legacy nav-item extensions via an internal
core.nav-item.target data ref.

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-19 11:00:46 +02:00

dev

…

src

Remove NavItemBlueprint in favor of page-based nav discovery

2026-05-19 11:00:46 +02:00

.eslintrc.js

…

catalog-info.yaml

…

CHANGELOG.md

Version Packages (next)

2026-04-28 15:53:09 +00:00

config.d.ts

Merge pull request #31683 from beverts312/techdocs-schema

2025-12-13 19:34:13 +01:00

knip-report.md

chore: regenerate knip reports

2026-04-16 12:14:47 +02:00

package.json

Version Packages (next)

2026-04-28 15:53:09 +00:00

README.md

…

report-alpha.api.md

Remove NavItemBlueprint in favor of page-based nav discovery

2026-05-19 11:00:46 +02:00

report.api.md

Updated API reports due to the package change

2026-02-23 06:29:04 -06:00

README.md

TechDocs Plugin

Getting started

Set up Backstage and TechDocs by following our guide on Getting Started.

Configuration

Refer to our configuration reference for a complete listing of configuration options.

TechDocs Storage API

The default setup of TechDocs assumes that your documentation is accessed by reading a page with the format of <storageUrl>/<entity namespace>/<entity kind>/<entity name>. This can be configured by implementing a new techdocs storage API.