TPEN 3 is now in Early Access! Get started today →
Development Timeline
The funding period for TPEN 3.0 was originally 2024-2026. Federal funding was removed on April 2, 2026 and reinstated on October 13, 2026. Development resumes in January 2027 and the full public launch is targeted for August 2028.
- ✅ Phase 1: 2024 (Completed)
- New platform design
- Project creation and management
- Core interfaces and workflows
- ✅ Phase 2: 2025 (Completed - Early Access; Advisory Board prioritization carried into Phase 3)
- Early access release (November 2025)
- Open to all users (March 2026)
- Production cutover (March 2026)
- ⏸️ Funding interruption: April - December 2026
- Federal funding removed (April 2, 2026)
- Reinstatement requested (July 2, 2026)
- Reinstated by the NEH (October 13, 2026)
- Development paused, Early Access remains live
- 🔧 Phase 3: January - October 2027 (Restart and stabilization)
- Development and deployment environments
- Release notes and the public record resumed
- Deferred interfaces and the end-to-end workflow
- 📅 Phase 4: November 2027 - August 2028 (Training, migration, launch)
- Comprehensive training and documentation
- Streamlined TPEN 2.8 migration tools
- Community demonstrations and workshops
- Full public launch: August 2028
The plan above replaces the one in the original proposal. The Phase 3 written for March 2026 never started, so it is not revised here, it is moved. Its content survives intact as Phase 4, and a new Phase 3 goes in front of it to rebuild the environment and the public record that the pause eroded. See the funding interruption for what that cost.
Current Status: Reactivation (November 2026)
TPEN 3 is live in Early Access and stays live through the restart. Core features are functional and we are still gathering feedback. What is happening right now is institutional reactivation, not grant-funded development: the reinstatement was confirmed on October 13, 2026, and funded work resumes in January 2027. Until then the team is reviewing the ecosystem and adjusting current plans based on the feedback received.
Available Now
- ✅ User authentication and account management
- ✅ Project creation from images, IIIF Manifests, and TPEN 2.8 import
- ✅ Classic transcription interface
- ✅ Role-based collaboration and permissions
- ✅ Web Annotation and IIIF standard compliance
- ✅ Export in multiple formats
- ✅ Public API for custom integrations
Coming Soon
- 🔄 Additional transcription interfaces (complex layouts, specialized workflows)
- 🔄 Enhanced manifest editing capabilities
- 🔄 Advanced image manipulation tools
- 🔄 Expanded export format options (TEI, custom schemas)
- 🔄 Repository integrations and cloud storage support
- 🔄 Comprehensive migration tools for TPEN 2.8 projects
These deferred items are scheduled work again. They land in Phase 3, alongside the interfaces and the end-to-end workflow that the pause interrupted.
View detailed feature comparison →
Historical Timeline
This page documents our development journey. For an overview of what changed from TPEN 2.8, see What’s New.
Phase 1: 2024
Establish the foundation for the new platform, including the technology stack, data management, and user interface. Develop a set of core interfaces and workflows for project creation, annotation, and transcription.
1. Evaluate and select a technology stack for data management and user interface.
The team considered several options, focusing on familiarity, scalability, and longevity. There is a strong preference for open-source technologies and a commitment to standards compliance. Where possible, the team will reduce dependencies on libraries and frameworks that would require ongoing maintenance.
TPEN Services
The API backbone of the TPEN platform includes the required configuration and account data, as well as the ability to create, edit, and delete projects. The API will be designed to be as flexible as possible, allowing for the proliferation or integration of third-party tools and services.
Private user account information and project configurations will be stored in a private MongoDB database managed on premises. User authentication is handled by Auth0 and an idToken recovery service allows external applications to authenticate users with TPEN without a backend server.
The TPEN API is available for any developer to use with the idToken granting access to appropriate user actions. The API services run on a Node.js server and are available for use with any client-side application. Code is developed in the open and contributions are welcome at the TPEN GitHub repository.
TPEN Interfaces
The user interface for TPEN 3.0 is intended to be as simple and modular as possible. For all core interfaces, we will use ES6 JavaScript with Web Components instead of a framework like React or Angular. This will allow for more durability and flexibility in the long term. Contributions from the community do not have to be so rigorously controlled and the TPEN 3 experience will differ from TPEN 2 in that it will encourage a diversity of tools built for the specific projects and workflows of the users.
Guiding Principle: The TPEN 3.0 interfaces are designed to be as simple, unstyled, and unopinionated as possible. As most of the content is available without authentication, it should be easy to design an interface for exhibiting project data in a variety of ways, with authentication only required for editing.
The GitHub repository for the TPEN interfaces is used directly for core components and as a template for new projects. In support of developers, there is a well-documented set of Interface Classes that can be used to build new components and interfaces.
2. Enable the creation and management of projects built from IIIF standard resources.
IIIF Manifests
During the first phase of development, we rely on the IIIF Presentation API to initialize projects. Though in some cases the version 2.1 API is still used, the team is committed to the 3.x standard and upgrades all incoming resources where possible. By the end of this phase, it will be trivial to start a new project by simply providing a URL to a IIIF manifest.
Guiding Principle: The TPEN tool is non-destructive and respects the integrity of the original resources. Wherever possible, the project content is pointed to the original resources through annotation and reference.
Collaboration
Any TPEN User can create a project and invite others to collaborate. Whoever creates a project is the Owner and all projects must have exactly one Owner. In addition to the Owner, a project may have any number of Leaders and Contributors. All User Roles are per Project and Custom Roles are allowed.
Our Project Management interactions have been proved out and are available on
GitHub. The Project Class in TPEN-interfaces includes helpful methods for adding and removing members, assigning roles,
and setting custom roles and permissions.
3. Develop a set of core interfaces and workflows for project creation, annotation, and transcription.
Workflows (See Workflow Diagrams)
TPEN 3.0 is built around modularity and flexibility but the core workflows emulate the existing functionality of the TPEN 2.8 platform. In Phase 1, we aim to allow a full end-to-end workflow for a single project, reserving advanced features and integrations for later phases.
End-to-End (Simplest Case)
flowchart LR
A[Login] --> B[Project List]
B --> C[Import New IIIF Manifest]
C --> D[Generate Pages]
D --> E[Create New Project]
E --> F[Open Transcription Interface]
F --> G[Assert Transcription]
G --> I[Save New Annotation to Page]
E --> H[Manage Collaborators]
H --> J[Invite Collaborators]
J --> K[Assign Roles/Permissions]
K --> E & B
I --> F & B;
This is the first target workflow for TPEN 3.0. The user logs in, creates a project, invites collaborators, transcribes a page, and saves the annotation. The user can then return to the project list to start a new project or continue working on the current project.
This simplest case was originally planned for December 2024 but has not been completed. It is required for the planned public Beta and is considered ASAP.
Project creation and management
flowchart LR
A[Login] --> B[Project List]
B --> C[Create New Project]
C --> D[Build Manifest]
D --> E[Add Pages]
E --> F[Save New Project]
B --> G[Manage Project]
G --> H[Edit Pages]
G --> I[Edit Metadata]
G --> J[Manage Collaborators];
This workflow covers the basic project requirements for the Beta release. In addition to a new project from a IIIF Manifest link, this workflow allows for the creation of a new project from scratch. The user can add pages, edit metadata, and manage collaborators. An external or forked Manifest Builder may be called for, but in general, the user should be able to create a project from a set of images that they provide. This hole is very deep and we may ultimately offer lots of options like create from TEI/XML or upload private images to a GitHub repository, but these are for consideration after the Beta.
Any Project should be able to be managed by the Owner and any Leaders. The relationship between the Manifest and the Project will be carefully managed to honor the original document, even when we build it ourselves. The Pages become important to track well, as they are the primary unit of work in TPEN.
Transcription and Annotation
flowchart LR
A[Login] --> B[Project List]
B --> C[Open Transcription Interface]
C --> D[Transcribe Page]
D --> E[Basic Tools]
D --> F[Image Parsing];
The Transcription Interface is the primary tool for the user to interact with the project. The user can transcribe the text on the page, add annotations, and save the work. For the Beta, we are focusing on the basic tools and features required to transcribe a page:
- Text Entry: The user can type text into a text box and it is saved to the Page. At this point, we do not need to support multiple Layers, but a Page will definitely have multiple lines.
- Image Parsing: The user can see the image of the page and draw boxes around the text to be transcribed. This will be a place to attach many options in the future, such as computer vision and external tools, but for the Beta, we are focusing on the user’s ability to draw boxes as in 2.8.
- Basic Tools: Split screen tools are part of TPEN’s history, so it is likely there will be some similar interfaces in the future. For the Beta, a single tool offering a preview of the transcription and the ability to navigate the page by clicking on a text line is sufficient.
These changes should all be saved in the Page and Layer objects, which are
Annotation Collections and Annotation Pages annotated onto the Canvas
and Manifest objects. All these also belong in RERUM, which is our first
big push to make TPEN 3.0 more interoperable. In the future, these interactions
may be more complicated, with a caching layer or sockets to keep from hammering
RERUM with minor updates, so anything we are doing now should include at least
a minor abstraction to allow for that.
Phase 2: July 2025
The Beta release is the first opportunity for the public to interact with the new platform. The Advisory Board members and Research Assistants will be the first to test the platform, followed by a wider group of test users. The Beta includes periods of feedback and focused features to improve the platform, which will be used to prioritize work for the final release.
1. Public Beta enabling Advisory Board members, Research Assistants, and test users to create and interact with simple Projects.
The release of the Beta is a major milestone for the project. Launching it requires a stable platform with a set of core features that are ready for testing. We should also have drafted our license and terms of service before inviting members of the public to use the platform. A direct feedback tool should be evaluated and included before the Beta release.
Expectations for the users and their data should be set before the Beta. As a guide, we should acknowledge that we will attempt to preserve the data but that changes to structure may render it unusable or the formal launch may require us to reset the database. We should also be clear about the licensing specifically in the case of the Beta, as we will regularly dig into users’ contributions and activity to improve the platform. This may be something a User could opt out of in a final product.
2. User feedback and improvements to the platform.
There are scheduled meetings for feedback from the Advisory Board which will select a subset of features to focus on for the final release. Some features, per the funding proposal, are required for the final release and others are simply proposed as possible and will be scheduled for work after delivery. It is up to the Advisory Board to decide which features are most impactful.
Those scheduled meetings did not happen: the board has been inactive, and the feature prioritization it was meant to perform is carried into Phase 3.
Users will also provide feedback and there should be a combination of simple ways to do this. Some GitHub issue templates will help, but there should also be a persistent feedback tool on each interface. Contact via email or forms must be easy to access and regularly reviewed.
3. Test cases and focused features based on feedback and recommendations.
There are three main ways to prioritize work for the final release:
-
Required Features: These are features that are required for the final release. They are the most important and will be prioritized first. As a rule of thumb, any feature not carried forward from TPEN 2.8 must be intentionally left behind. The features named in the proposal may be listed here later as well.
-
Advisory Board Features: These are features that the Advisory Board has selected as important for the final release. They are the next most important and will be prioritized second. The board is not active today, so this category has no entries until it is reconstituted in Phase 3.
-
User Features: These are features that users have requested or that fulfill the special cases of the test users. Some may be simply selected by the developers, but no feature should be added without a clear use case.
Funding interruption: April to December 2026
Federal funding for TPEN 3.0 was removed on April 2, 2026, before the phase originally written for March 2026 got under way. Nothing in that phase started. Development work stopped, and Early Access kept running on institutional support.
Reinstatement was requested on July 2, 2026 and confirmed by the NEH on October 13, 2026.
What the pause cost, stated plainly:
- Six and a half months between removal and reinstatement. Nine months of a thirty-six month funded period with no federal development.
- One phase of work that now has to be done in full.
- A platform untouched for the better part of a year, so the restart is not a resume.
- A public record that stopped. Monthly release notes end at April 2026, and the last change to this site before the reinstatement was 2026-05-04.
The environment is the sharpest problem. app.t-pen.org, api.t-pen.org, and
three.t-pen.org are live and healthy, but the development and staging tier
around them is not finished. Rebuilding without one means changes get tested
against production data in front of users, so it comes first.
Forward Timeline
The phases below are the plan of record as of November 2026. Phase 4 carries the objectives originally written for March 2026.
Phase 3: January - October 2027
The first funded phase after reinstatement. Its job is to make the project workable again before the real feature work resumes.
1. Restore the development and deployment environment.
Provision dev.app.t-pen.org and bring dev.api.t-pen.org back up, with a
separate database and its own RERUM target, so a change can be proven somewhere
other than production. Then prove the deployment path end to end: a pull
request goes green, merges, and DEV serves that commit with traceable identity.
2. Resume the public record.
Monthly release notes restart, and the April to December 2026 gap gets either a
reconstruction or one entry that explains it. The user documentation is audited
against what actually shipped in 2026, since getting-started.md,
tutorials.md, and faq.md all predate Early Access.
3. Finish the work the earlier phases deferred.
This is the end-to-end simplest case that Phase 1 recorded as incomplete, plus the interfaces still listed as Coming Soon. It is not new scope. It was already on the books before the money was pulled.
4. Reconstitute the Advisory Board.
The prioritization mechanism described under Phase 2 depends on the Advisory Board, and there is no active board today. It comes back in this phase, or feature selection for the final release has no mechanism at all.
Phase 4: November 2027 - August 2028
The original Phase 3, moved. Its content is unchanged, because none of it happened. This final phase focuses on training and documentation, migration from TPEN 2.8, community demonstrations, and feedback. The launch of TPEN 3.0 is targeted for August 2028.
1. Training and documentation for users and developers.
The training and documentation for TPEN 3.0 will be available on the website and integrated into the core interfaces. The documentation will be written with the user in mind, providing clear instructions and examples for common tasks.
Developer guidance will include blog posts and code documentation, as well as a set of examples for building custom interfaces and workflows. The core interfaces themselves should be well-documented and serve as a template for new projects.
It is possible a workshop may be held to introduce the new platform to the community. This would be a good opportunity to gather feedback and provide hands-on training for users and developers.
2. Migration from TPEN 2.8 to TPEN 3.0.
The data models of TPEN 2.8 and TPEN 3.0 are not compatible, so a migration tool will be developed to move projects and annotations from the old platform to the new one. The migration tool will be available to all users and will be supported by the TPEN team. Users should only opt into the migration, and it may be kept to a project-at-a-time basis to prevent moving forward stale or empty projects.
Eventually, creating new projects on TPEN 2.8 will be disabled and all users will be required to migrate to TPEN 3.0. A new TPEN user may have a TPEN 2.8 account, but the projects are not linked directly. When TPEN 2.8 is eventually end-of-life, the projects may all be exported to a static manifest to carry forward.
3. Community Demonstrations and Feedback.
The TPEN team will host a series of community demonstrations to showcase the new platform and gather feedback from users. These demonstrations will be at public conferences like the IIIF annual meeting and the SMRS conference. Additionally, the team will consider webinars or in-person workshops to introduce the platform to a wider audience, though this will largely happen after the launch and outside of the funding period.
4. Launch of TPEN 3.0 (August 2028).
The launch of TPEN 3.0 is targeted for August 2028. The platform will be available to the public and delivered as a stable, feature-complete product. All relevant materials will be submitted as deliverables to the funders and the platform will be maintained by the TPEN team for the foreseeable future.
After launch, the project will be configured as an open-source project, solliticing contributions from the community. The TPEN team will continue to develop the platform and provide support for users and developers. The data will be maintained and backed up regularly, with a plan for long-term preservation and sustainability.