Skip to content

Latest commit

 

History

History
66 lines (36 loc) · 7.71 KB

developer-programmes.md

File metadata and controls

66 lines (36 loc) · 7.71 KB

Developer programmes

The /developer-programmes page renders the page fixture through the shared content loader and CMS page workflow.

Editing

In CMS Pages, open the developer-programmes record and edit its page JSON. The normal content sync imports this fixture after deployment. Saving uses the existing validated GitHub PR workflow against develop; publication follows the normal CMS publishing process.

The developerProgrammesCopy section groups hero, programmes, comparison and choice headings, choiceHelp, principles, statement, and resources. Each programme owns its labels, descriptions, CTA, comparison rows and choice statements. Statistic values, highlight titles and the opportunity rows come from GitHub at build time (see Programme data), so the copy holds only their labels. The RFP build timeline and decision timing are the exception: they stay editorial values. Each programme's CTA and name are reused across the page. Image paths and alternative text are editable alongside the copy. Page title, description and SEO fields use the standard page metadata.

The schema validates both the build-time loader and the CMS save operation. The existing Pages JSON field stores the section without new database fields or a database migration.

The schema fixes some parts of the page structure, and a save that breaks them fails. programmes holds exactly two entries, rfp first and prize second. Each programme needs exactly three stats. For rfp, the first stat holds only a label and the other two hold a label and a value; for prize, all three hold only a label. Each programme's highlight holds only a label. principles.items needs exactly three entries and mobile.programmeImages exactly two. Comparison rows, choice statements and resource items each need at least one entry. Copy and link labels must be non-empty. Image alternative text may be empty, as it is in the fixture. Link destinations go through the shared link check, which rejects unsafe values such as javascript: URLs.

Each programme has a tag for its image panel and a separate comparisonTag for the comparison card. Edit them independently when their wording differs.

Page CTAs use the shared web Button: external HTTP(S) destinations open in a new tab with noopener noreferrer, while internal routes and section anchors stay in the current tab. This applies to desktop and mobile, including the resource links and Discord CTA.

Desktop line breaks

The Figma frame is 1440px wide. Newline escapes (\n) in body copy preserve its desktop line endings at widths of 1440px and above. Edit these breaks with the copy and review the result at 1440px. Below that width, copy wraps to the available space; the large programme and statement headings retain their deliberate breaks.

Mobile layout

Below 768px, the page follows the 393px mobile frame and expanded Prize card. Programme cards start closed and can be expanded independently. The comparison uses paired columns, followed by centred choice capsules, ruled principles, a compact statement and resource rows.

Desktop and mobile share the desktop Figma copy. Editing a heading, comparison tag or row, choice statement, or statement paragraph updates both layouts. The comparison keeps each programme's own label when the two columns use different wording. The section's mobile object contains only the expand/collapse labels and programme card images. Heading newlines preserve the mobile line breaks while desktop headings render on one line. Refresh existing CMS drafts from the fixture before editing.

Mobile CTA dimensions follow Figma. Tablet widths from 768px to 1439px retain 44px minimum CTA targets. Desktop CTA dimensions retain the Figma measurements.

The RFP statistics give the longer delivery-time value a wider middle column on desktop, correcting an overlap in the supplied Figma frame without changing the copy or type size. Edited statistics wrap within their columns.

{mark} inserts the shared Logos mark in programme names, headings and body copy. Keep that token wherever the brand mark should appear. Do not replace it with an image or a Unicode substitute.

Programme data

The page loads its copy together with the RFP data from rfp-programme.ts and the prize data from lambda-programme.ts, the same GitHub sources behind the RFP and Lambda Prize pages. The programme summaries merge them with the copy, and the desktop and mobile programme cards both render the result. The summary uses published RFP statuses. The site refreshes these values when it is rebuilt and published.

For the RFP programme:

  • The first stat shows the number of published RFPs, whatever their status. The other two stats keep their values from the copy.
  • The highlight shows the number and title of the first open RFP. With no open RFP, the highlight is hidden.
  • Up to two opportunity rows list the next open RFPs, then upcoming ones, each with its status label from the RFP page's listing.statuses.

For the Lambda Prize programme:

  • The three stats show the number of open prizes, the total of their amounts and the number of awarded prizes.
  • The highlight shows the ID, title and amount of the largest open prize, and is hidden when no prize is open.
  • Up to two opportunity rows list other open prizes with their amounts.
  • The availability line comes from the programmeData.availability message in messages/en.json.

The Builder Programmes panels on Get Started and Builders Hub share the same data. They show up to four open RFPs with links to their details and the first open featured prize. If no featured prize is open, the panel shows the next open prize in the list. If there are no open prizes, the programme link stays visible.

Monospace font

The page uses Fira Code through programmeMono from the generated Google fonts module, which exposes it as --developer-programmes-mono (weights 400 to 600). /lambda-prize and /rfp use the same font. fonts.md covers how the fonts are generated.

Images

The image component serves the three bundled backgrounds through responsive AVIF sources at 640, 1280, 1920 and 2560px, with WebP alternatives for browsers without AVIF support. The original exports remain unchanged. On desktop the first programme image loads eagerly and the other backgrounds load lazily; the small mobile programme card images load eagerly. Custom image paths entered in CMS use their supplied source directly.

Dark section backgrounds keep the overlaid text readable while images load or if a request fails.

Background picture elements are absolutely positioned so they do not occupy a grid column or push section copy into another row.

After replacing a bundled original, run pnpm --filter web generate:programme-images and commit the regenerated variants. The generator preserves the source aspect ratio and uses AVIF quality 60 and WebP quality 90. Review desktop and mobile crops before publishing.