PortalJS Roadmap and Priorities as of Q4 2023 (Oct 2023)

[rufuspollock]

Proposed Focus

Documenting and presenting what's there.

Assumption: the core functionality is there. However, could be much better presented e.g. examples, docs etc etc.

Once we've got better presentation we can come back to adding more features and examples.

Next step

Do a more detailed "shaping" i.e. assessment and planning of what we can do with, say, 4-6 weeks of effort.

Brainstorm: start of shaping

2 main groups:

• Developers building portals
• Editors/Curators entering content and data into the portal - see #883

A third group:

• People deciding what portal stack to use "Why use It"

There's also just documenting some of the core concepts which is common across all groups ...

For Developers

• Quick way to get started - this we have with the "getting started" tutorial at https://portaljs.org/docs/
  • 🚩 shouldn't really be at docs but e.g. portaljs.org/learn or something
  • Could we extended with additional functionality or at least lead-ins to that e.g. for maps, seo, adding content etc
• Howtos and FAQs Developer FAQs for PortalJS #878
  • Maps
  • Charts
  • Theming
  • i18n
  • Integrating data from source X ... (todo: explain what this means more ...)
  • Plugins and extensions
• Examples - what we have now is mostly complete sites. Could have some smaller examples (maybe go to howtos)
  • CKAN
  • Frictionless
  • Data Rich Documents
  • Github based

Editors and Curators

See #883 which has a lot on this.

Why use it

• Key features
• Why use it compared to X (or with X)
• Demos

Core concepts

• Data Rich Documents
• Decoupled frontends (what and why)
• MDX, React, NextJS etc
• Always bet on javascript ... (and how javascript / React is the plugin framework)
• What is a data portal / data catalog ... - see https://datahub.io/docs/dms and https://datahub.io/docs/dms/data-portals