Feedback on week 7 team project progress for CS2103T-W11-1

[nus-se-bot]

Team progress for v1.1

• Product website available at the expected URL(:heavy_check_mark: well done!)
• PR created from team repo to our repo(:heavy_check_mark: well done!)
• README page:
  • Some parts not related to your product are removed(:heavy_check_mark: well done!)
  • se-education.org acknowledged(:heavy_check_mark: well done!)
  • Ui.png has been updated(:heavy_check_mark: well done!)
• Product website title changed to match your product(:heavy_check_mark: well done!)
• User Guide: some content has been updated(:heavy_check_mark: well done!)
• Developer Guide: some content has been updated(:heavy_check_mark: well done!)
• Team repo git tagged as v1.1(:heavy_check_mark: well done!)

Individual progress of @LuWenQ for v1.1

• Team repo forked to your GitHub account https://github.com/luwenq/main (:exclamation: try to do by next milestone)
• Used forking workflow:
  • Created PRs Tutorial adding remark #45 Refactors #24 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs Extra classes for model #25 (:heavy_check_mark: well done!)
• Merged updates to documents(:exclamation: try to do by next milestone)
• luwenq.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @le0tan for v1.1

• Team repo forked to your GitHub account https://github.com/le0tan/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs Add more explanation to DEFAULT constants #35 Extra classes for model #25 Tutorial adding command #21 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs Update Badges and Documentation #44 Update Documentation and Site Attributes #42 Update User Guide and Developer Guide #38 Refactor UI #37 Command and Parser #34 Update Project website and User Guide #30 Refactors #24 (:heavy_check_mark: well done!)
• Merged updates to documents(:exclamation: try to do by next milestone)
• le0tan.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @jiayushe for v1.1

• Team repo forked to your GitHub account https://github.com/jiayushe/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs Update Badges and Documentation #44 Update Documentation and Site Attributes #42 Update User Guide and Developer Guide #38 [Tutorial] Add remark command #36 Update from upstream repository #22 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs Refactors #24 (:heavy_check_mark: well done!)
• Merged updates to documents(:heavy_check_mark: well done!)
• jiayushe.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @tiuweehan for v1.1

• Team repo forked to your GitHub account https://github.com/tiuweehan/main (:heavy_check_mark: well done!)
• Used forking workflow:
  • Created PRs Refactor UI #37 Add Remark Command #40 Update Project website and User Guide #30 Remove codacy bage from README #1 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs Command and Parser #34 Add more explanation to DEFAULT constants #35 Refactors #24 (:heavy_check_mark: well done!)
• Merged updates to documents(:heavy_check_mark: well done!)
• tiuweehan.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Individual progress of @Seris370 for v1.1

• Team repo forked to your GitHub account https://github.com/seris370/main (:exclamation: try to do by next milestone)
• Used forking workflow:
  • Created PRs Week 6 Tutorial-Adding Command #43 Command and Parser #34 (:heavy_check_mark: well done!)
  • Gave review comments to other PRs (:exclamation: try to do by next milestone)
• Merged updates to documents(:exclamation: try to do by next milestone)
• seris370.png uploaded and linked from AboutUs page, merged(:heavy_check_mark: well done!)

Tutor: @damithc

_{Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-02 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

[le0tan]

We updated the documents via Google Docs to ensure the consistency of the first draft of our user guide and developer guide. Since it's not written explicitly as a project requirement that the division of documentation work should reflect in separate git commits, can these Google Docs version history be the evidence of reaching the update to documents milestone? We will create git commit records to reflect the division once we think our UG and DG is stabilized. @damithc

https://docs.google.com/document/d/10pKeQjJ9HScXFr3LL2ckObKa1QPQnq0cx381AwSiJGY/edit?usp=sharing
https://docs.google.com/document/d/1-1kegS3qSPCR2cBJlsg2nLp97NCFhSGbHPhUS5reIiA/edit?usp=sharing

Affected milestones: @le0tan @Seris370 @LuWenQ