creating layout

This commit is contained in:
nathan
2026-07-16 16:36:46 -04:00
parent 8fc2cae0b5
commit 949a50f741
55 changed files with 3790 additions and 0 deletions

69
src/platform/index.njk Normal file
View File

@@ -0,0 +1,69 @@
---
layout: layouts/base.njk
title: The Platform
description: Frame 44 Atlas, the map platform, and Frame 44 Studio, the exhibit builder — the two pieces behind every Frame 44 exhibit.
permalink: /platform/
---
{% from "macros.njk" import ctaBand %}
<section class="hero">
<div class="container hero__inner">
<p class="hero__eyebrow">Platform</p>
<h1>Your team builds in Studio. Everything runs on Atlas.</h1>
<p class="hero__sub">Frame 44 Atlas is the map platform behind every exhibit — the map engine, your historical data, hosting and sync. Frame 44 Studio is where your staff build and edit exhibits — no developer required.</p>
</div>
</section>
<section class="section">
<div class="container">
<h2>Frame 44 Atlas</h2>
<p>The platform underneath every Frame 44 exhibit — the map engine, your historical data, and the infrastructure that keeps it all running.</p>
<ul>
<li>Live MapLibre map integration</li>
<li>Historical map layers and projections</li>
<li>Hosting and content sync</li>
<li>Offline kiosk runtime for gallery screens</li>
<li>Monitoring and support</li>
</ul>
</div>
</section>
<section class="section section--muted">
<div class="container grid grid--2">
<div>
<h2>Frame 44 Studio</h2>
<p>The block-based builder your own staff use to assemble each exhibit — no coding, no developer on standby.</p>
<ul>
<li>Headings, fact panels and timeline cards</li>
<li>Photo and document galleries</li>
<li>Map buttons, overlay toggles and scenario buttons</li>
<li>Themes to match your institution's look</li>
<li>One-click publish and sync workflow</li>
</ul>
</div>
<img src="/assets/images/placeholders/studio-screenshot.svg" alt="Screenshot placeholder of Frame 44 Studio" width="800" height="600" loading="lazy">
</div>
</section>
<section class="section">
<div class="container grid grid--2">
<div class="card">
<h3>Gallery screens</h3>
<p>Kiosk software built to run in a museum, not an office. It works offline on secure networks and syncs new content automatically when it's connected. We monitor and support every screen we install.</p>
</div>
<div class="card">
<h3>Web exhibits</h3>
<p>The same exhibits your visitors touch in the gallery also run on your museum's website — built once, published everywhere, at no extra authoring effort.</p>
</div>
</div>
</section>
<section class="section section--muted">
<div class="container">
<h2>Your team can edit everything, forever</h2>
<p>Once an exhibit is built, it's yours to maintain. Your staff can update text, swap photos, adjust map overlays and publish changes themselves — no ticket, no developer, no waiting.</p>
<p>Your content stays yours — exports in standard formats if you ever leave.</p>
</div>
</section>
{{ ctaBand("See Studio in a live walkthrough.", "We'll show you Frame 44 Studio and answer questions about your specific exhibit.", i18n.cta.bookConversation, site.ctaUrl) }}