Oogle

schools, colleges, programs and course platforms

Four audiences, one homepage, and an enrollment decision.

Education websites serve prospective students, current students, parents and staff at the same time, and most are organized around the institution rather than any of them.

THE STRUCTURAL PROBLEM

Education sites carry more content than almost any other category, and most of it's written for one audience and read by another.

Jobs competing for the same homepage.

Two audiences are in a hurry. Two are deciding something significant.

Convince a prospective student or parent

Programs, outcomes, cost, requirements and what it's actually like.

Get them through enrollment

Applications, deadlines, requirements and payment, without losing people.

Serve current students and parents

Calendars, closures, contacts and forms. Fast and dull.

Present programs consistently

So a program shows up right everywhere rather than being maintained in four places.

Deliver learning where it applies

Courses and materials, built or connected to a platform you have.

Where the audiences collide.

One site trying to be four

Prospective students, current students, parents and staff sharing a navigation that serves none of them well.

Program information in several places

The catalog, the program page, a PDF and a department page, each slightly different and each maintained separately.

Enrollment steps that leak

Long forms, unclear requirements, deadlines that are hard to find, and no way to save progress.

What schools and training providers ask.

Should the learning platform be part of the website?

Usually not. Established learning platforms do a great deal that would be expensive to rebuild. The work is making the transition between the two clear so students don't feel like they've been thrown somewhere else, and integrating them where it saves administration.

Can departments publish their own content?

Yes, and they should, otherwise it doesn't happen. The structure has to carry the consistency so that permission doesn't fragment the site. That's a content modeling problem rather than a policy one.

Our program information is in four places.

Extremely common, and the fix is structural. One record per program, presented everywhere it appears. It usually removes a recurring administrative burden as well as the inconsistency.

Site serving four audiences badly?

Tell us who the four are and what each one arrives to do. Separating them is usually the whole conversation.