# `MishkaCmsCore.Dev.SiteAPages`
[🔗](https://github.com/mishka-group/mishka_cms_core/blob/v0.0.1/lib/mishka_cms_core/dev/site_a_pages.ex#L5)

What `site-a` answers on top of the starter site: a small company, with a showcase page
(`/:lang/showcase`, linked from the header; `/` is the starter's own home, as on every dev site), a
services list, one page per service and a team page built out of the site's own media library.

A second site exists in the dev seeds to make the tenant boundary visible — the same component
names, the same layout name and the same addresses, all resolving to this site's own rows. See
`MishkaCmsCore.Dev.LocalhostPages` for why one module per site.

# `nav`

```elixir
@spec nav() :: [{String.t(), String.t()}]
```

The header links the layout is built with — see `MishkaCmsCore.Install.StarterContent`.

# `pages`

```elixir
@spec pages(%{required(atom()) => [String.t()]}) :: [map()]
```

The pages, as `MishkaCmsCore.Runtime.PageProvision` definitions.

`pictures` is `MishkaCmsCore.Dev.SeedMedia.images/1` for this site — the team page is written out
of it, so the faces on it are rows in this site's own library rather than paths into a directory
that may hold nothing.

---

*Consult [api-reference.md](api-reference.md) for complete listing*