-
Notifications
You must be signed in to change notification settings - Fork 61
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
[ENHANCEMENT] - Improve blog post template cosmetically #331
Comments
Would you maybe want the default for a blog draft be set for true? I currently added this into my branch because I am often not immediately ready to launch it since I work on it through out the week but still do lots of pushes to my repo. If I had the skills I would test it out but I am not quite there yet. |
if you would prefer to have it set to true, you can override the archetype for the blog post in your own repo (I don't want to get opinionated about workflow in the theme itself). hugo will look for the archetypes in the site's folder before the theme, so any archetypes you set there will take precedence! |
the tricky thing with image resizing is that it happens (the generation of the different sizes) usually outside of hugo (in the one example, the author uses gulp to process the different images, and what the shortcode does is pick which image of the resized ones to present, etc) I try to keep the theme away from assuming/requiring anything other than having hugo installed; adding in There are some things we could do to help the images be more responsive; generally the approach I have taken is "mobile first" so the default banner/thumbnails should all work fine. If you are doing stuff within your own markdown files it gets trickier. Most of the images in the theme are displayed with the class |
Thanks for the reply! Tested out the |
You'll need to add them; if you wanted to get slick, you could create your own shortcode (again, shortcodes outside of the theme take precedent) where you could do something like this: Create
you would then call it in your markdown like this:
Note that this is not testing code; you might need to tweak it a bit. And if there are other things you want to make the |
Cool! Thanks for setting the framework there and helping me understand :) |
Once ##310 is merged, we will want to do some work to make individual blog post pages look a little nicer, but this is a cosmetic improvement.
The text was updated successfully, but these errors were encountered: