NewBase
Get in touch

Webflow to Astro for EdTech

An education site is a content library with two audiences reading it and a learning platform behind it. The rebuild is where the library gets a proper model and where accessibility stops being an audit finding.

Get in touch

Two audiences, one component system.

Two audiences, and the part they share

The learner

Arrives asking

  • What does it actually do?
  • Is it free, and what does it cost?
  • Does my school already use it?
  • How quickly can I start?

Both

Needed by each

  • Pricing, in their terms
  • Proof from peers
  • Accessibility
  • Data handling

The institution

Arrives asking

  • Is there a VPAT?
  • Security review and SSO
  • Data handling and retention
  • References, and how we buy it
The middle is what both sides need, and it is what most sites write once for the learner and then expect the institution to accept. A rebuild is a reasonable moment to write it twice.

The library moves as a model, not as pages.

Education sites accumulate structured content faster than almost anybody, which is what makes the page count a misleading way to scope the move. Courses, subjects, instructors and materials relate to one another, and those relationships are the part of the migration worth checking record by record.

Course or program One record, many views

Subjects

Resources and guides

Instructors

Learning materials

Subjects
How courses are grouped and found, in the words a learner uses.
Resources and guides
The library that grows weekly, attached to what it supports.
Instructors
People, connected to the courses they actually teach.
Learning materials
The public ones, reusable wherever they belong. The rest stay in the platform.

The stack matters as much as the pages.

Astro The marketing site

What gets decided before an EdTech migration.

  1. 01

    The accessibility standard

    Semantic, keyboard, focus and contrast requirements named before the components are built. A rebuild is the one moment this is cheap rather than retrofitted, which matters in a sector where the question arrives during procurement.

  2. 02

    Who publishes what afterward

    What marketing, curriculum and the other teams can change without a developer, decided as a set of fields rather than discovered in the first week after launch.

  3. 03

    The learning platform boundary

    What moves with the site and what stays in the LMS, the student portal or the product. Nothing behind a login is in scope.

  4. 04

    Whether the library is content or a database

    How courses, subjects, instructors and resources relate, settled before a template is drawn, because this is the decision the rest of the rebuild is shaped by.

Whether COPPA or FERPA applies is a decision for your legal and privacy teams. A product that reaches younger users, or holds institutional records, raises questions that default analytics setups do not address. I implement the collection rules those teams agree on before anything is installed.

Questions about EdTech.

We have hundreds of course and resource pages. How is that scoped?

By how many templates are behind them rather than by the count. Pages generated from a collection move as content against one rebuilt template, which is most of an education library. Pages built one at a time in the Designer are the expensive ones. The first thing worth knowing is which of those you actually have, and the CMS answers it.

Can our team still publish without a developer?

For the content modeled as content, yes, and seasonal work is why it matters. A back-to-school campaign is the most predictable job in this sector and the worst one to queue behind a release, so campaign and subject pages stay CMS content with an editing setup chosen around who publishes them. A page pattern that has never existed becomes a change in the codebase.

What happens to our LMS and student platform connections?

They stay where they are and the site keeps handing off to them. Login, enrollment and anything reading student data are out of scope for the migration, and the work is rebuilding the routes into them and testing each one at its destination.

How is accessibility handled during the rebuild?

Built into the components rather than audited afterward: semantics, keyboard behavior, focus order and contrast, agreed as a standard before the components are written. What that does not do is settle a procurement question for you. A VPAT is a document your organization produces about your product, and the marketing site is one part of what it describes.

Building something else?

Reach out and see if we are a good fit.

Get in touch

Currently booking two to four weeks out.