Update Exec Docs

docs/club-execs/presidents/business-president.md

@@ -0,0 +1 @@
+# Co-President: Business

docs/club-execs/presidents/tech-president.md

@@ -0,0 +1 @@
+# Co-President: Technology

docs/event-comms-team.md

@@ -0,0 +1,27 @@
+# Event / Communication Teams
+
+## Brief Description of the role
+
+Event / Communication teams will be the key to communicate with members, planning events, posting on social medias, creating banners, etc. Although it may have more responsibilties than expected, but it will be more specific roles will be given as you go.
+
+### Event Side
+
+- Event Planning:
+  - Plan ideas and execute events to showcase the projects and their impact on the community (Icebreakers, End of Term Socials).
+- Event Logistics:
+  - Event location booking, transport banners, AV equipment, and decorating the events
+- Creative Planning:
+  - Design banners, posters, and other graphics to help Communications Team promote the events
+- Event Media:
+  - Capture and edit photos/videos of events to help the Communications Team build content
+
+### Communication Side
+
+- Marketing and Public Relations:
+  - Develop marketing strategies to increase the visibility of the club and its projects. Manage public relations and communicate the club's achievements and impact to the public.
+- Members Recruitment and Retention:
+  - Produce engaging content such as blogs, videos, and social media posts to tell the club's story. Showcase project milestones and member experiences to attract a wider audience and keep them active in the club.
+- Parntership Development:
+  - Contact and maintain strong relationships with club partners, and non-profits to explore collaborative opportunities
+- Secure Funding:
+  - Secure funding opportunities from sponsors for events, or grants to help projects if needed (can be tech support, etc).

docs/president-team.md

@@ -0,0 +1,45 @@
+# President Team
+
+The SFU Open Source Development Club operates under a Co-President model, with two equal leaders focusing on distinct but complementary domains: Business Co-President and Technology Co-President. This structure ensures balanced leadership, where both community development and technical innovation receive dedicated attention.
+
+## Business Co-President
+
+The Business Co-President serves as the primary representative of the club’s external and internal community affairs. Their focus is on diplomacy, communication, and organizational growth.
+
+### Responsibilities
+
+- Community Engagement & Diplomacy:
+  - Act as the main point of contact between the club and external partners, including SFU staff, faculty, sponsors, and other student organizations.
+  - Maintain strong relationships with alumni, industry contacts, and prospective collaborators.
+- Member Relations:
+  - Ensure all members feel welcomed, included, and informed about club activities.
+  - Lead initiatives that strengthen the club’s culture of openness, inclusivity, and collaboration.
+- Administration & Logistics:
+  - Oversee scheduling of meetings, events, and workshops.
+  - Handle administrative tasks such as membership tracking, communication channels, and resource allocation.
+- Finance & Sponsorship:
+  - Manage the club’s budget, funding applications, and spending records.
+  - Lead sponsorship outreach and maintain sponsor relations.
+
+## Technology Co-President
+
+The Technology Co-President serves as the lead for the club’s technical direction and operational excellence. Their focus is on managing projects, fostering innovation, and supporting the technical development of members.
+
+### Responsibilities
+
+- Project Oversight:
+  - Coordinate all ongoing and upcoming projects within the club.
+  - Ensure projects align with the club’s mission of open source collaboration and student growth.
+  - Monitor project timelines, deliverables, and quality standards.
+- Technical Mentorship:
+  - Support members in skill development by providing guidance on tools, technologies, and best practices.
+  - Promote knowledge sharing through workshops, documentation, and code reviews.
+- Infrastructure & Operations:
+  - Oversee technical infrastructure such as GitHub repositories, project documentation systems, and deployment platforms.
+  - Maintain standards for version control, testing, and collaborative workflows.
+- Innovation & Direction:
+  - Identify opportunities for new open-source initiatives and encourage members to experiment with emerging technologies.
+  - Ensure technical activities support both learning outcomes and real-world impact.
+- Collaboration with Business Co-President:
+  - Work closely with the Business Co-President to balance community needs with technical feasibility.
+  - Provide input for event planning, ensuring technical workshops and hackathons are well-structured and impactful.

docs/strat-team.md

@@ -0,0 +1,21 @@
+# Strategy Teams
+
+The Strategy Team steers the club’s project portfolio end to end: it selects mission-aligned, feasible projects, helps leaders define scope, objectives, and resourcing, connects teams with mentors through regular office hours, and provides non-technical enablement—workshops, documentation, hiring posts, and pitch materials—to maximize impact.
+
+### Responsibilites
+
+- Project Selection:
+  - Evaluate and select projects based on criterias such as their alignment with club objectives, potential impact, feasibility, etc. Ensure a diverse range of projects that cater to different community needs and skill levels.
+- Project Planning:
+  - Define the scope, objectives, and expected outcomes for each project. Assist project leaders in project planning before initiation and secure necessary resources if needed (members hiring, funding, etc)
+- Membership Contact:
+  - Organize and coordinate mentorship opportunities with alumni and industry professionals. Schedule regular office hours for mentors to guide project teams.
+- Project Management Support:
+  - Offer non-technical support such as organizing workshops and training sessions. Assist in creating project management documentation, hiring posts, and pitch presentations for projects, etc
+
+### Good to Have / Need to Have
+
+- Facilitation skills for workshops, office hours, and retrospectives.
+- Strong written communication for docs, pitch decks, and status updates.
+- Stakeholder outreach with alumni, mentors, and partner organizations.
+- Light technical fluency (Git/GitHub basics, issue templates, PR reviews).

docs/tech-team.md

@@ -0,0 +1,22 @@
+# Technology Teams
+
+The technology team in the SFU Open Source Development club has several roles in this club since the club is based on a programming club. As a member of this club, the technology team needs to help out with those responsibilities. If you would like to work in a technology team, you must dedicate some time to working on these responsibilities.
+
+### Responsibilites
+
+- Club Technology Management
+  - Identify new technologies and maintain current digital infrastructure to support the club operations such as club website
+- Club Platform Management
+  - Manage and moderate club communications platform such as building Discord bots, or Notion templates for documentation.
+- Project Technology Management
+  - Identify new technologies and maintain current digital infrastructure to support project teams (Manage Github Repo, AWS for project deployment, etc.)
+- Project Technical Support
+  - Build and maintain open-source tools/libraries, provide documentation/online guides to assist project teams
+
+### Good to Have / Need to Have
+
+- Knowledge of Git / GitHub (Maybe you learned in CMPT 276)
+- Knowledge of deploying site (for instance, GitHub Page, Vercel, etc)
+- Knowledge of how to write technical report / documentation
+- Any prior knowledge of cloud technologies (AWS, Azure, etc) is a plus
+- Eager to learn new technologies and work in team environment

docusaurus.config.ts

@@ -75,7 +75,7 @@ const config: Config = {
           type: "docSidebar",
           sidebarId: "tutorialSidebar",
           position: "left",
-          label: "Tutorial",
+          label: "Tutorials",
         },
         {
           type: "docSidebar",
@@ -87,7 +87,7 @@ const config: Config = {
           type: "docSidebar",
           sidebarId: "execSidebar",
           position: "left",
-          label: "Exec",
+          label: "Executives",
         },
         {
           to: "/blog",

sidebars.ts

@@ -61,7 +61,13 @@ const sidebars: SidebarsConfig = {
     },
   ],
 
-  execSidebar: ["intro-exec"],
+  execSidebar: [
+    "intro-exec",
+    "president-team",
+    "tech-team",
+    "strat-team",
+    "event-comms-team",
+  ],
 };
 
 export default sidebars;