sidemenu, docs, code of conduct and security features implemented

Author: Drago-03

CODE_OF_CONDUCT.md

@@ -0,0 +1,61 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes
+* Focusing on what is best for the overall community
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team. All complaints will be reviewed and investigated promptly and fairly.
+
+## Enforcement Guidelines
+
+Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+**Impact**: Use of inappropriate language or other behavior deemed unprofessional.
+**Consequence**: A private, written warning, providing clarity around the nature of the violation.
+
+### 2. Warning
+**Impact**: A violation through a single incident or series of actions.
+**Consequence**: A warning with consequences for continued behavior.
+
+### 3. Temporary Ban
+**Impact**: A serious violation of community standards.
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community.
+
+### 4. Permanent Ban
+**Impact**: Demonstrating a pattern of violation of community standards.
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). 

SECURITY.md

@@ -0,0 +1,92 @@
+# Security Policy
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are currently being supported with security updates.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.0.x   | :white_check_mark: |
+| < 1.0   | :x:                |
+
+## Reporting a Vulnerability
+
+We take the security of our project seriously. If you discover a security vulnerability, please follow these steps:
+
+1. **DO NOT** open a public issue on GitHub
+2. Send a detailed report to our security team at [security@yourdomain.com]
+3. Include the following in your report:
+   - Type of vulnerability
+   - Full path of source file(s) related to the vulnerability
+   - Location of the affected source code (tag/branch/commit or direct URL)
+   - Step-by-step instructions to reproduce the issue
+   - Proof-of-concept or exploit code (if possible)
+   - Impact of the vulnerability
+
+## What to Expect
+
+When you report a vulnerability, you can expect:
+
+1. **Confirmation**: We will acknowledge receipt of your report within 48 hours
+2. **Updates**: We will provide regular updates about our progress
+3. **Resolution**: Once the vulnerability is confirmed, we will work on a fix
+4. **Disclosure**: We will coordinate the public disclosure of the vulnerability
+
+## Security Best Practices
+
+### For Contributors
+
+1. **Code Review**
+   - All code changes must go through peer review
+   - Security-sensitive changes require additional review
+   - Use static analysis tools to identify potential vulnerabilities
+
+2. **Dependencies**
+   - Keep all dependencies up to date
+   - Regularly check for known vulnerabilities in dependencies
+   - Use dependency scanning tools in CI/CD pipeline
+
+3. **Authentication & Authorization**
+   - Use secure session management
+   - Implement proper access controls
+   - Follow the principle of least privilege
+
+4. **Data Protection**
+   - Encrypt sensitive data in transit and at rest
+   - Use secure hashing algorithms for passwords
+   - Implement proper input validation and sanitization
+
+### For Users
+
+1. **Account Security**
+   - Use strong, unique passwords
+   - Enable two-factor authentication when available
+   - Keep your access tokens secure
+
+2. **API Usage**
+   - Never share your API keys
+   - Use environment variables for sensitive data
+   - Rotate keys regularly
+
+## Security Features
+
+Our project implements several security measures:
+
+1. **Authentication**
+   - JWT-based authentication
+   - Rate limiting
+   - Session management
+
+2. **Data Protection**
+   - HTTPS encryption
+   - Secure password hashing
+   - Input validation
+
+3. **Infrastructure**
+   - Regular security updates
+   - Automated vulnerability scanning
+   - Secure configuration management
+
+## Acknowledgments
+
+We would like to thank all security researchers and contributors who help keep our project secure. Your efforts are greatly appreciated. 

client/src/App.css

@@ -5,33 +5,6 @@
   flex-direction: column;
 }
 
-.floating-logo {
-  position: fixed;
-  top: 20px;
-  left: 50%;
-  transform: translateX(-50%);
-  z-index: 1000;
-  animation: float 3s ease-in-out infinite;
-}
-
-.floating-logo img {
-  width: 150px;
-  height: auto;
-  filter: drop-shadow(0 0 10px rgba(0, 0, 0, 0.3));
-}
-
-@keyframes float {
-  0% {
-    transform: translateX(-50%) translateY(0px);
-  }
-  50% {
-    transform: translateX(-50%) translateY(-10px);
-  }
-  100% {
-    transform: translateX(-50%) translateY(0px);
-  }
-}
-
 .content {
   flex: 1;
 }
@@ -43,17 +16,39 @@
   flex-direction: column;
   align-items: center;
   justify-content: center;
-  color: white;
   padding: 2rem;
   text-align: center;
-  padding-top: 120px;
 }
 
-.App-header h1 {
-  font-size: 4rem;
-  margin: 0;
-  font-family: 'Montserrat', sans-serif;
-  font-weight: 700;
+.header-logo {
+  animation: pulse 3s ease-in-out infinite;
+}
+
+.header-logo img {
+  width: 500px;
+  height: auto;
+  filter: drop-shadow(0 0 25px rgba(74, 144, 226, 0.4));
+  transition: all 0.5s ease;
+}
+
+.header-logo img:hover {
+  transform: scale(1.05);
+  filter: drop-shadow(0 0 40px rgba(74, 144, 226, 0.8));
+}
+
+@keyframes pulse {
+  0% {
+    transform: scale(1);
+    filter: brightness(1);
+  }
+  50% {
+    transform: scale(1.02);
+    filter: brightness(1.1);
+  }
+  100% {
+    transform: scale(1);
+    filter: brightness(1);
+  }
 }
 
 .App-header p {
@@ -104,17 +99,38 @@
   line-height: 1.5;
 }
 
-@media (max-width: 768px) {
-  .floating-logo img {
-    width: 120px;
-  }
+.code-features {
+  margin-top: 1.5rem;
+  padding-top: 1.5rem;
+  border-top: 1px solid #eee;
+}
 
-  .App-header {
-    padding-top: 100px;
-  }
+.code-features ul {
+  list-style: none;
+  padding: 0;
+  margin: 0;
+  display: flex;
+  flex-direction: column;
+  gap: 0.75rem;
+}
 
-  .App-header h1 {
-    font-size: 3rem;
+.code-features li {
+  color: #4a90e2;
+  font-size: 0.95rem;
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  gap: 0.5rem;
+  transition: transform 0.2s ease;
+}
+
+.code-features li:hover {
+  transform: translateX(5px);
+}
+
+@media (max-width: 768px) {
+  .header-logo img {
+    width: 320px;
   }
 
   .App-header p {
@@ -124,4 +140,26 @@
   .domain-grid {
     padding: 2rem 1rem;
   }
+
+  .code-features li {
+    font-size: 0.9rem;
+  }
+}
+
+.menu-toggle {
+  position: fixed;
+  top: 1rem;
+  left: 1rem;
+  background: none;
+  border: none;
+  font-size: 1.5rem;
+  cursor: pointer;
+  color: #fff;
+  padding: 0.5rem;
+  z-index: 999;
+  transition: transform 0.3s ease;
+}
+
+.menu-toggle:hover {
+  transform: scale(1.1);
 }