Pages and Generated URLs

A source filename and a public URL are related, but they are not identical concepts.

Simple page

Source:

about.md

A normal build can create output such as:

_site/about.html

and a local URL such as:

/about.html

But Jekyll can also generate directory-style URLs depending on source structure, front matter, and permalink configuration.

Inspect instead of assuming

For three pages in your current site, record:

Use generated output and Liquid evidence to fill it.

Why this matters

Hard-coding assumptions about source paths can create broken links after:

• permalink changes;
• deployment under a repository subpath;
• collection configuration changes;
• moving source files.

page.url

Jekyll exposes the generated URL for a page through data such as:

{{ page.url }}

This is why the tutorial can compare navigation links with the current page.

Controlled move

Move a disposable page into a subdirectory or adjust its output behavior.

Predict the URL.

Build and compare:

• source location;
• generated location;
• page URL.

Checkpoint

Explain why "the file is in this folder" is not always enough to determine the final public URL.