Adding my name to the README file

README.md

@@ -0,0 +1,24 @@
+\### Fauna of the Forest and Mountains
+
+\*A brief overview by Carlos Valencia\*
+
+
+
+\### Secret Squirrel Member
+
+"I feel like a nut - John Nelson"
+
+
+
+\### Added My MO
+
+An overview by Mohamed Sudi
+
+
+
+\### Contributed
+
+
+
+Josh'ua Monsalvatge
+

TeamCharter.md

@@ -0,0 +1,121 @@
+# Team Charter: Outdoor Travel Project
+
+## Project Overview
+The project involves designing and developing a hiking and outdoor adventure website that provides detailed travel information, community oriented features, and multi-media compatibility for uploads. The website will include weather and ferry data, localized tips and information, user accounts, blogs/comments, and administrative tools for content management. The target audience includes the client’s friends, family, and outdoor enthusiasts, with an eventual goal of reaching broader audiences visiting the Pacific Northwest.
+
+**Deadline:** December 15  
+**Team Size:** 4 Members  
+**Client:** Independent Project (funded by client)  
+**Budget:** $3,000 initial, up to $200 monthly maintenance  
+
+---
+
+## User Stories
+- As an outdoor enthusiast planning a trip, I want to view *detailed information* about hiking and travel destinations - including how to get there, difficulty levels, real-time weather, and ferry schedules, so that I can plan my experience easily from one place. 
+- As an international visitor, I want to be able to *translate* the site into my *preferred language* so that I can understand travel information clearly and feel included as part of the community. 
+- As a friend or member of the site, I want to *securely log in* to access exclusive content so that I can receive insider tips and special information. 
+- As a user who has visited a location, I want to *leave comments* and share my own experiences so that I can engage with others and contribute to a growing outdoor community. 
+- As an administrator, I want to easily *upload photos* and add new adventures without needing technical support so that the site stays current and reflects my journeys. 
+- As an outdoor guide, I want the ability to *list my offerings* so that I can connect with interested users and *potentially generate income* through the platform.
+
+---
+
+## Project Goals
+1. Launch a functional website that provides:
+   - Destination information, weather, and ferry details.  
+   - User login and membership system with role-based access.  
+   - Blog/comment section for shared user experiences.  
+   - Administrative panel for easy photo and adventure uploads.  
+2. Ensure scalability for:
+   - Future monetization features (membership tiers, guide listings).  
+   - Multilingual translation support.  
+   - Integration with external data sources (weather, ferry, maps).  
+3. Deliver a clean, user-friendly design optimized for both desktop and mobile.  
+4. Deploy to a reliable cloud host (AWS [EC2/S3], Azure, or equivalent).  
+
+---
+
+## Team Roles and Responsibilities
+
+### Developer: Josh’ua Monsalvatge
+**Responsibilities:**  
+- Coordinate scope, milestones, and weekly Monday agendas.  
+- Maintain client communications and change control.  
+- Own roadmap, risk tracking, and release management.  
+
+### Developer: Carlos Valencia
+**Responsibilities:**  
+- Backend services, authentication, role-based access.  
+- External integrations (weather API, ferry data, maps).  
+- Infrastructure-as-code and cloud deployment pipeline.  
+
+### Developer: Mohamed Sudi
+**Responsibilities:**  
+- Frontend architecture and UI implementation.  
+- Responsive layout, accessibility, and localization (i18n).  
+- Performance optimization and design system components.  
+
+### Developer: John Nelson
+**Responsibilities:**  
+- Test strategy, automation, and regression suites.  
+- Documentation, runbooks, and admin content workflows.  
+- UAT coordination and defect triage/resolution tracking.  
+
+---
+
+## Communication Protocols
+- **Primary Communication:** Email (for client updates).  
+- **Team Collaboration:** Discord or Slack (for internal communication).  
+- **Progress Tracking:** Trello, Miro, or Notion boards (task assignments, milestones).  
+- **Meeting Cadence:**  
+  - **Weekly team meeting every Monday** (status review, sprint planning, blockers).  
+  - **Weekly client update** via summary email following Monday meeting.  
+  - Urgent communication through agreed chat platform.
+
+---
+
+## Project Timeline (Aligned with Monday Meetings)
+
+| Week | Date | Focus | Deliverables / Milestones |
+|------|------|--------|----------------------------|
+| **Week 1** | Oct 28 | Project Kickoff | Review client transcript, confirm goals, assign team roles, create task board. |
+| **Week 2** | Nov 4 | Discovery & Planning | Complete user stories, draft requirements doc, initial wireframes, finalize tech stack. |
+| **Week 3** | Nov 11 | Design & Architecture | Approve final wireframes, create UI mockups, outline database schema and architecture plan. |
+| **Week 4** | Nov 18 | Development Phase 1 | Build homepage, hiking info section, and integrate weather and ferry APIs. |
+| **Week 5** | Nov 25 | Development Phase 2 | Implement login/membership system, blog/comments, and admin features. |
+| **Week 6** | Dec 2 | Testing & Refinement | Conduct functionality tests, fix bugs, finalize design polish and responsiveness. |
+| **Week 7** | Dec 9 | Launch Preparation | Perform client review, finalize deployment setup, deliver documentation. |
+| **Week 8** | **Dec 15 (Sunday Deadline)** | Final Delivery | Website fully live by end of day Dec 15; post-launch verification and client approval. |
+
+---
+
+## Quality and Testing Criteria
+- User login and access control verified through role-based authentication.  
+- Real-time data from weather/ferry APIs displayed correctly.  
+- Site translation functions for multiple languages without data loss.  
+- All pages pass responsiveness and performance benchmarks.  
+- Content uploads validated for both client and admin roles.  
+
+---
+
+## Risk Management
+- **Scope Creep:** Controlled through client-approved change requests.  
+- **Time Delays:** Managed via Monday reviews and sprint accountability.  
+- **Technical Issues:** Mitigated through version control (GitHub branches) and weekly testing.  
+- **Budget Constraints:** Prioritize essential features; postpone non-critical enhancements.  
+
+---
+
+## Core Values
+1. **Respect and Inclusion** — Every team member’s input is valued; we listen before responding and ensure equal participation.  
+2. **Accountability** — We take ownership of our assigned tasks and communicate proactively when challenges arise.  
+3. **Transparency** — We maintain open, honest communication and share progress, setbacks, and updates regularly.  
+4. **Collaboration** — We build solutions together, recognizing that teamwork produces higher quality results than isolated effort.  
+5. **Continuous Improvement** — We seek feedback, reflect on our work, and refine both our process and product continuously.  
+
+---
+## Success Criteria
+- Website live and functional by **December 15**.  
+- Client able to upload, manage, and update site content independently.  
+- Users can access accurate, engaging, and localized travel data.  
+- Future roadmap documented for mobile app and monetization features.