RFC: Should docs about clones be part of the scope?

E.g. Mega Duck, should we start merging/including technical documentation about it in Pan Docs?

@bbbbbr started consolidating the current knowledge in https://github.com/bbbbbr/megaduck-info

What about the Analogue Pocket?

Read the existing Pan Docs structure and the linked megaduck-info documentation first; compare the Mega Duck and Analogue Pocket material with the project's current scope. Done means reaching an agreed decision about whether clone documentation belongs in Pan Docs and documenting the resulting scope.

Written by the indexing model from the issue text.