Planning Neos 2.1 / Flow 3.1

The Neos Project Neos Team
2

Thanks for starting this one @robert, it’s very important we work more as a team on prioritized features to improve our workflow. Started a separate thread for that discussion, so we can use this one for collecting and deciding on features for the release. See Optimizing release development workflow for Neos/Flow

Btw. the Github move is only half way done as I see it, maybe even less. Development of 2.1 can of course be done independently for a while, but currently we’re in limbo as I see it. Finalizing this should have a higher priority than working on the next release.

Additionally I see we need to focus more on stuff around the product, which the release of 2.0 allows us to do. We need to grow adoption & contribution. Personally I think that’s more important than product. For this we need to work on our website and communication in addition to easing the contribution workflow and on-boarding of new contributors.

Here’s what I can imagine the next releases could include (not in any particular order or prioritization):

Neos

Every release (step by step)

  • JS/CSS refactoring
  • UI improvements

2.1

  • Finalize history module
  • Finalize content security
  • Workspace workflow
  • Asset replacement
  • Allow uriSegment to be empty for default presets
  • Help texts

2.2+

  • Native sorting/filtering (CR)
  • CKEditor
  • Developer tools
  • TypoScript browser/debugger
  • Node type creator
  • Command module
  • Logging module
  • Internal search (documents, content, media + extendable)
  • Navigate component (multiple trees, custom sorting/filtering)
  • Content translation improvements
  • Split view
  • Review workflow
  • Soft deletion
  • Insert node wizard
  • Concurrent editor support
  • Advanced linking
  • Tablet optimization
  • Integration of external services
  • Google Drive
  • Dropbox
  • Flickr
  • YouTube
  • Vimeo
  • One Drive
  • Responsive preview
  • Redirects
  • Red carpet
  • Cross site linking
  • Access control UI

3.0+

  • Flexible user interface
  • Structured editing (+ inline validation)
  • Undo / redo (CQRS)
  • Content publishing API
  • Import/export API

Flow

3.1

  • REST support
  • Web service API
1 Like