| Table of Contents | ||
|---|---|---|
|
...
Architecture Roadmap Progress
Frontend Development |
.png?version=2&modificationDate=1553045180777&cacheVersion=1&api=v2&width=600)
| Processes |
.png?version=1&modificationDate=1547559903780&cacheVersion=1&api=v2&width=600)
|
Architecture Roadmap Timeline
...
| Task | Description | Requesting | Dependencies | Wild Guess | Start | (Target) Actual |
|---|---|---|---|---|---|---|
| Deployment Pipeline, Phase 1 | GoCD pipeline that publishes static frontend files to a named S3 bucket | Enterprise, Discovery, Publisher, Journals | DevOps | 4 weeks | July 2 | (Aug 3) Aug 3 |
| Authn: Monitoring & Logging | New Relic dashboard to monitor authentication-related errors and performance metrics. | 1 week | July 9 | (July 27) Aug 20 | ||
| Authn: JWT: Asymmetric Keys | Enabling Auth service and REST endpoints to use asymmetrically signed JWT tokens | DevOps | 1 week | July 23 | (July 30) Aug 1 | |
| Authz: OAuth Scopes in platform | Enable in production | Microsoft | 2 days | July 31 | (Aug 1) Aug 8 | |
| Authn: SSO across micro-frontends (a.k.a., JWT Session Cookies) | Allow users to seamlessly navigate from one microfrontend to another without re-authenticating if desired by the microfrontend. IDAs: edx-platform, ecommerce (for Enterprise) | Enterprise, Publisher, | 1 week (POC), | (Aug 1) Aug 8 | (Oct 6-GS) Nov 16 | |
Shared Header & Footer (with Micro-frontend configurations) | Reusable header and footer components that can be shared across our IDAs to provide a consistent experience as users navigate from one micro-frontend to another. We will target the following micro-frontends initially: Grades, LMS, Studio. | Enterprise, Discovery, Publisher, Journals, | UX, Product | 4 weeks | (Oct 22) Dec 3 | (Dec 21) |
Replatform
| Task | Description | Requesting | Dependencies | Wild Guess | Start | (Target) Actual |
|---|---|---|---|---|---|---|
| Pick a LMS feature to rewrite | Get input from other themes/teams and make decision on which feature | UX, Theme teams | 1 week | 7/27 | 8/3 | |
| API Best Practices | Develop (via OEPs) and implement (via fitness functions) best practices, as learned from writing the APIs. | Ongoing | (May 29-DO) | |||
| Design system | FedX and UX: implement commonly required components with a style guide. | UX | Ongoing |
...