feat(website): link the Screenly shop so visitors can buy a player

[vpetersson-bot]

Issues Fixed

No issue. Visitors had no way to buy hardware from the site: the Anthias Player Mk2 is on sale in the Screenly shop, but nothing on anthias.screenly.io linked to it.

Description

Adds a direct buying path to the shop listing, in three places:

• Home page hero: a Buy a Player button next to Get Started and See Features.
• Main nav: a Buy a Player entry, so the link is on every page (desktop and mobile), using the existing external-menu handling.
• FAQ: a new "Can I buy a ready-made Anthias player?" entry in the About group, right after "What hardware do I need?". Specs are quoted from the listing (fanless arm64, 4 GB RAM, 16 GB industrial-grade flash, cables in the box), plus the fact that one player runs one screen. It states plainly that the player ships without Anthias installed and that buying hardware is optional, and links out for price and shipping rather than quoting a price the site would have to keep in sync.

Each link is UTM-tagged with the existing house pattern (utm_source=anthias.screenly.io, utm_medium=referral). The campaign is buy-a-player for all three, with utm_content naming the placement (home-hero, nav, faq), so we can tell which surface actually drives orders. That is a small extension of the current convention, which encodes placement in the campaign and does not use utm_content yet; happy to flatten it if you would rather keep one dimension.

Because the FAQ layout builds FAQPage structured data from data/faq.yaml, the new question also lands in the page's JSON-LD.

Verified with a local Hugo 0.157.0 extended build (same version CI installs): builds clean, and the link renders in the hero, in both nav variants, and in the FAQ answer.

Review follow-ups

• Escaped the ampersands in the hero link's query string as &, matching every other query-string link in layouts/index.html.
• Dropped the "can drive a 4K display" sentence from the FAQ answer. The listing's spec list says 4K Support: No and its description says 1080p Full HD, and our own per-board notes agree with the listing rather than with the claim, so the site should not assert 4K.

One thing about the listing itself, outside this repo: the product is currently UNLISTED in Shopify, so it will not appear in the shop's search or collections even though the product page is live and Add to cart works.

Separately, the listing is internally inconsistent about the board and is worth a tidy-up: the SKU is SP-RP4B4G0001 (Pi 4B) while the description says it "uses Raspberry Pi 5 hardware". The Pi 5 description is the correct one, so the stale SKU is the part to fix.

Checklist

• I have performed a self-review of my own code.
• New and existing unit tests pass locally and on CI with my changes.
• I have done an end-to-end test for Raspberry Pi devices.
• I have tested my changes for x86 devices.
• I added a documentation for the changes I have made (when necessary).

Device testing and the unit suite do not apply: this touches the marketing site only, no device or application code. Verification was the local Hugo build described above.

[Copilot]

Pull request overview

Adds clear paths from the Anthias marketing site to the Screenly shop listing for the Anthias Player Mk2, so visitors can directly purchase supported hardware.

Changes:

• Adds a “Buy a Player” CTA button in the home page hero linking to the Shopify product page with UTM tags.
• Adds a persistent “Buy a Player” item to the main navigation menu (desktop + mobile) using the existing external-link menu handling.
• Adds an FAQ entry explaining the ready-made player option and linking to the shop listing.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
website/layouts/index.html	Adds a hero CTA button linking to the shop product page.
website/hugo.toml	Adds a new main-nav menu entry for the shop link (external).
website/data/faq.yaml	Adds a new FAQ Q/A about buying the Anthias Player Mk2 with a shop link.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (2)

website/layouts/index.html:16

• In HTML attribute values, query-string separators should be HTML-escaped as & (as elsewhere in this file) to keep the template output valid HTML. The current href includes raw & characters.

                <a class="btn-secondary" href="https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&amp;utm_medium=referral&amp;utm_campaign=buy-a-player&amp;utm_content=home-hero" target="_blank" rel="noopener">Buy a Player</a>

website/data/faq.yaml:28

• This FAQ answer asserts the Player Mk2 "can drive a 4K display", but the linked shop listing (the cited source of specs per the PR description) currently states 1080p / no 4K support. To avoid publishing potentially incorrect specs, consider removing the 4K claim (or adjusting it to match the listing).

    - question: Can I buy a ready-made Anthias player?
      answer: |
        Yes. Screenly sells the **Anthias Player Mk2**, a fanless arm64 player with 4 GB of RAM, 16 GB of industrial-grade flash storage, and the power, Ethernet, and HDMI cables in the box. It can drive a 4K display, and one player runs one screen, so order one player per screen. See the [Screenly shop](https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&utm_medium=referral&utm_campaign=buy-a-player&utm_content=faq) for the current price and shipping.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (3)

website/hugo.toml:36

• The site’s existing UTM convention appears to use utm_source/utm_medium/utm_campaign only (no utm_content), with placement encoded in the campaign (e.g. website/hugo.toml:23 uses utm_campaign=nav). This menu URL adds utm_content=nav, which is inconsistent with the rest of the site’s tracking links.

  [[menus.main]]
    name = 'Buy a Player'
    url = 'https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&utm_medium=referral&utm_campaign=buy-a-player&utm_content=nav'
    weight = 22
    [menus.main.params]
      external = true

website/layouts/index.html:16

• The site’s existing UTM convention appears to encode placement in utm_campaign and does not use utm_content (e.g. website/hugo.toml:23 uses utm_campaign=nav, and website/layouts/index.html:257 uses utm_campaign=home-body). This link introduces utm_content=home-hero, which makes tracking parameters inconsistent across the site.

                <a class="btn-secondary" href="https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&amp;utm_medium=referral&amp;utm_campaign=buy-a-player&amp;utm_content=home-hero" target="_blank" rel="noopener">Buy a Player</a>

website/data/faq.yaml:30

• This new outbound link introduces utm_content=faq. Elsewhere on the site, UTM tags appear to omit utm_content and encode placement in utm_campaign (see e.g. website/layouts/index.html:257 and website/hugo.toml:23). Mixing conventions will make analytics harder to compare across link surfaces.

    - question: Can I buy a ready-made Anthias player?
      answer: |
        Yes. Screenly sells the **Anthias Player Mk2**, a fanless arm64 player with 4 GB of RAM, 16 GB of industrial-grade flash storage, and the power, Ethernet, and HDMI cables in the box. It can drive a 4K display, and one player runs one screen, so order one player per screen. See the [Screenly shop](https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&utm_medium=referral&utm_campaign=buy-a-player&utm_content=faq) for the current price and shipping.

        The player is hardware only: Anthias is not preinstalled, so you install the free software yourself the same way you would on any other supported board. Buying hardware is entirely optional, since Anthias runs just as well on a Raspberry Pi or PC you already own.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

website/hugo.toml:36

• Menu weights in this file consistently use multiples of 5/10 (10, 15, 20, 25, 30, 40, 50). Setting this new entry to 22 breaks that established spacing and makes future insertions harder; consider shifting subsequent weights so everything stays on the same 5-step grid while keeping the same visual order.

  [[menus.main]]
    name = 'Buy a Player'
    url = 'https://shop.screenly.io/products/anthias-player-mk2?utm_source=anthias.screenly.io&utm_medium=referral&utm_campaign=buy-a-player&utm_content=nav'
    weight = 22
    [menus.main.params]
      external = true

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.