Issue 165

templates/boneset.html

@@ -199,6 +199,7 @@ <h2 style="color: #003366; text-align: center; margin-bottom: 25px; border-botto
     <script type="module" src="js/sidebar.js"></script>
     <script type="module" src="js/main.js"></script>
     <script type="module" src="js/imageDisplay.js"></script>
+    <script type="module" src="js/annotationOverlay.js"></script>
 
     <!-- Simple Escape Key Handler -->
     <script>

templates/data/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @jacksayshi

templates/data/.github/ISSUE_TEMPLATE/pull_request_template.md

@@ -0,0 +1,19 @@
+### Description
+
+Fixes #<ISSUE_NUMBER> (A reference to the issue that the PR resolves. For example, if a PR resolves issue #47, the first comment in the PR should be: Fixes #47 (GitHub will then automatically link your PR to the issue it resolves.))
+
+Please include a summary of the changes and the related issue. Include any relevant motivation and context. List any dependencies that are required for this change.
+
+**A pull request must contain the following elements.**
+
+# 1. What was Changed
+A brief summary of the changes made. Please note that you should not be listing files that you changed or code that you wrote here. This is a summary of what the end result of your changes are, rather than the code itself.
+
+# 2. Why it was Changed
+A justification for why those changes were needed. Describe the problem that prompted the change or how the new feature can benefit users.
+
+# 3. How it was Changed 
+A more technical description of the changes that were made. This is additional information that we will be using when reviewing code changes, so it's a great place for you to share some of your thoughts about how you changed the code. Detail the methods or techniques used to implement the changes. You can also mention any challenges you faced or alternatives you considered.
+
+# 4. Screenshots (if applicable)
+Add the before and after screenshots for UI related changes

templates/data/.gitignore

@@ -0,0 +1 @@
+node_modules/

templates/data/BonyPelvis/.vscode/settings.json

@@ -0,0 +1,8 @@
+{
+  "rust-analyzer.workspace.discoverConfig": null,
+  "files.associations": {
+    "*.xml.rels": "xml"
+  },
+  "editor.defaultFormatter": "esbenp.prettier-vscode",
+  "editor.formatOnSave": true
+}

templates/data/CONTRIBUTING.md

@@ -0,0 +1,81 @@
+# Contributing to Digital Bones Box
+
+Thank you for checking out **Digital Bones Box**! We are so happy you are here. If you are intrested in contributing to the project below are some guidelines that help us make most out of your contribution. 
+
+## Getting Started
+
+### How to Contribute
+
+### 1. **Fork the Repository**
+- Navigate to the Digital Bones Box repository on GitHub
+- Click the "Fork" button on the top right of the repository page to create your own copy.
+
+
+### 2. **Clone Your Fork**
+- Clone the repository to your local machine:
+   ```bash
+   git clone https://github.com/oss-slu/DigitalBonesBox
+   cd your-repo
+
+
+### 3. Create a New Branch
+- Create a new branch for your contribution:
+  ```bash
+  git checkout -b feature-branch
+  ```
+
+---
+
+## Contribution Workflow
+
+### 1.Choose an Issue associated with the label **hacktoberfest**
+- Choose the Issue associated with the label hacktoberfest and clearly read all the details and acceptance criteria for the issue before starting to work on the issue.
+
+### 2. Make Your Changes
+- Work on your branch locally. Implement your changes and test them thoroughly to ensure they work correctly.
+- For any UI changes, please include screenshots in the pull request.
+
+### 3. Commit Your Changes
+- Commit messages should be clear and concise. Follow the format:
+  ```
+  git commit -m "Add feature X to improve performance"
+  ```
+- Make sure your commit is properly documented and explains the **why** and **what** of the changes.
+
+### 4. Push Your Changes
+- Push your branch to GitHub:
+  ```bash
+  git push origin feature-branch
+  ```
+
+### 5. Submit a Pull Request (PR)
+- Navigate to your fork on GitHub and click the **Pull Request** button.
+- Ensure your PR:
+  - References the related issue number (e.g., `Fixes #123`).
+  - Provides a clear description of what was changed and why.
+  - Includes relevant tests or screenshots where applicable.
+  - follow the Pull Request template.
+
+---
+
+## Code Guidelines
+
+- Keep your code readable, maintainable, and well-documented.
+
+### 1. Documentation
+- Update documentation as necessary. If your change impacts functionality, be sure to update the corresponding documentation in the **Help** or **README** files.
+
+---
+
+## Issue Reporting
+
+### 1. Suggesting Enhancements
+- If you have ideas for new features, improvements, or optimizations, submit them through a GitHub issue and tag it with **enhancement**.
+
+---
+
+## Community
+
+- If you have any questions or need guidance, feel free to or reach out via email sritammiraja.iragavarapu@slu.edu 
+
+Thank you for your contributions!