Open pgraverdy opened 2 years ago
@pgraverdy I have changed the readme to better track progress of the task.
@pgraverdy I have added the sequence diagram to the readme
@pgraverdy Awaiting your response, please let me know what you think
@azlaanmsamad I added some issues, please have a look and reflect on the sequence diagram.
@pgraverdy
I have updated the readme.md with sequence diagram, please check it when you have time and let me know your comments.
In the README, expand each step and add subitems/subsub items (can mark them done or todo). Many are already in the doc. Its fine to postpone some and explain (e.g., in Step 2, move the CI/Github Actions item to a new Step 6 that can be named "CI Setup" and add a subitem note stating that its delayed as not priority, ...)
Then add a design section in the README.md that presents the architecture of the system you re building. This is really fundamental as it conveys what you understand of the task and what you are aiming at.
You can either do one or more sequence diagram (can be written in markdown/mermaid - check Github MD extensions there). You can use this to identify the different components in the app, and how they communicate.
Alternatively (or in addition), you can make an architecture diagram of the app (wich identifies the "components" that send data, requests, ... and use arrows beteen these components to represent the relationships between the components, the flow of actions/information.
@azlaanmsamad do not hesitate tp ask questions below in the issue if this is not clear.