MORROW / THE NEXT TURN

Getting started

Getting started

Getting started

A practical guide to making MORROW your own while preserving the design system, responsive behavior and connected content that make the template work.

01 / GUIDE

Quick start

Start by making a private remix, then preview the pages before changing anything. Work from the shared system outward so updates stay consistent.

Remix and preview

Create your own remix from the Framer project. Open Preview and check the supplied Desktop, Tablet and Phone breakpoints before editing. Test the navigation menu and page links at each size.

Understand the page structure

The site includes Home, About, Expertise, Work, Perspectives and Contact; Case Studies and Perspectives CMS archives and detail templates; Privacy Policy and Terms of Use sample legal pages; and the Style Guide and Getting Started documentation pages. The legal routes are connected from the shared footer.

Recommended order

Replace the brand assets and global styles first; update shared navigation and footer links; replace page copy and photography; then populate CMS entries and test every route and form.

02 / GUIDE

Branding

MORROW’s active identity is built around ink, warm paper and signal vermilion, with Syne, DM Sans and Newsreader assigning a clear role to each typeface.

Logo and wordmark

Select the shared Brand / Logo component and update its editable logo or wordmark properties. Keep the rising-stripe mark and wordmark proportions legible at all breakpoints. Check both the desktop and mobile navigation variants after replacing the mark.

Global colors

Edit the existing MORROW / color styles in the Assets panel. Active tokens are Ink #151616, Paper #F0EDE5, Signal #F15137, White #FCFAF5, Muted #9B9B93 and Rule #85847F. Prefer these shared styles over local color overrides.

Fonts and brand graphics

Edit the active global text styles to change Syne display typography, DM Sans utility/body typography or Newsreader editorial emphasis. Update the existing rising-stripe mark artwork in place; do not add a near-duplicate style just for one page.

03 / GUIDE

Components

Reusable components keep repeated layouts and interaction states in sync. Edit the source component when a change should appear across the site.

Properties and variants

Select an instance to edit the properties exposed by that component. Use its existing variants for supported layouts and states; available properties differ by component. Preview changes at desktop, tablet and phone widths.

Navigation and footer

The shared Navigation component includes Desktop, Tablet, Phone and Phone Open variants. Keep those variants and their interactions intact. Update link destinations in the existing component. Footer Main is shared across pages; documentation links are grouped under Resources.

Responsive behavior

Avoid fixed widths that force text to break mid-word. Keep the existing stack behavior, responsive visibility and image fitting. Check long headings and labels at the narrowest supported width after changing content.

04 / GUIDE

CMS

Case Studies and Perspectives use native Framer CMS collections and connect their records to archive cards and detail templates.

Case Studies

Add a record with Project Name, Slug, Category, Short Description, Cover Image, Image Alt Text, Client, Year, Services, Overview, Challenge, Approach, Outcome, Gallery, Featured, SEO Title and SEO Description. Save and preview the generated detail route.

Perspectives

Add a record with Article Title, Slug, Category, Excerpt, Cover Image, Image Alt Text, Author, Publication Date, Reading Time, Article Content, Featured, SEO Title and SEO Description. The detail template presents author, date and reading time in a compact group, uses responsive article typography, and links back to /perspectives. Review the archive card and detail page after editing.

Featured content, galleries and SEO

On Home, Featured separates featured entries from supporting entries in both Case Studies and Perspectives sections. The /work and /perspectives archives show all entries. The Case Studies detail template renders the Gallery array and hides its section when Gallery is empty. Both CMS detail templates use each record’s SEO Title and SEO Description for dynamic page metadata. CMS Image Alt Text fields are not dynamically bound to the six Home/detail cover image layers; update each static layer description manually when replacing its image. Check the rendered route and spacing in Preview after edits.

On Home, Featured separates featured entries from supporting entries in both Case Studies and Perspectives sections. The /work and /perspectives archives show all entries. The Case Studies detail template renders the Gallery array and hides its section when Gallery is empty. Both CMS detail templates use each record’s SEO Title and SEO Description for dynamic page metadata. Check the rendered route and spacing in Preview after edits.

05 / GUIDE

Content & photography

Use the native CMS fields and image fills so customers can edit content without changing the layout.

Replace sample copy

Replace demo content with your own services, case studies and articles. Keep titles concise enough for the card composition, and review variable-length content in the CMS detail templates.

Image proportions and optimization

Use landscape images around 3:2 for broad project and article covers, and portrait images around 2:3 for profile photography. Keep the subject within the crop-safe area, export appropriately sized web images, and preview desktop and phone crops. The current Home/About People images are owner-supplied AI illustrations depicting fictional people, not actual staff.

Alternative text and licensing

Write concise, descriptive English alt text for meaningful images; use empty alt text only for decorative imagery. Four CMS-linked Home cover images and the Case Study and Perspective detail covers use static image-layer alt text because the CMS Image Alt Text field cannot be bound dynamically to image elements here. Keep each CMS field accurate, and update the matching Framer image layer’s alt text manually whenever its image changes. Confirm image and license suitability; copyright permission does not automatically grant model, property, trademark or likeness rights.

Write concise, descriptive English alt text for meaningful images; use empty alt text only for decorative imagery. Four CMS-linked Home cover images use static alt text because the CMS Image Alt Text field cannot be bound to those image elements here. Update the alt text manually in Framer whenever one of those Home images changes. Confirm the license permits your intended use. Copyright permission does not automatically grant model, property, trademark or likeness rights; verify any additional permissions needed.

06 / GUIDE

Contact forms

The Contact page uses a native form: Name (required text), Email (required email), Company (optional text), Service Interest (optional text), and Project Description (required resizable multiline text). Its dedicated native submit button handles incomplete, sending, success and error feedback with its own text and status indicators. The separate feedback popup was intentionally removed.

Set the destination

The production form is configured for hello@morrow.studio with the subject “New Project Inquiry.” The owner manually tested the form and verified email delivery, required-field validation, and native submit-button feedback states. Framer may still display an unverified recipient flag in settings; a real test confirmed delivery.

Test the complete flow

In a customer remix, configure the intended recipient and test the form again. Confirm required fields block incomplete submissions, a real test message reaches the configured inbox, and the native button displays its sending, success and error states. All submission feedback in MORROW is handled by the button; no separate popup is used.

07 / GUIDE

Publishing

Finish by checking metadata, legal copy, page behavior and your domain settings in Framer.

Page metadata and sharing

Review the page titles and descriptions. The project already has a MORROW favicon and social sharing image configured in Site Settings; replace them only when rebranding or using approved customer assets. Confirm the site title and description, contact details, and social destinations are your own; the current LinkedIn and Instagram links point to platform homepages and should be replaced with approved profiles. Style Guide and Getting Started are set to noindex; review those settings if customers want the documentation pages indexed. Preview a shared link after any changes.

Legal copy and domain

Privacy Policy and Terms of Use pages are included at /privacy-policy and /terms-of-use, use the shared Base layout, and are linked from the footer. Their editable sample sections and placeholders are not legal advice and are not represented as legally compliant. Replace them with content reviewed for your business and jurisdiction before publishing. Connect your custom domain through Framer Project Settings.

Plan and pre-launch review

Choose a Framer subscription that supports the CMS, custom domain and publishing features your site needs; compare current plan limits in Framer before purchase. Check routes, CMS detail pages, navigation, footer, image alt text, responsive layouts, reduced-motion behavior and a real form submission. The Style Guide project-card preview was checked at 320px and 360px phone widths. Keep /style-guide and /getting-started no-indexed.

08 / FRAMER AGENT

Build with Framer Agent

Open Framer Agent from the top toolbar. MORROW’s seven custom Project Skills are installed and available: /design-system, /rebrand, /brand-voice, /case-study, /perspectives, /seo-check, and /launch-check. Use a skill by naming its slash command in your request. The example prompts below are starting points; remix testing has not been completed. Review any generated page at Desktop, Tablet, and Phone sizes, and verify content, CMS bindings, links, accessibility, and claims before accepting changes.

Design and rebrand

Use /design-system to build a Careers page with MORROW styles, components and Base; ask for the existing responsive grid. Use /rebrand to replace the wordmark, colors and company details while preserving CMS bindings. Example: “Rebrand this remixed copy for Northstar Advisory; show the global changes first and keep existing content unless I approve edits.”

Write and create CMS content

Use /brand-voice to refine page copy in concise professional English. Use /case-study to add an item to the existing Case Studies collection, and /perspectives to draft in the existing Perspectives collection. Examples: “Rewrite this About copy with specific, natural language and no unsupported claims”; “Create a case study from these supplied notes”; “Draft a 900-word perspective from this outline and sources.”

SEO and launch review

Use /seo-check to report page and CMS metadata, headings, alt text, links and sharing metadata issues before broad edits. Use /launch-check to review responsive layouts, links, forms, CMS, accessibility, legal copy, photography, SEO and performance risks. Examples: “Audit SEO and list fixes before changing anything”; “Review this remixed site before launch and mark which checks need manual testing.”

MORROW

Independent strategy advisory for what comes next.

MORROW

Independent strategy advisory for what comes next.

© MORROW 2026

A longer view. A clearer way forward.

MORROW / THE NEXT TURN

Getting started

Getting started

Getting started

A practical guide to making MORROW your own while preserving the design system, responsive behavior and connected content that make the template work.

01 / GUIDE

Quick start

Start by making a private remix, then preview the pages before changing anything. Work from the shared system outward so updates stay consistent.

Remix and preview

Create your own remix from the Framer project. Open Preview and check the supplied Desktop, Tablet and Phone breakpoints before editing. Test the navigation menu and page links at each size.

Understand the page structure

The site includes Home, About, Expertise, Work, Perspectives and Contact; Case Studies and Perspectives CMS archives and detail templates; Privacy Policy and Terms of Use sample legal pages; and the Style Guide and Getting Started documentation pages. The legal routes are connected from the shared footer.

Recommended order

Replace the brand assets and global styles first; update shared navigation and footer links; replace page copy and photography; then populate CMS entries and test every route and form.

02 / GUIDE

Branding

MORROW’s active identity is built around ink, warm paper and signal vermilion, with Syne, DM Sans and Newsreader assigning a clear role to each typeface.

Logo and wordmark

Select the shared Brand / Logo component and update its editable logo or wordmark properties. Keep the rising-stripe mark and wordmark proportions legible at all breakpoints. Check both the desktop and mobile navigation variants after replacing the mark.

Global colors

Edit the existing MORROW / color styles in the Assets panel. Active tokens are Ink #151616, Paper #F0EDE5, Signal #F15137, White #FCFAF5, Muted #9B9B93 and Rule #85847F. Prefer these shared styles over local color overrides.

Fonts and brand graphics

Edit the active global text styles to change Syne display typography, DM Sans utility/body typography or Newsreader editorial emphasis. Update the existing rising-stripe mark artwork in place; do not add a near-duplicate style just for one page.

03 / GUIDE

Components

Reusable components keep repeated layouts and interaction states in sync. Edit the source component when a change should appear across the site.

Properties and variants

Select an instance to edit the properties exposed by that component. Use its existing variants for supported layouts and states; available properties differ by component. Preview changes at desktop, tablet and phone widths.

Navigation and footer

The shared Navigation component includes Desktop, Tablet, Phone and Phone Open variants. Keep those variants and their interactions intact. Update link destinations in the existing component. Footer Main is shared across pages; documentation links are grouped under Resources.

Responsive behavior

Avoid fixed widths that force text to break mid-word. Keep the existing stack behavior, responsive visibility and image fitting. Check long headings and labels at the narrowest supported width after changing content.

04 / GUIDE

CMS

Case Studies and Perspectives use native Framer CMS collections and connect their records to archive cards and detail templates.

Case Studies

Add a record with Project Name, Slug, Category, Short Description, Cover Image, Image Alt Text, Client, Year, Services, Overview, Challenge, Approach, Outcome, Gallery, Featured, SEO Title and SEO Description. Save and preview the generated detail route.

Perspectives

Add a record with Article Title, Slug, Category, Excerpt, Cover Image, Image Alt Text, Author, Publication Date, Reading Time, Article Content, Featured, SEO Title and SEO Description. The detail template presents author, date and reading time in a compact group, uses responsive article typography, and links back to /perspectives. Review the archive card and detail page after editing.

Featured content, galleries and SEO

On Home, Featured separates featured entries from supporting entries in both Case Studies and Perspectives sections. The /work and /perspectives archives show all entries. The Case Studies detail template renders the Gallery array and hides its section when Gallery is empty. Both CMS detail templates use each record’s SEO Title and SEO Description for dynamic page metadata. CMS Image Alt Text fields are not dynamically bound to the six Home/detail cover image layers; update each static layer description manually when replacing its image. Check the rendered route and spacing in Preview after edits.

On Home, Featured separates featured entries from supporting entries in both Case Studies and Perspectives sections. The /work and /perspectives archives show all entries. The Case Studies detail template renders the Gallery array and hides its section when Gallery is empty. Both CMS detail templates use each record’s SEO Title and SEO Description for dynamic page metadata. Check the rendered route and spacing in Preview after edits.

05 / GUIDE

Content & photography

Use the native CMS fields and image fills so customers can edit content without changing the layout.

Replace sample copy

Replace demo content with your own services, case studies and articles. Keep titles concise enough for the card composition, and review variable-length content in the CMS detail templates.

Image proportions and optimization

Use landscape images around 3:2 for broad project and article covers, and portrait images around 2:3 for profile photography. Keep the subject within the crop-safe area, export appropriately sized web images, and preview desktop and phone crops. The current Home/About People images are owner-supplied AI illustrations depicting fictional people, not actual staff.

Alternative text and licensing

Write concise, descriptive English alt text for meaningful images; use empty alt text only for decorative imagery. Four CMS-linked Home cover images and the Case Study and Perspective detail covers use static image-layer alt text because the CMS Image Alt Text field cannot be bound dynamically to image elements here. Keep each CMS field accurate, and update the matching Framer image layer’s alt text manually whenever its image changes. Confirm image and license suitability; copyright permission does not automatically grant model, property, trademark or likeness rights.

Write concise, descriptive English alt text for meaningful images; use empty alt text only for decorative imagery. Four CMS-linked Home cover images use static alt text because the CMS Image Alt Text field cannot be bound to those image elements here. Update the alt text manually in Framer whenever one of those Home images changes. Confirm the license permits your intended use. Copyright permission does not automatically grant model, property, trademark or likeness rights; verify any additional permissions needed.

06 / GUIDE

Contact forms

The Contact page uses a native form: Name (required text), Email (required email), Company (optional text), Service Interest (optional text), and Project Description (required resizable multiline text). Its dedicated native submit button handles incomplete, sending, success and error feedback with its own text and status indicators. The separate feedback popup was intentionally removed.

Set the destination

The production form is configured for hello@morrow.studio with the subject “New Project Inquiry.” The owner manually tested the form and verified email delivery, required-field validation, and native submit-button feedback states. Framer may still display an unverified recipient flag in settings; a real test confirmed delivery.

Test the complete flow

In a customer remix, configure the intended recipient and test the form again. Confirm required fields block incomplete submissions, a real test message reaches the configured inbox, and the native button displays its sending, success and error states. All submission feedback in MORROW is handled by the button; no separate popup is used.

07 / GUIDE

Publishing

Finish by checking metadata, legal copy, page behavior and your domain settings in Framer.

Page metadata and sharing

Review the page titles and descriptions. The project already has a MORROW favicon and social sharing image configured in Site Settings; replace them only when rebranding or using approved customer assets. Confirm the site title and description, contact details, and social destinations are your own; the current LinkedIn and Instagram links point to platform homepages and should be replaced with approved profiles. Style Guide and Getting Started are set to noindex; review those settings if customers want the documentation pages indexed. Preview a shared link after any changes.

Legal copy and domain

Privacy Policy and Terms of Use pages are included at /privacy-policy and /terms-of-use, use the shared Base layout, and are linked from the footer. Their editable sample sections and placeholders are not legal advice and are not represented as legally compliant. Replace them with content reviewed for your business and jurisdiction before publishing. Connect your custom domain through Framer Project Settings.

Plan and pre-launch review

Choose a Framer subscription that supports the CMS, custom domain and publishing features your site needs; compare current plan limits in Framer before purchase. Check routes, CMS detail pages, navigation, footer, image alt text, responsive layouts, reduced-motion behavior and a real form submission. The Style Guide project-card preview was checked at 320px and 360px phone widths. Keep /style-guide and /getting-started no-indexed.

08 / FRAMER AGENT

Build with Framer Agent

Open Framer Agent from the top toolbar. MORROW’s seven custom Project Skills are installed and available: /design-system, /rebrand, /brand-voice, /case-study, /perspectives, /seo-check, and /launch-check. Use a skill by naming its slash command in your request. The example prompts below are starting points; remix testing has not been completed. Review any generated page at Desktop, Tablet, and Phone sizes, and verify content, CMS bindings, links, accessibility, and claims before accepting changes.

Design and rebrand

Use /design-system to build a Careers page with MORROW styles, components and Base; ask for the existing responsive grid. Use /rebrand to replace the wordmark, colors and company details while preserving CMS bindings. Example: “Rebrand this remixed copy for Northstar Advisory; show the global changes first and keep existing content unless I approve edits.”

Write and create CMS content

Use /brand-voice to refine page copy in concise professional English. Use /case-study to add an item to the existing Case Studies collection, and /perspectives to draft in the existing Perspectives collection. Examples: “Rewrite this About copy with specific, natural language and no unsupported claims”; “Create a case study from these supplied notes”; “Draft a 900-word perspective from this outline and sources.”

SEO and launch review

Use /seo-check to report page and CMS metadata, headings, alt text, links and sharing metadata issues before broad edits. Use /launch-check to review responsive layouts, links, forms, CMS, accessibility, legal copy, photography, SEO and performance risks. Examples: “Audit SEO and list fixes before changing anything”; “Review this remixed site before launch and mark which checks need manual testing.”

MORROW

Independent strategy advisory for what comes next.

© MORROW 2026

A longer view. A clearer way forward.

Create a free website with Framer, the website builder loved by startups, designers and agencies.