-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify which customization steps are mandatory before zola serve
succeeds
#19
Comments
Real! Same problem here |
Same problem here! |
I really like this theme - looks amazing - thank you @justint I'm trying to get started and am getting the below error also. I just followed the steps. |
The steps that I needed to add to make the theme useful are:
Also, add this to Finally, when you add |
@markstock Thank you! that worked nicely 😃 |
Your
justint.github.io
repo'sREADME
states:However, adding the Papaya theme is rather frustrating compared to doing exactly the above: forking
justint.github.io
.I start from a clean
zola init
and add the theme.After doing everything before Customization in the
README
.Ok, so I add
color_mode
to myconfig.toml
. This is not mentioned anywhere in theREADME
btw.Try again:
Ok, so the menu is mandatory. I read the resp. Customization section, add it, and try again:
That's when I gave up and forked
justint.github.io
and started modifying it. ☺I guess I am trying to say: if you want users to not fork
justint.github.io
there are two options:zola serve
succeeds after adding the Papaya theme?justint.github.io
but stripped of specifics.The text was updated successfully, but these errors were encountered: