Add Home

Home.md

@@ -0,0 +1,23 @@
+## Dealing with "issues" on Git
+
+An "issue" typically refers to a feature, bug, or other point of discussion or task that requires attention. Issues serve multiple purposes:
+
+- **Tracking**: They help maintain a record of tasks, enhancements, and bugs for a specific project.
+- **Discussion**: They offer a platform for collaborators to discuss the task or bug in question, decide on solutions or approaches, and provide feedback.
+- **Organization**: Through the use of labels, milestones, and assignees, issues aid in categorizing and distributing work within a project.
+
+When someone discovers a bug, has a question, or wishes to propose a new feature, they can open an issue in the repository. Other collaborators or the repository owner can then comment on the issue, offering feedback, solutions, or answers. Once the topic of the issue is resolved, it can be closed.
+
+In our collaborative workflow, we use Issues to coordinate and track the development of specific course content. Here are some guidelines to consider:
+
+- Keep issues concise and to the point.
+- Title the issue descriptively, e.g., "General Check Up - BMI calculation".
+- Avoid bundling multiple problems into a single issue. Aim for succinct discussions of a problem and close the issue promptly once resolved.
+- To assign tasks, request feedback, or seek clarification on content-related topics, mention a specific team member by using the "@" symbol followed by their username, like `@username`.
+
+Go to issues here: [https://git.vdm.dev/joomla/eHealth-Portal/issues](https://git.vdm.dev/joomla/eHealth-Portal/issues)
+
+## Navigation on the eHealth system
+
+Once you've logged in you will see this screen:
+![](/attachments/091a8020-51be-4f41-bd47-7d969cb97fcb)