Update docs.radicle.xyz to be Upstream-specific
brandonhaslegs opened this issue · comments
We recently removed out-of-date references to Upstream in docs.radicle.xyz.
@joelhans is taking over maintaining docs.radicle.xyz and I believe he's got a plan already: https://commitcopy.notion.site/docs-radicle-xyz-planning-architecture-27de5273d4d34193b4de114d721cabc7.
Is there anything more specific that you wanted to do here @brandonhaslegs? Also why is this issue on this repository and not on the docs repo?
We're also taking some time to re-align Upstream to fit into the current Radicle ecosystem and I think until we have the mvp for this strategy out the door, there won't be any other documentation besides the one in the Upstream repo itself.
I'd love some more context for this as well. The current goal of docs.radicle.xyz (as far as I'm aware) is to give users one possible path for hosting and collaborating on code using Radicle tools/projects. The only functional path right now is the CLI tooling, hence the new focus on documenting how to take common actions using that.
I'd love to bring Upstream back into the fold in the future, so that the docs showcase how collaboration works in the CLI and Upstream, and let them choose the workflow that fits best for them, but I think that's a ways off still.
I could go on longer about the need for some centralized source of truth within Radicle, instead of having a bunch of separate docs sites that don't discuss the ways that the projects interact, but I don't want to distract too much from getting some context around this issue.
I didn't write this, @abbey-titcomb did. This is carried over from her list on #299
Sorry for the lack of context here folks, was just trying to drop some thoughts based on feedback I've gathered regarding our website. Now that @joelhans has gotten started on his docs.radicle.xyz work, maybe it's better to close this issue and let him continue on with his plan! I think he's very aware of the issues we need to fix with docs.radicle.xyz.