RobotnixAcademy

Unit 01 · overview

Unit 1: Foundations and the Jekyll Build

A website can look complicated in the browser while beginning as ordinary files in a folder.

This Unit strips the stack down on purpose. No theme. No starter template. No magic button that hides the build.

You will create a first page, understand why Jekyll runs through Ruby and Bundler, run the Jekyll CLI, inspect generated _site output, make controlled changes, and break one layer on purpose so you can see where failures actually live.

Unit question

What happens between editing a source file and seeing a finished page in the browser?

Build model

SOURCE FILES
      ↓
JEKYLL RENDER / BUILD
      ↓
GENERATED SITE (`_site`)
      ↓
LOCAL SERVER / DEPLOYMENT
      ↓
BROWSER

Do not move on because the diagram looks familiar. Move on when you can point to evidence from your own project for every arrow.

Unit path

  1. A Website Is Files Before It Is a Screen
  2. What Jekyll Actually Does
  3. Ruby, Gems, Bundler, and the Gemfile
  4. Create the First Site Without a Theme
  5. Source → Build → _site → Server → Browser
  6. jekyll build, jekyll serve, and the CLI
  7. Project Anatomy and Generated Files
  8. Break the First Build and Trace the Failure
  9. Unit Build: First Portfolio Checkpoint

There is no calendar deadline built into this sequence. The checkpoint matters more than the clock.

Unit artifact

A local Jekyll portfolio with a dependency record, generated output, source/build trace, Expected/Observed test, and bounded failure diagnosis.

Upstream foundation

This Unit adapts the Jekyll project's official README and setup/build documentation at pinned commit 74d751339d3e534aa51d5d7b0640e9bd743509e4 under the MIT License. Attribution and the license notice are governed through sources/jekyll/.