See also the community post which allows for better formatting: https://usercommunity.optimizely.com/c/analytics/feature-request-curated-content-blocks-on-the-analytics-home-page

The problem

What we see

Home is a single list of every report, sorted by the date it was last edited. This suits builders, who want the work they touched most recently.

Other audiences meet the same page and face a different task. They want to find the report that matters and trust it.

Newest is not best. A test copy edited today sits above a reviewed report edited last month.

Trusted and experimental reports look the same. A copy named "Dashboard_copy" sits next to an approved report.

Structure is hidden. Folders, such as "Main Reports", appear only as a small tag.

Guidance is hard to find. Warnings, such as "do not edit this dashboard", sit inside report descriptions.

The page is plain. It has no pictures, no pinned items, and no starting point for new users.

Why it matters

Home is the first impression of the whole analytics product. Senior leaders and new users see this page first.

We’re democratising access to data and dashboard building, so we want people to get a full exposure to the platform, this curates the first impression of the platform.

The page works. It does not yet show how much good work sits behind it. This can affect how the product is judged and how widely it is used inside an organisation.

The proposed feature

The idea

Home becomes an ordered list of blocks. Users with edit rights add, move, and remove blocks from a short menu. Nobody needs to write code.

A curated area sits at the top of Home.

All content is the default block. It holds today's sort row, search box, and report list. Nobody can remove it, but an editor can move it up or down.

The header, left nav, create cards, and Filters panel stay as they are.

With no curated blocks, the page is the same as it is now.

Content blocks

Header. Page title, purpose, and optional search.

Callout. Warnings and notices.

Featured report. The one report that matters most, with a picture.

Card grid. Pinned reports with a name, picture, and short description.

Link list. Dense lists with a name, one line of text, and an owner.

Tile row. Navigation by area.

Embedded report. A live, read-only report in a frame.

Mock Up

Page templates

Templates give editors a starting point they can change.

Team hub. Header, callout, featured report, pinned cards, embedded report, link list, and area tiles.

Executive overview. Header, one embedded headline report, and three deep-dive cards.

Getting started. Header, numbered steps, and template cards to copy.

Ways to create the blocks

We would welcome any of these, or a mix.

A. Mark Eting. The editor describes the page in plain words. For example, "a team hub with our five main dashboards and a warning about the read-only report". Mark Eting proposes the blocks, and the editor reviews and changes them. This fits how people already use "Ask Mark".

B. Form builder. The editor adds a block, fills in a short form, and drags blocks to reorder them.

C. Sheet or CSV import. One row per item, with columns for name, description, link, type, owner, and image. This allows bulk edits and version history.

D. Tag driven. Report owners tag a report, and a block fills itself from the tag. This stays current without manual work, but gives less control over order.