seanlane / gochowdown Goto Github PK

Have you considered supporting other languages?
I don't know hugos approach for internationalization but I saw its possible ...

Hi,

I tried to publish some of the recipes using GoChowDown and noticed none of yield, cooking or preparation times end up anywhere in the output. I haven’t checked, but probably there’s more of those.

I may at some point send a pull request, but please consider adding these.

Hi,

I was wondering whether this theme support "contentDir" option in Hugo configuration file, or better Module config mounts.

I would like to use an external folder to version my recipes with my other markdowns.

Maybe this is not due to the theme but a miss-configuration on my side. What your guess on that ?

Thanks for your project. This is really cool.

Hey, I am looking for a bit of feedback, before sending in a pull request.

The "inspired by" line is a bit weird.

• When only a sourceName is defined, then it looks fine: "inspired by Name of Source"
• When both a sourceName and authorName, then it becomes bit weird: "inspired by Name of Source from Author Name"
• When only a authorName is defined, then it is a invalid sentence: "inspired from Author Name"

I want to create a pull request for "Inspired by Name of Source. Written by Author Name.". This makes the variations easy (the whole thing or only one of the pieces) and translations are easy.

I am not a native English speaker, so suggestions for the text are welcome.

Hi,
It would be nice to somehow be able to separate long ingredient lists such that they become more readable. I know that I could use components for this but sometimes I don't want to clutter the components. An example would be to separate wet and dry ingredients in a baking recipe, different components don't really fit in that case. Something like

Ingredients:
[ ] apples
[ ] bananas

[ ] oranges

with new lines inbetween would be sufficient.

Hi,
Does the pagination only apply to the components or also to the recipes shown on the front page ?

PS : Thanks for all the great work on this theme !

Hi Sean,
Love this theme!
When I create recipes I dont see the recipes on the frontpage as the image on the readme suggest, I only see a blue block with 'Recipes' and if I click on that I see a list of recipes.

I found a very cool Hugo template to render a word cloud of the used tags with logarithmic distribution of font sizes: https://www.sidorenko.io/post/2017/07/nice-tagcloud-with-hugo/

I implemented this for my Gochowdown site and like/use the tags page a lot more now. It's much more useful than a long list of words imho. This is what it looks like on my site:

I like it so much that I wanted to suggest making it the default for Gochowdown. The only thing that would need to be customized to include it in the theme is the smallest and biggest font size as far as I can see.

I wonder if the components should be viewable too, you can click them but they are not displayed, that is, there is a page with the title, but nothing else.

This is my first contact with Hugo and with this theme. I've tried to get the configured title of the site ({{ .Site.title}}) into the navigation bar.

I've done this by adding an entry into <nav> section of header.html. Here I used <h1> to get a bigger this.

In the end, the result looks ugly (wrong font, wrong color, bad spacing). I don't know which CSS styles I have to use to get a proper look and feel. ;-)

Could you please add the title into the navigation bar area?
Could this be "switchable" from within config.yml?

Is there a parameter to specify a Google Analytics property for tracking?

Hi,
Thank you for your great work with GoChowdown. I think Hugo needs more recipe themes like that (or at all)!

However, there are some things I would like to change, like the navbar, recipe listings, etc. So, it becomes more or less its own thing. So I thought about giving it its own name like GoChopChop (I'm open for input). In the end, that would mean more variety what is beneficial for everybody involved.

Instead of starting at zero, and because I like GoChowdown, I decided to fork your project and edit it to my liking. However, to value your and the communities work, I'm not sure how to treat the licensing. As far as I know, I need to stick with the same license type, which is MIT (I'm fine with that).
There still is the copyright note within the license with your name, @seanlane. My idea is to add another line below your name and add mine, so you keep the copyright of the code you contributed. In addition to that, I would like to add in the README that my project is a fork of GoChowdown with a link to this project.

Are you ok with that? I know according to the license, I can redistribute, etc., but I think it's only fair to ask you if you agree with how I want to handle the license stuff. =)

First I want to congratulate you for the great job in developing the theme.
I'm using it as a base on the blog I'm developing through R and Blogdown.
everything went well, but the main menu does not appear when I load the html.
I tried to modify config.toml and config.yml, but without success.

what can I be doing wrong to not be able to reproduce as the model?

https://herminiosabino.github.io/clara/

I want to thank's in advance.

Sincerely.

It would be very nice to reuse the Theme as a Go Module. You only have to refer to the repository .

To use the Theme as Go Module you only have to put a simple short go.mod file in the root of the repository.

See example for GoChowDown go.mod file.

module github.com/seanlane/gochowdown

go 1.16

Thanks a lot!

From the Demo ... https://themes.gohugo.io/theme/gochowdown/ when you click on Categories it goes to 404 page ...

https://themes.gohugo.io//theme/gochowdown/category/

Would be great if https://themes.gohugo.io//theme/gochowdown/ showed some sample recipes to inspire confidence in adopting the theme. I don't know if this is related to issue #2....

Since some pull requests have added the ability to provide translations for certain languages, the README should be updated to describe how to use those.

Maybe look into having the README translated into said languages as well?

Add a search box to filter recipes on the page.

https://gohugo.io/tools/search/