BeaconCMS/beacon

Expose `page.extra` field in the `@beacon` assign

Open

#465 opened on Apr 29, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (120 forks)batch import
area:contentgood first issueroadmap

Repository metrics

Stars
 (1,194 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The @beacon assign that is managed and build by the BeaconAssigns module holds public data about the current page as the page title, path, and so on. But currently it's missing the extra field which holds the data of custom page fields. We want to expose that data because it's public and useful to build pages.

So when the @beacon is created we want to have @beacon.page.extra with all the data of custom page fields available.

Contributor guide

Research direction
Add the `page.extra` field to the `assigns` map when creating the `@beacon` assign in `BeaconAssigns`. Locate where the assign is built, likely in `Beacon.Web.Live.PageLive` or a module that assembles the assign data. Include the `page.extra` field from the page struct.
Tech stack
elixir
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ElixirPhoenix LiveView
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60