-
Notifications
You must be signed in to change notification settings - Fork 36
Open
Description
Overview
The README mentions the discontinuation of Renku Legacy and provides a transition guide, but it could greatly benefit from more detailed documentation on how to migrate from Renku Legacy to Renku 2.0.
Suggested Improvements
- Step-by-step instructions: Include a clear, step-by-step guide in the README or linked documentation that outlines the migration process for users. This should cover common scenarios, potential pitfalls, and how to handle existing data and configurations.
- Frequently Asked Questions (FAQ): An FAQ section addressing common concerns about the transition could alleviate potential confusion users may have concerning compatibility, changes in features, or how to leverage new functionalities in Renku 2.0.
- Example Projects: Providing example projects that illustrate the migration process and highlight the new features of Renku 2.0 would be incredibly helpful for users to visualize how to use the new system effectively.
Benefits
These changes will enhance user experience and ensure a smoother transition for those currently using Renku Legacy, supporting community engagement and minimizing frustration during the upgrade process.
Metadata
Metadata
Assignees
Labels
No labels