Content Navigation
Overview
- Renders each row as a clickable navigation tile with a colored icon, a label, and a short description
- Makes the whole tile one large link, so the entire card is easy to click – not just the text
- Color-codes the icon by category, so a hub of links reads by type at a glance
- Uses a Choice column to pick the icon, so editors add a link without ever touching the JSON
- Applied as column-formatting JSON on the label column, so it changes the look without changing the data
- Any row with an unmapped icon falls back to a neutral link tile instead of looking broken
Common Use Cases
- A department or team landing page
- An intranet quick-links or hub menu
- A resource or knowledge-base index
- An onboarding start-here list
- A set of app or system shortcuts
- A curated links list on a project site
Details
- Design Pattern: Cards & Tiles
- Format Scope: Column
Required Columns
| Display name | Column type | Internal name |
|---|---|---|
| Label | Single line of text | [Title] |
| URL | Hyperlink | [Url] |
| Description | Single line of text | [Description] |
| Icon | Choice | [Icon] |
Prerequisites
- Build a list with these columns before you paste the JSON.
- Then add a row per destination – a label, the link, a short description, and an icon.
- Internal column names (in brackets) must match the JSON exactly.
- The icons key off the choice values Docs, Forms, People, Help, and Data – use these exact words or edit them in the JSON to match yours (anything else gets a neutral link icon).
- Create the destination field as a Hyperlink column, not an Image or Picture column.
- Use destination URLs the client users can open – the tile opens the link in a new tab but cannot bypass SharePoint, page, file, or form permissions.
How to Apply JSON code
- Select the Label column header, then Column settings, then Format this column.
- Switch to Advanced mode.
- Paste the JSON below and click Save.
- Widen the Label column and hide the others so each tile has room.
- Keep the view in List layout so the whole tile stays clickable.
JSON Code
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",
"elmType": "a",
"attributes": {
"href": "[$Url]",
"target": "_blank",
"title": "=('Open ' + @currentField)"
},
"style": {
"display": "flex",
"flex-direction": "row",
"align-items": "center",
"gap": "14px",
"padding": "12px 16px",
"margin": "6px 0",
"background-color": "#ffffff",
"border": "1px solid #e5e7eb",
"border-radius": "12px",
"box-shadow": "0 1px 2px rgba(0,0,0,0.08)",
"text-decoration": "none",
"box-sizing": "border-box",
"cursor": "pointer"
},
"children": [
{
"elmType": "div",
"style": {
"flex-shrink": "0",
"width": "46px",
"height": "46px",
"border-radius": "10px",
"display": "flex",
"align-items": "center",
"justify-content": "center",
"font-size": "22px",
"background-color": "=if([$Icon] == 'Docs', '#e5f0fa', if([$Icon] == 'Forms', '#e3f2f1', if([$Icon] == 'People', '#efe9f7', if([$Icon] == 'Help', '#fbe9df', if([$Icon] == 'Data', '#e7f5ec', '#f0f0f0')))))"
},
"txtContent": "=if([$Icon] == 'Docs', '📄', if([$Icon] == 'Forms', '📝', if([$Icon] == 'People', '👥', if([$Icon] == 'Help', '🛟', if([$Icon] == 'Data', '📊', '🔗')))))"
},
{
"elmType": "div",
"style": {
"flex-grow": "1",
"display": "flex",
"flex-direction": "column",
"gap": "2px",
"min-width": "0"
},
"children": [
{
"elmType": "div",
"style": {
"font-size": "16px",
"font-weight": "700",
"color": "#201f1e",
"white-space": "nowrap",
"overflow": "hidden",
"text-overflow": "ellipsis"
},
"txtContent": "@currentField"
},
{
"elmType": "div",
"style": {
"font-size": "13px",
"font-weight": "500",
"color": "#5a5a5a",
"white-space": "nowrap",
"overflow": "hidden",
"text-overflow": "ellipsis"
},
"txtContent": "[$Description]"
}
]
},
{
"elmType": "div",
"style": {
"flex-shrink": "0",
"font-size": "22px",
"font-weight": "700",
"color": "#a19f9d",
"padding-right": "4px"
},
"txtContent": "›"
}
]
}
Common Questions About the Content Navigation
What is the Content Navigation example built with?
It is built with a standard Microsoft List (SharePoint list) and a small piece of column-formatting JSON applied to the label column. There is no custom development, no SPFx solution, and no third-party tools. It is the kind of clean, maintainable navigation Greg Zelfond builds for teams that want a friendly hub of links without ongoing development overhead.
What columns does it need?
It needs four columns: the label (the built-in Title), a hyperlink for the destination, a text description, and a choice column for the icon. The tile refers to these by their internal names, so the JSON and the columns must line up – in this example those internal names are Url, Description, and Icon.
Is the whole tile clickable, or just the text?
The whole tile is a single link, so people can click anywhere on the card to go to the destination. Because the entire tile is clickable, keep the view in the List layout – inner links like this do not work inside the Gallery (tiles) layout.
Does this design use any custom development or third-party tools?
No. It uses only out-of-the-box SharePoint column formatting, which Microsoft supports natively. That keeps it stable and easy to maintain, and nothing breaks when SharePoint is updated. Out-of-the-box is the only way Greg builds, so you can own and extend the design yourself for years.
If LookBook 365 is code-free and out-of-the-box, why does this example include JSON?
Because SharePoint formatting JSON is not custom code – it is a native configuration feature built into lists and libraries. It is declarative: it only describes how an existing column looks and where its link points, and cannot run scripts, reach external services, or change your data. Nothing is deployed and nothing breaks when Microsoft updates SharePoint, and you can edit or remove it anytime. That is why LookBook 365 treats it as out-of-the-box and low risk.
Can Greg build a navigation hub like this for our intranet?
Yes – this is exactly the kind of work Greg Zelfond does. As an independent SharePoint consultant and Microsoft MVP, he designs out-of-the-box list and library formatting like this so your team can read and maintain it without a developer. Reach out through the contact page to talk about your hub.
