Whitepaper
Whitepaper from the Stephen Gilfus library.
This paper is being finalized for release.
Request advance access or be notified when it publishes — every request is reviewed personally before release.
The shape of the argument
A short outline of the headline conclusions a reader will leave with.
- 01
Whitepaper from the Stephen Gilfus library.
- 02
Original frameworks distilled from category-defining build experience.
- 03
Architectural decisions and trade-offs explained in plain language.
Audience fit
Written for readers who carry decision weight on systems that outlast their tenure.
- 01
Founders and operators building category-defining platforms
- 02
Executives evaluating institutional architecture decisions
- 03
Investors and boards underwriting platform-stage companies
In one paragraph
A keyword-led summary so the paper is discoverable and scannable before you open the PDF.
Blackboard Building Blocks (B²) was the published contract that turned a closed LMS into an extensible academic platform. This 2000 companion paper introduces the system services, supported interfaces, and partner-extensible toolset behind B² — and explains why a single vendor can never build everything a research university, a community college, and a corporate academy all need. The honest move was to give that work back to the institutions and partners closest to it. The paper documents the interfaces, the developer model, and the governance that made third-party extensions safe to deploy in enterprise installations — establishing the architectural pattern (platform plus partner ecosystem) that every serious learning platform has copied since.
What readers ask first
- What is the Blackboard Building Blocks (B²) initiative?
- Building Blocks (B²) is Blackboard's extensibility framework: a documented set of system services and supported interfaces that lets institutions and partners add functionality without modifying the core product. It is the contract that made third-party extensions safe to run inside enterprise Blackboard installations.
- How do Building Blocks differ from plug-ins?
- Building Blocks are governed extensions against published system services, with a supported interface and a developer model designed for upgrade safety. Plug-ins are typically unsupported modifications. The B² model exists precisely so partner code survives platform upgrades.
- Why did Blackboard publish the Building Blocks architecture?
- Because no single vendor can serve a research university, a community college, and a corporate academy with the same feature set. Publishing the contract let the institutions and partners closest to each problem extend the platform without forking it.