Seeking Dev. Partners

Edupack seeks institutions, agencies, and other Higher Ed pros to become development partners.

Edupack’s development partners are driven to improve campus website publishing. Each partner meets with Edupack’s team to sculpt the roadmap of features they are interested in. One-on-one meetings take place at the beginning and end of the development of each feature:

Content Governance
Libraries of reusable blocks and patterns.

Automated Archiving
Rules to sunsetting stale content.

Self-service Web Publishing
Control over onboarding & a domain-of-ones-own

Brand Governance
Brand control across large networks.

Trusted .edu tech that supports Higher Ed users.

Accessibility Reporting
Keeping Campus sites accessible.

Edupack has also built a thriving community to help development partners solve solutions to problems that are outside of our roadmap.

Interested in having your ideas coded?

Contact me, blake@edupack.dev, for more information.

Together, we can revolutionize Higher Ed web publishing.

#key-info, #updates

What is Edupack?

Edupack is a WordPress plugin. Our plugin simplifies Higher Ed website management.

Edupack users manage complex website systems. Some of these users maintain self-service, “Domain of One’s Own,” systems. Others maintain a single website for lots of stakeholders. Whatever the complexity, our goal is to streamline the Higher Ed website publishing workflow, from content inception to its sunsetting.

Edupack is also a community.

All core Edupack code is Open Source, published under the GNU General Public License. That means anyone can use Edupack’s core tech for free. We’ve done this so that Higher Ed pros feel free to exchange ideas and code with us (we never want to lock users into proprietary systems!)

We hold monthly meetings with our users to discuss new features and we maintain a Slack channel to discuss anything on the mind of Higher Ed pros. We aim to be as transparent as possible to gain user trust as we develop our solutions (for more info, read our post on transparency).

If you aren’t part of Edupack already, we sincerely hope you’ll join.

Feel free to email me or message me in Slack.

We cannot build the future of Higher Ed without you!


Edupack Transparency

How open is too Open?

We trust you’ll ask questions. We don’t want to bombard you. We trust that you’ll ask for the info you want. We do have several public forums for brainstorming. General ideas fit nicely into Slack’s #general channel. Randomness fits into #random. We email key announcements, and I’m not so sure what P2 is for yet, but “2” rhymes with “true” so… Great Truths might go here?

We never share private information. Our commitment to privacy is built into our service. Edupack isn’t a hosting service. The Edupack plugin currently does not currently collect any of your data (this may change if we need to learn about usage). Data on third-party services (ie- Slack, GitHub, P2, Gmail, …) won’t be shared with any other third party.

We also protect experimentation. Spitball ideas with me, @bbertucc. If you say something is private, I won’t tell a soul. I also encourage folks to share ideas privately with each other before bringing them to the larger group. Hashed-out ideas usually get better traction.

Business decisions and Edupack finances are public (mostly). We sometimes sign NDAs, so we obviously can’t share data that can’t be disclosed. We do aim to share most Edupack financial data. Feedback on profits, losses, investments, and lessons helps us make better business decisions. That said, we maintain employee and partner rights to privacy and never share anything employees or partners do not want us to share.

Anytime we discuss anything privately, we do it to maintain your trust. Your trust is our most precious asset. Our privacy policies work to maintain your trust in Edupack.

Ask your questions!