@@ -436,4 +436,45 @@ flowchart TB
436436 F --> G[Merge complete ✓]
437437 style A fill:#ffe6e6,stroke:#f00
438438 style G fill:#e6ffe6,stroke:#0f0
439- ```
439+ ```
440+
441+ ## Common Questions
442+
443+
444+ ??? question "Why do I need the staging area? Can't I just commit directly?"
445+ The staging area gives you control! You can:
446+
447+ - Commit only related changes together
448+ - Review changes before committing
449+ - Keep work-in-progress unstaged
450+ - Create clean, logical commit history
451+
452+ Many Git tools allow skipping staging (` git commit -a ` ), but understanding it makes you a better Git user.
453+
454+ ??? question "What's the difference between Git and GitHub?"
455+ - ** Git** = Version control software (runs on your computer)
456+ - ** GitHub** = Website for hosting Git repositories (in the cloud)
457+
458+ Think of it like:
459+ - Git = Microsoft Word
460+ - GitHub = Google Docs
461+
462+ We'll cover GitHub in detail later!
463+
464+ ??? question "Can I use Git for non-code projects?"
465+ Absolutely! Git works great for:
466+
467+ - Documentation (Markdown, LaTeX)
468+ - Design files (if text-based)
469+ - Configuration files
470+ - Writing (books, articles)
471+ - Any text files that change over time
472+
473+ ??? question "How much space does Git use?"
474+ Git is surprisingly efficient! It:
475+
476+ - Compresses data
477+ - Stores only changes (internally)
478+ - Removes duplicates
479+
480+ A repo with years of history might only be a few MB.
0 commit comments