100 Days Of Code Log R2

The 100 Days Of Code Log R2 is a Jekyll-based blog template for publishing a daily coding log, structured as consecutive numbered days with project, progress, and resource links.

What is the 100 Days Of Code Log R2?

The 100 Days Of Code Log R2 is a static site template built with Jekyll by James Priest to document his second round of the #100DaysOfCode challenge. It takes daily markdown entries as input and renders a chronological log with 100 dated sections, each containing project name, progress notes, thoughts, and links to work. The template is hosted on GitHub Pages and uses Ruby and Jekyll with customized template code.

Key Features

• Daily entry structure — Each day is a dated heading with fields for project, progress, thoughts, and link to work, ensuring consistent logging across 100 days.
• Multi-round navigation — A table at the top links to Round 1, Round 3, Round 4, and Round 5 logs, so readers can browse the entire challenge history.
• Code block rendering — Entries include syntax-highlighted snippets for JavaScript, bash, and Vim, making technical notes readable on the page.
• Resource and demo links — Every entry links to course notes, CodePen live samples, GitHub repositories, and official documentation, turning the log into a study hub.
• Jekyll and GitHub Pages workflow — The site is built with Ruby and Jekyll and regenerates automatically when commits are pushed to GitHub Pages.
• Goal checklist — The header includes a checkbox list of challenge goals (code daily, complete scholarship, join nanodegree), all marked complete.
• Responsive design — Because the author studied responsive web design fundamentals, the log's layout adapts to mobile viewports with contained tables and breakpoints.
• Commitment metadata — Start and end dates are displayed, along with links to the official #100DaysOfCode repo and 100daysofcode.com.

Who is it for?

• Developers taking the #100DaysOfCode challenge — They can fork this repository and replace the day entries with their own projects and notes to maintain a public streak.
• Self-directed learners documenting courses — The format suits anyone recording video courses, reading notes, and coding exercises, as the author did for Udacity's Mobile Web Specialist track.
• Job seekers building a coding portfolio — A public, consistently updated daily log serves as evidence of dedication and breadth of skills for hiring managers.

What can you do with this template?

• Run a daily coding streak — Publish one entry per day for 100 days, each including what was built and what was learned, to stay accountable.
• Organize a learning path — Link each day to detailed course notes and live demos on CodePen or GitHub so the log becomes a table of contents for a self-paced curriculum.
• Showcase professional development — Use the log to document certifications, bootcamps, and side projects, as James Priest did to track his Google scholarship and React bootcamp completion.

How does this template work?

The template is written as a Markdown file that Jekyll processes into a static HTML page. Each day is a section with a heading like "Day 99", and the author fills in the project, progress, thoughts, and links. After pushing the file to a GitHub repository, GitHub Pages rebuilds the site automatically using Jekyll, serving the latest log at the public URL.

Pros and cons

• Pros: Free to host on GitHub Pages, no database required, code blocks render with syntax highlighting, and the multi-round navigation keeps multiple logs interconnected.
• Cons: Requires basic Markdown and Git knowledge to edit; the daily numbering is manual, so skipping a day means renumbering entries.

Pricing

Free — the template is publicly available on GitHub Pages, and Jekyll is an open-source static site generator that runs on any platform.

FAQ

Is the 100 Days Of Code Log R2 free?

Yes, the log is hosted publicly on GitHub Pages and the source repository is accessible, so anyone can fork or copy it at no cost. Jekyll, the generator, is open source.

Do I need to install anything to use it?

To edit and preview locally, you need Jekyll (Ruby-based) or you can simply edit the Markdown file on GitHub and let GitHub Pages build it automatically. A basic understanding of Git and Markdown is helpful.

Can I use this log without Jekyll?

The Markdown file itself can be read as plain text anywhere, but the rendered page with navigation and code formatting depends on Jekyll and GitHub Pages. You could also convert it to HTML with other tools.

How long did the original challenge take?

The author logged 100 consecutive days from January 28, 2018 to May 8, 2018. The log includes links to five total rounds, so the setup supports multiple iterations over time.

Does the template include any special features for code?

Yes, entries contain code samples for JavaScript, SQL, bash, and Vim config, which are automatically highlighted. The log also embeds screenshots and CodePen demos, though those are stored in the repository's assets folder.