> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junojourney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Homepage Views

> Switch between homepage views, pin the cards you check most, and read quiet cards like your due-dates digest and team goals.

export const RoleBadge = ({roles = []}) => {
  const colorMap = {
    Admin: "yellow",
    Manager: "blue",
    Learner: "green",
    "Co-editor": "purple"
  };
  return <>
      {roles.map(role => <span key={role}><Badge color={colorMap[role] || "gray"} size="sm" shape="pill">{role}</Badge>{" "}</span>)}
    </>;
};

export const RelatedPages = ({pages = []}) => {
  if (pages.length === 0) return null;
  return <>
      <br />
      <strong>Related articles</strong>
      <CardGroup cols={2}>
        {pages.map(page => <Card title={page.title} href={page.href} key={page.href} />)}
      </CardGroup>
    </>;
};

Your **Home** page is built from a row of views and a grid of cards underneath it. This guide covers the view switcher, pinning your favorite cards, and reading cards that only show up when there's something to report.

<Note>
  Homepage views are currently in beta. If you don't see a row of view chips above your cards, your organization hasn't turned it on yet.
</Note>

## The view switcher

Above your cards is a row of chips: **For you**, plus any views your organization or you have created.

| Chip            | What it shows                                                |
| --------------- | ------------------------------------------------------------ |
| **For you**     | The default — a blend of everything relevant to your account |
| **Named views** | Views your admin shared with you, or ones you built yourself |

Select a chip to switch. Your choice is remembered the next time you visit. If a chip shows a view your admin created for you, you'll see **Set by your admin** underneath the row.

<Note>
  If you only have **For you**, the chip row is hidden — there's nothing to switch between yet. It appears once you pin a card or an admin shares a view with you.
</Note>

## Cards

Each view fills a row of **three cards**. They come from the view itself: either cards your admin curated into a shared view, or ones you've pinned yourself. A card set to **Large** is wider and takes two of the three slots.

## Pinning a card to "My view"

Any card can be pinned so it always shows up. Open a card's menu (the **⋯** icon) and select **Pin to my view**. Pinning creates a personal view called "My view" if you don't already have one, and switches you to it.

You get **3 pinned slots**. Once they're full, pinning another card opens a dialog asking which one to replace; the card with the least recent activity is suggested first, but you can pick either of the others. To remove a pin, open the card's menu again and select **Unpin from my view**.

## Quiet cards

Some cards only report something when there's a reason to — an overdue assignment, a pending budget request. If you pin one of these and there's nothing to report, the card doesn't disappear or claim a false all-clear: it shows an honest empty state explaining why it's quiet right now. If a card fails to load, it says so too, instead of looking the same as "nothing due."

## Two cards worth knowing

**Upcoming due dates** — everything due soon across your assignments, soonest first. Each row opens the course directly. Nothing due shows as "Nothing due," not an error.

**Your team's goals** <RoleBadge roles={["Manager"]} /> — one row per direct report, showing their goal progress or how many goals they still haven't committed to. A team with no goals yet shows "No goals on your team yet" with a nudge to help them set one.

<RelatedPages
  pages={[
{ href: "/getting-started/home", title: "Your Home Page" },
{ href: "/admin/homepage-views", title: "Homepage Views (Admin)" },
{ href: "/development/goals", title: "Goals" },
]}
/>
