[Doc] End to End Workflow and Architecture
Open
documentation
Open to All
question
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 78
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 6
Description
A markdown report on end to end architecture, workflow and expectation with mermaid diagrams. Dont use LLM for anything else than structure and grammar.
It should also include the rationale behind decisions, for eg. why we decided to go with clients clipboard but couldn't for now, separate client server setting, trackpad region for mirror and all. Also, consider discussions from successful issues and PRs to get the decision points.
In short, this should be enough to explain the entire vision and work to anyone without looking at the codebase.
Contributor guide
Assessment
This issue has not been assessed yet.