Epic: Roadmap To v3.0

[sghoweri]

Sketching out the work I think is remaining till we can release the next beta version of PL Node + big ticket items left for the full v3.0 release.

Please let me know if I'm missing anything or got anything wrong here!

Goals

1. Stability

   • ie. the Pattern Lab Node v2.0 to v3.0 refactor work

2. Interoperability

   • Move to monorepo (DONE!)
     • Publish monorepo pieces independently (ie release updates as they are ready to go?)
   • Unify the Pattern Lab Ecosystems (ie. native PHP-based Twig support)

3. Flexibility / Customization

   • UIKit refactor
   • Customizations (light / dark mode, logo support, support for 3rd party UI add-ons, etc)

4. Maintainability

   • Automate release process
   • Docs & Demos
   • Automate Now.sh deployment of docs / demos
   • Pattern Lab as a platform vs PL as a monolith

5. Platform Prep

   • Consumable, extendable, and interoperable design systems / pattern libraries

---

Work Remaining For Next Beta

• Merge in any open PRs that are good to go? Merge in current UIKit PRs?
• Confirm publishing / release process?
• Publish next release to NPM

Work Remaining For v3.0 Release

• Markdown / Viewall path bugs
  • Viewall Patten breaks if a folder includes a markdown file #970
• Docs
• Finish Twig Renderer integration
• Clean up, PR remaining UIKit refactor / rebuild updates
  • CSS Vars for theming

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[sghoweri]

Bump! Still open + still in progress. 🙂

[aleksip]

I would consider a working plugin system a must-have. Seems to me the plugin system is broken at the moment? The plugin system might also need some rearchitecting. Currently PL seems to assume that every package beginning with plugin- is a PL plugin. This means that it finds and tries to install Babel plugins, for example.

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[sghoweri]

Bump

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[sghoweri]

fist bump

[bmuenzenmeyer]

btw - 3.0 was accidentally released a while ago, see #1039 so not sure how much of this still applies

[ringods]

Can we close this issue in favor of more recent issues and the core 2 project board?

[bmuenzenmeyer]

i'm in favor. @sghoweri if you agree please close.

[sghoweri]

Closing out -- I'll open standalone tickets if there's anything worth keeping around (and still relevant) from this