You could say a lot more: you could link to this thread, or reproduce the issue in their issue tracker. That isn’t a pain, it is what we all need to improve themes.
This is possibly an outlier (I qualify it as “possibly”, here’s hoping we don’t have more issues). The extended version is related to outputting processed assets, but you can search the forums for more info. You probably don’t need to know (most folks don’t).
If you see a theme’s instructions that don’t work:
Contact the theme author, work with them to update the theme
I don’t know anything about this portion of the project, but wanted to point out that clarification may be warranted somewhere for someone (I know, super helpful!).
It’s pretty simple really. To make a theme that uses PostCSS features work for the basic version of Hugo the theme author should generate the resources locally and commit them to Git.
I published my attempt at following your instructions above. I may have done something wrong so feel free to look over them and advise.
I also loaded the Extended Hugo and followed the instructions published in the theme and it loaded without a problem first attempt.
All I want is a list of commands I can copy and paste into a Linux Bash session and arrive at a working Theme.
I do not know about Extended Hugo and what it does.
I also do not wish my experience on anyone else, so I think it is reasonable to ask the Theme developer about revising his instructions. He agreed.
I am new to Hugo Theme deployment and am not qualified to speak to Theme publishing requirements.
I do appreciate the help getting this Theme working for me.
I gave you that simplified list above. I cannot figure out what you’re doing wrong.
Provided you have a sample project the only command you really need is to git clone that theme.
Hugo Extended allows for for SASS resource to CSS transformation and also requires the PostCSS cli installed from npm.
Hugo basic does not have the above feature hence the error.
But since the SASS resources of the Hugo Fresh theme are now generated and commited by the author you do not need Hugo Extended because the SASS resource transformation has already been done and it’s possible to use the theme with the Basic version of Hugo.
I tested using the fresh theme with the standard hugo and it does not build.
It does build with the extended hugo.
I used a fresh aws ec2 instance, installed Hugo .48 and used the themes instructions to install the theme. This gave me the standard “this feature is not available in your current Hugo version”
I replaced the standard hugo with the extended hugo binary and hugo runs fine.
I did contact the Theme author with this information.
If anyone could verify it does not work using standard Hugo, it would be appreciated.
If someone thinks this theme works with the standard version of hugo, please provide the step by step instructions showing how it was built so I can see the error of my ways .
Thanks!
Thanks for your reply…I downloaded [hugo_0.55.4_Windows-64bit.zip]. Still not working. I got an error saying "failed to transform resource: TOCSS: failed to transform “style.sass”. I am using Hugo fresh theme… before that, I converted yaml file into toml.
.