learning-website-framework1-1  Exercise 1: Measure Your Site
==========================================================

The goal is numbers, not opinions. Count the files under each top-level
folder of content/ and list the biggest areas.

Git Bash (run from the website-content folder):

  for d in content/*/; do
    n=$(find "$d" -type f -name '*.html' | wc -l)
    echo "$n  $d"
  done | sort -rn

PowerShell (same folder):

  Get-ChildItem content -Directory | ForEach-Object {
    [pscustomobject]@{
      Area  = $_.Name
      Pages = (Get-ChildItem $_.FullName -Recurse -File -Filter *.html).Count
    }
  } | Sort-Object Pages -Descending

Both can be slow on a OneDrive folder the first time; let it finish.

Record the result in a table like this (your numbers will differ):

  Area                 HTML pages   Share
  -------------------  ----------   -----
  <biggest area>       ...          ...%
  <next area>          ...          ...%
  ...
  TOTAL                ...          100%

Then answer:
1. Which areas hold most of the pages? (A split is only worth it for areas
   that are big or that grow fast.)
2. Which area is growing fastest right now? (Languages, for this site.)
3. Which areas would still need links to each other after a split?

WHY THIS WORKS AS AN ANSWER
---------------------------
A decision to split the site should start from a measurement, not a feeling.
The count tells you which areas are big enough to deserve their own site, and
the cross-links question tells you how much shared navigation you will have to
maintain afterwards. Chapter 2 of Learning Website: Framework & Architecture
uses this table to map content to sites.