REIGN
Get Reign

For K-12 schools

Reign for K-12 schools. School, parent and student intranet.

Build the school site as a private intranet by role: staff groups, a parent area, student resources and a calendar, all behind a login, with BuddyNext spaces per class and Learnomy for homework and materials. Move one annoying process first, usually the newsletter or permission forms. Reign gives the whole site a clean, readable look.

Schools use a classroom tool, a behaviour app and a separate homepage, so parents juggle apps, teachers re-post the same notice in several places and there is no single hub.

Reign + BuddyNext + Learnomy provides a unified school intranet: parent portal, class spaces, homework, announcements and community. Both plugins install free, which matters on a school budget. BuddyPress and LifterLMS work the same way.

Class groups, homework, announcements and document sharing, free to install. You buy the Reign theme; BuddyNext and Learnomy are ours and install free.

  • BuddyNext community engine
  • Learnomy courses
Start with the free plugins Or the BuddyPress Community Bundle kit See the build recipe Have us set it up

Key takeaways for K-12 schools

  • Roles and privacy are the first configuration job, before any feature.
  • Launch one process that visibly works, then spread. Adoption in the first term decides everything.
  • The site sits alongside your management information system and does not replace it.
  • BuddyNext and Learnomy install free, which matters on a school budget. See pricing for the theme licence.

What it looks like on Reign

Screens from the live demos, with sample content. Open any of them and click around.

Three highlights for K-12 schools.

  • 01

    Per-class BuddyNext spaces for homework and parent communication.

  • 02

    School-wide announcements posted in a space every parent can see.

  • 03

    Permission slips and handouts shared as downloads on class pages.

What the site looks like on day one.

You launch with a private intranet: staff groups, a parent area, student resources and a calendar. Access is by role, so parents see announcements and their year group, staff see the staffroom, students see their materials. Nothing is public. For a school the first configuration job is roles and privacy, and it matters more than any feature on the page.

What a member actually does.

Parents arrive for a specific reason, a newsletter or a form, and come back when something useful lives there. Staff adopt it faster if the staffroom replaces an existing mess of email threads. Students use it when the material they need is there and nowhere else. Adoption is won or lost in the first term, and it is won by moving one genuinely annoying process onto the site rather than by launching everything at once.

How this usually makes money.

Most school deployments are not revenue at all, they are cost and communication: replacing a newsletter tool, a file-sharing subscription and a forms service with one site. Where money does move it is usually trips, fundraising or clubs, handled by a commerce plugin. The argument to a governing body is normally consolidation and data control rather than income.

The mistake to avoid.

Launching everything at once for every audience. Parents, staff and students adopting three new areas simultaneously means none of them stick. Move one genuinely annoying process, usually the newsletter or permission forms, and let adoption spread from something that visibly worked.

Which Reign setup fits a school intranet

Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. A school uses it as an intranet, with groups, resources and announcements for different audiences.

BuddyNext provides profiles, spaces and notifications. A space per class holds homework conversations and parent communication, and pinned posts carry school-wide announcements. Learnomy holds course material and quizzes for students. Because everything is private, nothing is published to the public web unless you choose to.

If you already use BuddyPress, the BuddyPress Community Bundle kit is the packaged route, and the enterprise intranet build guide covers a role-based private site step by step. The plugins page shows what is free, and Reign is a flat theme licence with no per-user fee.

Launch steps for a school site

Introduce the site through one thing that people already dislike doing. If it replaces that, adoption follows.

  1. 01

    Map your roles before building: parents, staff, students, governors and visitors. Write down who may see which space.

  2. 02

    Install WordPress with Reign and BuddyNext on hosting your school's IT contact has approved. The hosting guide lists what to ask a host.

  3. 03

    Create the staffroom first, because staff adopt fastest if it replaces a mess of email threads.

  4. 04

    Create one space per year group for parents, with announcements and a calendar. Test the roles by logging in as each type of user.

  5. 05

    Move the newsletter or permission forms onto the site and keep an email route as well, so no parent is left out.

  6. 06

    Name an owner for the site, ideally a teacher with a few hours a week and a technical contact. Meet them each term to fix what is not working.

What staff, parents and students do week to week

Staff open the site on Monday to read notices and check the calendar. A class teacher posts the week's homework in the class space and pins a reminder about a trip form. Parents receive a notification and open the site when the post matters to them.

Parents mostly read. They look for dates, forms and the occasional photo from an activity, and they come back when there is a reason. The more the site holds that they actually need, the more they return, so resist posting everything.

Students use the learning area for resources and quizzes. They might ask a question in the class space rather than emailing a teacher. A teacher can answer once for everyone, which reduces repeated emails.

How a school site grows

Schools grow a site by adding groups, not features. After the newsletter, the next move is usually clubs and trips, then a staff handbook, then a student resources area. Each addition replaces another tool, which is the argument to a governing body.

Consolidation is the main benefit. A single login and a single place for notices replaces a newsletter tool, a file-sharing subscription and a forms service. Document the saving in terms of tools replaced rather than predictions.

Handover matters. Write simple guides for posting and for adding a new class space, and teach a second member of staff. A site that depends on one person disappears when they move on.

How to protect children's data and keep the site safe

A school site holds information about children, and that comes with duties that no theme can handle for you. The safe approach is to hold as little as possible, limit who can see it and write down your decisions. Involve the person responsible for data protection from the first meeting.

Decide what the site never contains. For many schools that means no medical details, no safeguarding records and no assessment data. Those stay in the systems built for them. The site holds notices, resources and conversation, which carry much less risk.

Limit visibility by role. Parents see their child's year group and not others, students see their class, and visitors see the public pages only. Test with a parent, a student and a stranger before launch and again after any change to the structure.

Think about images and names. Agree a policy on photographs, check consent records before posting and avoid naming children where a first name or no name will do.

Keep the software up to date and have a plan for staff changes. When a teacher leaves, their access should end the same day. A short checklist for joiners and leavers is one of the most useful documents a school site can have.

Mistakes specific to school sites

Launching everything at once for every audience is the main one. Parents, staff and students adopting three new areas simultaneously means none of them stick. Pick one process and win it first.

Weak roles are a close second. Retrofitting separation onto a site people already use is hard, so design it in. Test as a parent, a student and a visitor before you invite anyone.

Finally, do not make the site the only channel for anything a parent must see. Keep email or printed notices for safeguarding and urgent matters, so no family is excluded.

When a different setup fits better

If you need a full management information system for attendance and assessment, buy that separately and let this site handle community and communication. The universities page covers larger institutions with alumni and department groups.

If you run an independent tutoring practice rather than a school, the online tutors page is a closer fit.

K-12 school-specific questions.

GDPR / FERPA compliance for student data?

That depends on your host, your settings and your jurisdiction, not on the theme. Expect to need a data processing agreement with the host, two-factor sign-in and access audits. Talk to your school or district IT before storing student personal data.

Can teachers post homework via mobile?

Yes. Teachers can post from a phone browser, and the Reign layout stacks for small screens. Test the posting flow on a phone before you roll it out to staff.

Can we keep parents, staff and students separate?

Yes, with roles and private groups. A parent sees announcements and their child's year group, staff see the staffroom, students see resources. Map the roles before building anything, because retrofitting separation onto a site people already use is considerably harder than designing it in.

Is this safe for student data?

It is your responsibility rather than a vendor's. Use proper hosting, keep everything updated, restrict admin access, and collect the minimum you need. For anything under student-data regulation in your jurisdiction, involve whoever handles that at the school rather than deciding alone.

What about existing school systems?

This sits alongside a management information system rather than replacing it. The site handles community, communication and resources; the MIS keeps being the record of truth for attendance and assessment. Trying to replace an MIS with WordPress is a project that ends badly.

Who administers this day to day?

Someone has to own it, by name, or it decays within a term. That is usually one teacher with an interest plus occasional technical help. Deciding this before launch matters more than any feature choice.

Can parents opt out of the community?

They can simply not use it, but the announcements need a route that reaches everyone, usually email as well as the site. Never make the site the only channel for something a parent must see.

Buy the theme. Add the plugins free.

BuddyNext and Learnomy cost nothing to install, and each has its own Pro plan for later. Running the third-party stack instead? The BuddyPress Community Bundle kit is the packaged route. Or have the Wbcom team set either one up for you.

See the free plugins See the BuddyPress Community Bundle kit Have us set it up

One theme, the whole site

See what you can build with Reign, then try it.

Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. Start with one, add the others when you need them, and keep one login for every member. Open a live demo, or launch a sandbox and get a fresh WordPress site to click through in about a minute.

Add more when you need it

Not sure which setup fits your site?

Tell us what you want members to do on your site. We will tell you which Reign setup, plugins and kit fit, before you buy anything.

Ask us before you buy Email support@wbcomdesigns.com

What customers say on Trustpilot

Love this company

Love this company. Loved the REIGN product. They were there the entire time helping me set things up; and when things went wrong? They were quick to take action and help find a solution.

Fable FortitudeCA