Examples from 0.3.x included in docs for 0.2.x about perseus HOT 8 CLOSED

Ah. v0.3.0 will go stable tomorrow, so I'd advise upgrading for now, but that is a very clear problem in the docs that needs solving! Thanks for the report!

from perseus.

Okay, this was easily fixed by making the Checkout action copy in the whole Git history with fetch-depth: 0, rather than its default behavior of copying in only parts. The website now compiles both locally and on CI, and I believe this issue is resolved!

from perseus.

This will require getting previous version of files with git show programmatically, which I'll set up tomorrow, it's certainly necessary to do.

from perseus.

Great! I didn't look up how the docs are generated, so I don't have suggestions how to fix it.

from perseus.

For some reason this isn't building correctly. Reopening until I've figured that out.

from perseus.

Also, I feel I should add to this that saying v0.3.0 would be stabilized today was incorrect (sorry!), that was before the plugins system was scheduled for that release, so it'll be a little while before it goes stable. See #58 for details. That said, v0.3.0 is perfectly usable in beta form.

from perseus.

Also, I feel I should add to this that saying v0.3.0 would be stabilized today was incorrect (sorry!)...

OK, no problem. At the moment, I'm just experimenting, so switching from v0.2.x to v0.3.0 shouldn't be a problem.

Regarding plugins, if I plan to use perseus serve to generate CSS in static via tailwindcss, should that fall into the Type 3 plugins? (sorry for off topic)

from perseus.

Right now, that's ambiguous, because that'd be setup/teardown code (rather than modifying any existing Perseus behavior), but it would either be type 1 or type 2. Likely type 1.

from perseus.