Skip to content
Chris Hartgerink edited this page Mar 9, 2024 · 3 revisions

This document is to track to do's throughout the rebuild. We are currently in the process of collecting and consolidating these from various sources.

Warning

This page is subject to lots of change at the moment.

Features

  • Automated publishing - API endpoints - API tokens - R package
  • Branded + designed emails
  • Built in moderation
  • Circular dendogram icon for modules
  • Collection of collections
  • comment system
  • Data export - Interoperability
  • diffing modules
  • Encompassing DOI registration - eg DOI registration for conferences
  • feature parity with v1
  • Features - Moderation - Group workspaces
  • Folder structures in modules
  • follow modules
  • Freemium model for supporters
  • Improvements - Generate Sitemap by default
  • Invite co-authors without ResearchEquals account
  • Linking between existing DOIs
  • Multiple affiliations --> select relevant ones upon publishing
  • Organization pages
  • Social image generation (stable form) - see Vercel
  • Strong search functionality (systematic review + discovery) --> search to collection?
  • versioning modules
  • text editor
  • Add links to any outputs
  • Native support for versioning of modules

Comms

  • clear comms strategy
  • Coherent design language
  • Excitign + excitement building (momentum)
  • Improved copy
  • next level marketing page - Clear benefit and value proposition
  • Testimonials - eg https://testimonial.to/ or homemade
  • Upgraded marketing story

UX

  • improve reading experience
  • Include major screens on their own route
  • Map the flow for specific, desired actions -> fewer steps and less information helps accomplish mission. Each step can lead to attrition.
  • onboarding improvements
  • Play nicely with reference managers
  • Quick replace files in drafts
  • Sharing button Mastodon
  • Well documented pathways per group

Development guidelines

  • ActivityPub federation
  • Auth - 2FA - Passkeys - SSO
  • Automated build tools
  • code problems are sometimes other problems
  • Componentized
  • Factor out the XML generation - see proposal
  • Fast loadtimes
  • Functional github actions (lighthouse, etc)
  • Granular queries - reactive load times
  • Improve file metadata management in database (instead of dumping Uploadcare JSON and assuming it's Type)
  • Long lasting - 5-10y
  • Minimal content layout shift (CLS)
  • Minimal dependencies
  • Ready for localization (scalable)
  • Remove as much cruft as possible - outsource actions to urls (e.g., invitations, accept reject)
  • Strong HTML standards
  • Unit tested
Clone this wiki locally