Skip to content

[RMP] Centralize Documentation into the Merlin/Merlin repo #788

Description

@bschifferer

Problem:

The feedback of our repository is that it is easy to follow:

  • Every repository has its own documentations. Users have to switch back and forth between documentations
  • There is no single entry point for users where to start and read something end-to-end

Some examples:

Goal:

Provide a better user experience for our documentations

High Level Decision:

We need to decide:

  • How should (new) users discover Merlin?
  • Do we have one centralized documentation vs. documentations per repository?
      • If centralised - what does it mean? Do we move all API docstring documentation into one repository?

ADR: https://docs.google.com/document/d/1FmK55tAo0wy0tHUe3eE8xqZKGDYSvy0tvq8Y036854A/edit#heading=h.dspp0kxpgck1

Some Options:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions