Closed syvwlch closed 2 years ago
I had a brief moment of confusion but it is a minor thing and not really consequential.
yml is the file extension for a yaml file. So "...add to the yml at either site or article..." means "add it to the yml file..."
Yes?
Well, at the site level, which is what I did, you add it to a _site.yml
file which applies to the entire site.
When doing this at the article level you add it to the yml header of the article's Rmarkdown file. For example, here's the homepage's yml header, with a theme:
key added pointing to the new css file:
---
title: "Welcome Aboard"
description: |
The Data-Ship _Data Ignota_
theme: site.css
site: distill::distill_website
output:
distill::distill_article
---
Thanks for the clarification. I'm learning my way around github by following your example, but a "how to use github" tutorial would be useful at this point. I'll research that on my own, as I'm sure that material is here.
The best way, I've found, is to learn Git and GitHub within the context of something else.
It's infrastructure.
So you'd pick something you're interested in learning/doing and find a book/course that shows you how and uses Git... or one that explains Git in the context of that field or application or language?
Makes good sense. I have at least one stalled proto-project for linux stuff that I could get back to. As time permits, I'll pull that out, dust it off, and see if I can reweave the unraveled tapestry.
Is your feature request related to a problem? Please describe.
The site looks rather plain Jane, and already have an issue #49 to fix some spacing issues with lists.
Describe the solution you'd like
Canonical solve for a
distill
package site is to create a theme css file and add it to the yml at either site or article level.