How patel-muhammad/first-pr-nmit works
Project type and purpose
• This is a _static website_ (index.html + styles.css) whose primary goal is to introduce beginners to the Git/GitHub Pull Request (PR) workflow.
• There is no backend service or database—just a small HTML/CSS site, a GitHub repository, and the Git‐based collaboration process.
Main components of the system
a. GitHub “Original Repository” (upstream)
b. Developer’s GitHub Fork (user’s copy)
c. Local Development Environment (developer’s machine)
d. Static Hosting / Browser (if served via GitHub Pages or any static‐site host)
e. Optional: Continuous Integration (CI) or review process (for merging PRs)
Relationships and data flows
• Fork: user clicks “Fork” → GitHub creates a _Forked Repo_ from the _Original Repo_.
• Clone: user runs git clone → copies the _Forked Repo_ to the _Local Environment_.
• Edit & Commit: user modifies index.html/css → git add & git commit → changes live in the _Local Environment_
• Push: user runs git push → updates the _Forked Repo_ on GitHub.
• Pull Request: user opens a PR → GitHub notifies maintainers, who review and _merge_ back into the _Original Repo_.
• Serve: once merged, GitHub Pages (or any static‐site host) delivers index.html + styles.css to the _Browser_.
Architectural patterns and design principles
• _Client‐side only:_ no server‐side code, purely static assets.
• _Git‐centric workflow:_ the “architecture” is driven by Git operations and GitHub’s collaboration model.
• _Separation of concerns:_ static content lives in the repo; hosting is delegated to a CDN or GitHub Pages; development occurs locally.
Technologies, frameworks, libraries
• HTML5, CSS3
• Git (branching, commit history)
• GitHub (fork/clone/push/PR/merge)
• Optional: GitHub Pages as a static file host
Essential elements to capture
• All four main components plus optional CI step
• A note that the site is purely static, served over HTTP/HTTPS