Add student organization profile page

CONTRIBUTING.md

@@ -208,6 +208,35 @@ Please follow these coding style guidelines:
 - Write clear, concise comments where necessary.
 - Use meaningful variable and function names.
 
+### Contributing Guidelines
+- Create a feature branch from main (e.g., feat/add-postgres-stack).
+- Use Conventional Commits (feat:, fix:, chore:) to keep history clean and readable.
+- Include tests where applicable.
+- Run linting and tests before submitting a pull request.
+- Ensure your changes follow the existing project structure and registry-based stack system.
+
+---
+
+## Issue Labels
+
+When opening issues or reviewing pull requests, please apply the most relevant label(s) to help maintainers triage and prioritize them. Here’s a basic guide:
+
+| Label | When to Use |
+|-------|-------------|
+| `bug` | A reproducible error, crash, or incorrect behavior in Taco. |
+| `feature` | A new capability or enhancement that does not exist yet. |
+| `enhancement` | Improvements to existing features, performance, or developer experience. |
+| `docs` | Documentation updates, typos, or README/CONTRIBUTING changes. |
+| `refactor` | Code cleanup or restructuring without changing behavior. |
+| `ci` | Issues related to GitHub Actions, testing, or build pipelines. |
+| `good first issue` | Small, well-scoped issues suitable for new contributors. |
+
+**Tips:**
+- Most issues should have **one primary label**.
+- If an issue touches multiple areas (e.g., a feature that also needs docs), feel free to add more than one.
+- PRs should ideally match the label of the issue they close.
+
+---
 ### Commit Messages
 
 Please write a rough description for the changes made in each commits

ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,2 @@
+# .github/ISSUE_TEMPLATE/config.yml
+blank_issues_enabled: false

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+## Summary
+
+Describe the purpose of this pull request. What does it do, and why is it needed?
+
+Closes #(issue number) if applicable.
+
+---
+
+## Changes Made
+- [ ] Added a new feature
+- [ ] Updated existing functionality
+- [ ] Improved documentation
+- [ ] Refactored internal code
+- [ ] Fixed a bug
+
+Briefly summarize the major changes:
+
+-  
+-  
+-
+
+---
+
+## Testing
+
+How was this change tested?
+
+- [ ] Manual end-to-end testing
+- [ ] Unit Tests
+- [ ] CI checks passed