Document custom fork of styling? about one-click-hugo-cms

[easherma]

@erquhart I understand that, but it would be easier to adopt with some documentation on the differences of this custom version, especially if someone is unfamiliar with PostCSS or new to Tachyons.

For instance, I just spent awhile debugging some odd behavior on my site and have deduced that _states.css is probably a custom add. Is this correct? If so, a list of these and others in the readmes and/or in the css files themselves would help. Happy to coordinate on a PR!

Somewhat tangentially, I'm not sure that using custom forks of these libraries is a great move for a repo that is supposed to be a template that speeds adoption of the platform.

[easherma]

@darindimitroff I'm not following the logic there, but I understand you not wanting to do the work to revert to a vanilla Tachyons.

Most people may unfamiliar with Tachyons, but everyone besides yourself is unfamiliar with whatever extensions or modifications you made. It seems like if that was a concern we'd have more explicit documentation of the styling here and/or how it varies from vanilla Tachyons, or we'd call it a day and use vanilla Tachyons and point to their docs.

That being said, I greatly appreciate this template as I've been able to build off it and learn how to use Netlify at the same time and have actually learned Tachyons through this template. That being said, in my fork I've also pretty much slowly replaced much of the css with vanilla Tachyons. :-D

[erquhart]

That's actually the way Tachyons is supposed to be used. Customizing it, which most projects require, means editing the source, which means you can't update.

_{Sent with GitHawk}

[erquhart]

Agreed, that's why I don't use Tachyons lol. If any effort went toward the problem you're describing, I think it should be toward getting this project off of Tachyons.

Otherwise, if you prefer to contribute documentation, that's great too.

_{Sent with GitHawk}

[easherma]

@darindimitroff you are the original creator, right? Any thoughts on this?

[darindimitroff]

I can add some documentation around the custom fork, but I don’t plan on implementing vanilla Tachyons. Most people using the template might not be familiar with Tachyons to begin with, so the idea is to use the atomic patterns as a useful paradigm in general.

[erquhart]

We'll definitely contributions towards improvement! Closing for now but do comment if there's anything further.