Skip to content

docs: add article about how google.com works - #78

Open
spideythedev wants to merge 3 commits into
open-devhub:mainfrom
spideythedev:main
Open

docs: add article about how google.com works#78
spideythedev wants to merge 3 commits into
open-devhub:mainfrom
spideythedev:main

Conversation

@spideythedev

Copy link
Copy Markdown

Add: “What Happens When You Type google.com?” Blog Article

Overview

Adds a new educational blog article explaining what happens behind the scenes when a user types google.com into a browser and presses Enter.

The article takes readers through the complete journey from URL input to rendered pixels.

What’s Covered

  • URL parsing
  • Browser and OS caching
  • DNS resolution
  • Root, TLD, and authoritative DNS
  • IP addresses and network routing
  • BGP and Internet infrastructure
  • TCP and QUIC
  • TLS and HTTPS
  • HTTP/1.1, HTTP/2, and HTTP/3
  • Google's distributed infrastructure
  • Load balancing
  • HTTP requests and responses
  • Compression
  • HTML parsing
  • DOM and CSSOM
  • Layout and painting
  • Browser compositing
  • Failure scenarios
  • Complete request-to-render pipeline

Why

The goal is to give developers a clear mental model of how the web works across multiple layers, from networking infrastructure to browser rendering.

The article is written as an approachable technical deep dive rather than a framework-specific tutorial.

Type of Change

  • New blog article
  • Bug fix
  • Feature
  • Refactor
  • Documentation update

Content

Title: What Happens When You Type google.com?

Category: Web

Tags: Web, Networking, DNS, HTTP, TLS, Browsers, Internet, How It Works

Checklist

  • Markdown formatting verified
  • Code blocks formatted correctly
  • Article structure reviewed
  • Links included
  • Original educational content
  • No application logic changed

@devhub-bot

devhub-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown

Warning

Some commit messages in this PR do not follow the Conventional Commits specification.

Expected format: type(scope): description

📋 Invalid commit messages
  • Commit a5d2e71 does not follow Conventional Commits: Create what-happens-when-you-type-google.md
  • Commit 3357c16 does not follow Conventional Commits: Update what-happens-when-you-type-google.md
  • Commit 197409c does not follow Conventional Commits: Merge pull request #1 from spideythedev/spideythedev-patch-1

Tip

Valid types:
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

Note

This is just a friendly reminder and will not block the PR from being merged.

@devhub-bot devhub-bot Bot added the docs Improvements or additions to documentation label Sep 2, 2026
@beetle-ai

beetle-ai Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary by Beetle

This PR adds a comprehensive educational blog post titled "What Happens When You Type google.com?" to the website's content repository. The article provides an in-depth technical walkthrough of the entire journey from user input to rendered webpage, covering DNS resolution, network routing, TLS encryption, HTTP protocols, Google's infrastructure, and browser rendering processes. A minor metadata correction was also applied to fix the category field.

📁 File Changes Summary (Consolidated across all commits):

File Status Changes Description
content/blog/what-happens-when-you-type-google.md Added +1,212/-0 Comprehensive technical blog post explaining the complete journey of typing a URL into a browser, covering DNS, TCP/TLS handshakes, HTTP protocols, network routing, Google's distributed infrastructure, and browser rendering pipeline. Includes detailed explanations of each stage with ASCII diagrams and conceptual models. Minor metadata update: category field changed from "Web" to "WebSite".

Total Changes: 1 file changed, +1,213 additions, -1 deletion

🎯 Key Changes:

  • New Educational Content: Added a 1,212-line technical blog post that breaks down the complex process of web browsing into 28 digestible sections
  • Comprehensive Coverage: Explains DNS hierarchies, TCP three-way handshakes, TLS certificate verification, HTTP/2 and HTTP/3 protocols, load balancing, and browser rendering stages (DOM, CSSOM, layout, paint, compositing)
  • Visual Learning: Includes ASCII diagrams and conceptual flowcharts throughout to illustrate complex networking and rendering concepts
  • Layered Architecture Focus: Emphasizes the importance of understanding network layers and separation of concerns in complex systems
  • Practical Debugging Guidance: Provides troubleshooting insights for common failure points (DNS errors, connection failures, TLS issues, HTTP errors)
  • Metadata Refinement: Updated category classification from "Web" to "WebSite" for better content organization

📊 Impact Assessment:

  • Security: ✅ Positive — The post educates readers about TLS certificate verification, HTTPS security properties, and the importance of encrypted connections. Promotes security awareness by explaining how browsers validate server authenticity.
  • Performance: ✅ Neutral — This is educational content with no performance implications. The post itself discusses performance optimization concepts (compression, HTTP/2 multiplexing, edge infrastructure) but doesn't affect site performance.
  • Maintainability: ✅ Positive — Well-structured markdown with clear section headings, consistent formatting, and logical progression. Easy to update individual sections independently. Metadata is properly formatted for content management systems.
  • Testing: ✅ Positive — Content is self-contained and doesn't require functional testing. The technical accuracy of explanations (DNS hierarchy, TLS flow, rendering pipeline) aligns with industry standards and best practices. No code dependencies to test.
⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only.Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide
  • Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
  • Comment @beetle on any PR to start analysis manually
  • Comment @beetle stop to stop any ongoing analysis

Follow us: Beetle · X · LinkedIn

@beetle-ai

beetle-ai Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

✅ You're good to merge this PR! No issues found. Great job!

Settings
⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only.Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide
  • Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
  • Comment @beetle on any PR to start analysis manually
  • Comment @beetle stop to stop any ongoing analysis

@devhub-bot

devhub-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown

Warning

Linting checks did not pass for this PR.

Run: View logs

Tip

Make sure to check the following before pushing:

  • code formatting issues
  • code quality / linting errors
  • unused or broken imports
  • syntax or type issues (if applicable)
  • secret leaks or exposed credentials
  • security / dependency vulnerabilities
  • invalid YAML / JSON / config files

Then fix the issues, commit, and push again.

Note

This is just a friendly reminder and will not block the PR from being merged.

@calebephrem

Copy link
Copy Markdown
Member

I'll talk to you about this one in discord :3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants