Skip to content

πŸš€ Getting Started

Overview

Welcome to the GetCimple team! This section is your entry point as an internal team member to understanding what we're building and why. Whether you're a business partner, developer, devops engineer, or other internal stakeholder, you'll find the guidance you need to get oriented quickly with our cybersecurity governance platform.

Key Documents

πŸ“‹ Quick Start Guide

Choose your path based on your internal team role

  • Business Partner path (strategy, market, customers)
  • Developer/Technical Team path (architecture, coding)
  • DevOps/Infrastructure path (deployment, operations)
  • Product/Feature Management path (roadmap, user needs)
  • UX/Design path (user experience, interface design)
  • Understanding our target customers (end users we're building for)

🧠 Key Concepts and Glossary

Essential terminology and concepts

  • GetCimple platform concepts
  • Cybersecurity and compliance terminology
  • Technical architecture concepts
  • Business process definitions
  • Complete acronym reference

How to efficiently navigate this documentation

  • Documentation structure overview
  • Navigation strategies for different use cases
  • Search tips and advanced features
  • Mobile and accessibility features

🌟 What Are We Building?

We're building GetCimple, a cybersecurity compliance SaaS platform designed specifically for Australian businesses with board directors. Our goal is to create a win-win relationship between:

  • Board Directors: Who need governance oversight and compliance assurance (our primary end users)
  • Management Teams: Who handle implementation and day-to-day operations (our secondary end users)

Our governance-first approach differentiates us by positioning GetCimple as a board-level governance tool rather than a technical security tool, emphasizing director oversight and compliance management.

Key Differentiators

  • Dual-target design serving both governance and implementation needs
  • Australian regulatory focus (Essential Eight, APRA CPS 234, Corporations Act)
  • Multi-board access for directors serving on multiple boards
  • Complete tenant isolation with no cross-company data sharing

🚦 Your Learning Journey as Internal Team

Phase 1: Foundation (Start Here)

  1. Current Section: Getting Started - Team orientation and role-based paths
  2. Strategic Understanding: Core Principles - Our values and approach
  3. Business Context: Project Overview - Market opportunity and what we're building

Phase 2: Deep Dive (Choose Your Focus Area)

Phase 3: Contribution (Apply Your Role)

  • Contribute to business strategy and market understanding
  • Develop technical architecture and implementation
  • Design and build product features and capabilities
  • Create user experiences that serve our end customers

Business Partners

Technical Contributors

Product and Design Teams

Understanding Our End Users

πŸ“š Documentation Standards

This internal documentation follows established standards for:

  • Consistent Structure: Each section has clear purpose and organization
  • Cross-References: Related information is linked for easy discovery
  • Visual Hierarchy: Headings, emojis, and formatting aid scanning
  • Comprehensive Coverage: Business, technical, and design perspectives
  • Quality Standards: Regular review and improvement processes

πŸ’‘ Tips for Success as Internal Team

Getting Oriented

  1. Start with your role-specific path in the Quick Start Guide
  2. Understand our target customers since they drive all our decisions
  3. Reference Core Principles regularly for decision-making alignment
  4. Use search functionality for specific questions

Staying Updated

  • Check "What's New" sections in major areas for recent developments
  • Monitor TaskMaster for project progress and task coordination
  • Review recent updates on section index pages
  • Follow cross-references to understand how sections connec

Contributing to the Projec

  • Report issues through TaskMaster or established feedback channels
  • Suggest improvements based on your expertise and perspective
  • Follow development guidelines established for the projec
  • Coordinate through established team processes

πŸŽ‰ Ready to Contribute?

Choose your next step based on your role:

  • πŸ“‹ New team member: Start with Quick Start Guide
  • 🧠 Need terminology: Check Key Concepts
  • 🧭 Want navigation help: Read Navigation Guide
  • πŸš€ Ready to contribute: Go to your role-specific section and get started

Welcome to the GetCimple team! This documentation is designed to help you understand what we're building, why we're building it, and how you can contribute effectively to creating value for Australian businesses struggling with cybersecurity governance.