Details

Explore the site’s pages and project files, and see how they fit together.

What you can do

  • Browse the site as an expandable hierarchy of pages.
  • Open individual branches or use Expand all and Collapse all.
  • Open a page directly from its linked label.
  • See how many immediate children each branch contains.
  • Compare page totals, dynamic routes, and counts at each hierarchy level.
  • Browse the project’s actual folders and file names separately from its page URLs.
  • Compare file types and observed App Router naming conventions.
  • Expand every folder, or use a folder’s right-hand button to expand only its subtree.

What to know

  • Pages are grouped by URL path, with Home first and siblings sorted by title.
  • Branches start closed, and their arrow controls work separately from page links.
  • Some dynamic pages share a non-clickable [...] placeholder to keep large branches compact.
  • Each branch counts its direct children, not every descendant; analytics include pages hidden behind compact placeholders.
  • The tree reflects the pages available in the current environment, so a local preview may differ from the public site.

Project file rules

  • Files include tracked and untracked working files that pass Git’s ignore rules, including nested rules and negation. Ignored tracked files are also excluded.
  • Git’s administrative metadata and the generated inventory are excluded. Only file paths are published; file contents and absolute machine paths are not included.
  • Folders appear when they contain included files. The haritssr/ root starts open, other folders start closed, and folders sort before files. Symlinks are listed without following their targets.
  • File names are plain text. The chevron opens one folder; the right-hand subtree button opens that folder and every folder beneath it.
  • Collapse subtree closes descendant folders while keeping the selected folder open. Global controls affect only their own tree.
  • File-type counts use the final extension without regard to case. Dotfiles with no further suffix count as extensionless. Folder counts exclude the root, whose depth is zero.
  • App conventions count matching filenames and folder names under app/. Only observed conventions appear, and these counts overlap file-type totals.
  • During development, the file inventory refreshes when files or repository ignore rules change. The public site shows the inventory generated at deployment.

Understanding the counts

Tree route analytics explained
MetricMeaning
Total pagesAll pages available in the site’s shared index.
Fixed routesPages whose URL is not generated from a dynamic route pattern.
Dynamic route patternsActive URL templates that generate pages, such as /blog/[slug].
Pages generated from dynamic routesIndividual pages produced from those templates.
Route patternsFixed routes plus active dynamic route patterns.
Hierarchy levelsPage counts by URL depth, with Home included in level one.

How it works

Tree uses the same route manifest as search and the sitemap. Page files decide which routes exist, so a new page appears without being registered; curated metadata adds its title and description. The server builds the hierarchy and counts, and the browser handles opening and closing branches. The same generated inventory supplies the project-file tree and its analytics. Closed file branches unmount their contents while retaining expansion state.

Tree components and data flow diagram
Rendering diagram…

Changelog

Messages mentioning Tree or its components, oldest first; dates and times use Jakarta time (WIB).

Loading change history…