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.
Automate archival policies with Edupack’s 0.0.2 version. From Edupack’s new Network Admin tab, send automated warning emails and archive stale sites. Super admins can also set exemptions for sites that shouldn’t be archived.
Version 0.0.2 also allows Super Admins to hide/show site publishing permissions for network users. The site publishing permissions allows users to manually archive sites, so that sites can be hidden from the public.
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.
Integrations Trusted .edu tech that supports Higher Ed users.
The Blocksy theme already saves coding time. Their GUI style controls cover 80% of what designers can imagine. FSE provides additional global style settings that could, theoretically, make custom themes useless. Designers could design their site within WordPress without needing mockups or coding expertise.
For Higher Ed pros, block-based style controls also provide better management over user capabilities. That means accessibility and branding policies can be policed at a code level instead of through visual, human tests.
For those reasons, the future is bright for FSE.
Unfortunately, FSE’s bright future is probably not coming soon.
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.
I’m in charge of Edupack’s outreach. I’m also trying to keep our Slack channels focused by publishing the goals behind our communication and work. This post establishes the motivation behind the #outreach group on Slack.
From user onboarding to content sunsetting, Edupack aims to simplify Higher Ed web publishing. To reach our bold vision, Edupack is launching an outreach initiative in three phases (enumerated with domain names 😉):
1. Find Good Ideas & Dream Big (joinedupack.com)
Our first phase of outreach needs to promote brainstorming.
Imagine.. Higher Ed web publishing simplified into a single framework of standards and tech..
We are at the start of a big project. The potential is endless, and we should promote big ideas while we can.
2. Deliver Features (edupack.dev)
Once we have all the ideas we can handle, we’ll focus on delivering features. Our features must live up to the dreams of Higher Ed Pros. @nathansmonk and his team are working hard to turn dreams into a reality.
Our aim is to have Higher Ed pros using our plugin as quickly as possible. We want our development to be guided by real user stories.
3. Sustain Openness (edupack.co)
We plan to sustain our open core through support services. We love the idea of support services because companies are literally paying us to ensure our code is great and our systems are functional.
I hope that the dreamers and early users who contribute to Edupack become our biggest cheerleaders. Our cheerleaders can push Higher Ed institutions to pay for our services.
Edupack caters to every Higher Ed stakeholder. From I.T. admins to professors and students, approved campus users can publish content without design or coding expertise. At our February meeting, Matt presented the following onboarding design iterations.
How are we designing the easiest onboarding in Higher Ed? Answer: Iterate, iterate, iterate…
Our First Iteration
Our first iteration was built around a simple form collecting key pieces of information. The user entered their desired domain, keywords, and selected a “type” of site. Once complete, the user moved to add content from a library of pre-defined blocks.
This raised further questions, such as:
How do we make the pattern library scalable? With space in the sidebar limited, a large number of patterns would be difficult to navigate.
How would a user add functionality to the site?
“Site Type” was confusing to a user. Users who had no knowledge of different site types needed to see what each site type meant.
To clarify “site types,” we gave visual examples of different site types.
We added the ability for users to start with a blank canvas. This gives experienced users total control over what content they add.
More questions arose:
Is there a better way to add new pages?
How are relationships between pages created?
How do we deal with endlessly expanding site types?
Users often know what pages their sites have. Instead of asking users to fit their content into a page, we decided to offer different patterns of content on each page. A page-by-page setup motivated a sitemap step. The sitemap gives non-experienced users a visual understanding of how their website pages are connected:
The visual sitemap inspired us to visualize other aspects that are confusing in a WordPress site setup, namely the features that a user wants to activate.
Instead of asking users who may not have any WordPress experience to choose plugins, our onboarding form asks users what features they want to add:
Different plugins would be activated behind the scenes, depending on what features a user wanted. Thinking of a site’s features vs. plugins means that network admins should receive fewer requests for plugins that do the same thing as other plugins.
Our onboarding system is now being developed. We’ll soon have a working version installed with all our Braintrust users.