Combating brain rot through comprehensive software engineering education.
Visit the live site: https://grokkingsoftwareengineering.github.io
GrokkingSoftwareEngineering provides deep, long-form technical content to combat the brain rot epidemic caused by short-form content and superficial tutorials. We believe in building genuine expertise through comprehensive education.
- Documentation Platform: JetBrains Writerside
- Hosting: GitHub Pages
- CI/CD: GitHub Actions
- JetBrains Writerside IDE (recommended)
- Or any text editor for Markdown editing
- Git for version control
-
Clone the repository
git clone https://github.com/grokkingsoftwareengineering/grokkingsoftwareengineering.github.io.git cd grokkingsoftwareengineering.github.io -
Open in Writerside
- Launch JetBrains Writerside
- Open the project folder
- The Writerside configuration will be automatically detected
-
Preview locally
- Use Writerside's built-in preview functionality
- Or build locally using the Writerside CLI
grokkingsoftwareengineering/
├── .github/
│ └── workflows/
│ └── build-docs.yml # GitHub Actions workflow
├── Writerside/
│ ├── cfg/
│ │ └── buildprofiles.xml # Build configuration
│ ├── images/ # Static assets and styling
│ │ ├── gse-logo.png # Main logo
│ │ ├── favicon.png # Favicon
│ │ ├── gse-banner.svg # Social media banner
│ │ └── gse-styles.css # Custom styling
│ ├── topics/ # All article content
│ │ ├── Home.md # Main landing page
│ │ ├── Article-Template.md # Template for new articles
│ │ └── [topic-files].md # 60+ topic articles
│ ├── c.list # Categories configuration
│ ├── gse.tree # Main navigation structure
│ ├── v.list # Variables and branding
│ └── writerside.cfg # Main Writerside config
└── README.md # This file
We welcome contributions from engineers who share our mission of comprehensive technical education.
- Depth over brevity: Articles should be 3,000-10,000+ words
- Comprehensive coverage: Don't just show what, explain why and when
- Practical examples: Include real-world applications and code samples
- Progressive structure: Build concepts systematically
- Quality focus: Accuracy, clarity, and educational value are paramount
- Language-agnostic: Concepts apply to any language; use Node.js-style JavaScript for examples
- Review existing content to understand our style and avoid duplication
- Use the Article Template (
Writerside/topics/Article-Template.md) - Follow our writing guidelines for voice, tone, and structure
- Include practical examples and code samples where appropriate
- Test all code examples to ensure they work correctly
- Fork the repository and create a feature branch
- Write your content following our guidelines
- Preview locally using Writerside
- Submit a pull request with a clear description
- Collaborate on review to ensure quality and consistency
- New articles on topics from our roadmap
- Content enhancement of existing articles
- Code examples and practical demonstrations
- Technical review for accuracy and clarity
- Accessibility improvements and typo fixes
- Primary Color:
#1a365d(Deep blue - trust, depth, stability) - Secondary Color:
#2b6cb0(Bright blue - innovation, clarity) - Accent Color:
#38a169(Green - growth, progress) - Typography: Inter for text, JetBrains Mono for code
- Logo: Geometric foundation blocks representing solid engineering principles
- Reading-optimized layout: 75-character line length for optimal readability
- Progressive navigation: Clear learning paths from beginner to expert
- Deep-focus design: Minimal distractions to encourage thorough reading
- Accessibility: High contrast, clear hierarchy, semantic markup
The site automatically builds and deploys via GitHub Actions when changes are pushed to the main branch:
- Build: Writerside Docker container processes all content
- Test: Automated testing for broken links and structure
- Deploy: Static site deployment to GitHub Pages
For manual builds or testing:
# Using Writerside CLI (if installed)
writerside build --instance gse --output dist/
# Or using Docker
docker run --rm -v $(pwd):/docs jetbrains/writerside:243.22562 build --instance gse- Reading time estimation for all articles
- Search functionality across all content
- GitHub integration for easy contribution
- Responsive design for all device types
- SEO optimization for discoverability
- Issues: Report bugs or suggest improvements via GitHub Issues
- Discussions: Join technical discussions in GitHub Discussions
- Contributions: See our contribution guidelines above
- Contact: Questions about the project or collaboration opportunities
This project is open source and available under the MIT License.
GrokkingSoftwareEngineering is built by engineers, for engineers. Special thanks to all contributors who help build this comprehensive resource for the software engineering community.
Together, we're combating brain rot through quality technical education.