New theme: Osprey Delight (forked from Osprey)

[kdevo]

Theme submission

Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:

Link to my theme repository: https://github.com/kdevo/osprey-delight

I made sure that...

• [x] the repository contains a good README.md describing my theme
• [x] an open source license has been added to LICENSE.md
• [x] all metadata have been added to theme.toml
• [x] screenshots have been added in the images/ folder with the required dimensions
• [x] in case I'm using a customized demo via the exampleSite folder that
  • [x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
  • [ ] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample
• [ ] I tested my theme against the gohugoio/HugoBasicExample
  • [x] I've checked the developer tools' console in my browser for error messages (in general, not using the Hugo Basic Example)
• [x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.

Feel free to ask questions. We're glad to help.

[kdevo]

Additional comment:

Since @tomanistor recently fixed the theme to work again in the showcase I feel okay to publish my own interpretation of it.

The intent of this fork is not to replace Osprey (which I really like and started to use for my own site a while ago), but rather to provide an alternative choice for people who...

• do not need the built-in blog
• are in for a small speed boost
• like the modular extras or design changes I implemented

The changes I made since the fork are all summarized in the README.

If there is a problem please let me know. Thanks and keep up the good work!

[tomanistor]

Good stuff @kdevo, I love the forked edition!

[digitalcraftsman]

Hello @kdevo,

thank you for sharing this theme with the Hugo community. Great to see a the great Osprey theme into a more minimal one-page theme.

Your theme should be listed soon on the themes site. Furthermore, I'll promote your theme on Hugo's official Twitter account.

[kdevo]

Hi @digitalcraftsman,

awesome, thank you very much!

Two questions that came up while checking the theme's look and feel on the Hugo themes site:

1. The demo looks a bit empty. In the theme's exampleSite directory I added some gallery items which usually appear under the WORK section of the site, but according to the documentation I assume that the theme is completely rendered using the Hugo Basic example without accepting own/custom files in the content directory, correct? Is there a clever way around this limitation?
2. Is it correct that Emojis are not supported in the rendered README.md on the Hugo themes site? If it's not a bug (e.g. missing enableEmoji = true flag or similar), I might consider removing them from the original source because the raw :sparkles: (for instance) doesn't look as sparkling ✨ as expected.

Thanks in advance!