Move code output style file to this repo?

[joelostblom]

I was going to copy the changes from seedcase-project/check-datapackage#260 to the other seedcase projects to ensure that the code output always is styled the same in the docs pages. However, I realized that having a separate copy in each repo becomes quite clunky if we decide to update the styling. And since the _pretty_repr.qmd file really is all output documentation styling, I'm thinking that it would make more sense to have that file in this repo instead and consider it part of the seedcase-theme (another way to think about this is that if we could have done those same color modification with css only, then it would for sure live in this repo).

My understanding is that when this extension is installed, all the files from the _extensions folder are copied over locally. So if we include _pretty_repr.qmd there, it would become available to all projects that use seedcase-theme and the relevant doc pages could include it using the following line (which I think is similar to how we currently include favicons etc, eg in https://github.com/seedcase-project/seedcase-flower/pull/47/changes):

{{< include ../../_extensions/seedcase-project/seedcase-theme/_pretty_repr.qmd >}}

What do you think of that organization @lwjohnst86 ?

[lwjohnst86]

Since this requires running Python, this is only relevant for Python projects and not all Seedcase websites, so it would be better placed in template-python-project in /template/docs/includes/.

[lwjohnst86]

I'll transfer this to that repo now ☺️

[joelostblom]

Ah interesting, I thought the docs in the template package is a description of how to install and use our template package, not an example for how to create docs for a new package. It also seems like that from guide page in the template docs, doesn't it?

What I mean with that is if I create a new project from the template, am I not likely to delete the docs folder because it is a description of the template package and not a template for the new package I'm making. But maybe I'm misunderstanding?

I'm not against having it here, just wanted to check in on the above before PRing.

[lwjohnst86]

You're right, /docs/ is for the template. But /template/docs/ is the docs/ folder created in the new project using the template. Everything under /template/ gets used when creating new templates, while everything in the root or other folders is the infrastructure for Copier (and docs to use the Copier template).

[joelostblom]

Ah right, I looked in the wrong place 🤦