{
  "context": "Evaluates how the solution uses mkdocs-awesome-pages-plugin to build explicit navigation entries for pages, directories, nested sections, and external links. Checks rely on plugin-specific constructs in mkdocs.yml and .pages navigation files.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin enabled",
      "description": "`mkdocs.yml` registers the `awesome-pages` plugin (`AwesomePagesPlugin`) so `.pages` files are processed, keeping the filename configuration aligned with `.pages`.",
      "max_score": 15
    },
    {
      "name": "Top-level order",
      "description": "Root `.pages` `nav` uses ordered `MetaNavItem` entries to map `index.md`, `overview.md`, `api/`, and the external link with the exact titles `Home`, `Overview`, `API Reference`, and `Project Website` in the specified sequence.",
      "max_score": 30
    },
    {
      "name": "Guides section",
      "description": "A nested `nav` block creates the `Guides` section (via the dict-plus-list form that `MetaNavItem.from_yaml` parses), explicitly listing `guides/intro.md` as `Getting Started` then `guides/advanced.md` as `Deep Dive`.",
      "max_score": 25
    },
    {
      "name": "API directory entry",
      "description": "Navigation includes `api/` as a directory entry (not flattened rest patterns) so the plugin renders an `API Reference` Section/VirtualSection with the folder's `index.md` leading and other API pages preserved in folder order.",
      "max_score": 20
    },
    {
      "name": "External link",
      "description": "The final `nav` item is a URL entry that mkdocs-awesome-pages-plugin recognizes as a Link, titled `Project Website` and pointing to `https://example.com/docs`.",
      "max_score": 10
    }
  ]
}