You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Followed the installation steps of this plugin (added the plugin to the jekyll_plugins group in the Gemfile)
Tried serving the site with bundle exec jekyll serve, but due to my theme using jekyll-seo-tag the site failed to build. I've hit problems before with the specific {% seo %} so maybe this is more of an issue with that gem? It would be nice if it caused a warning instead?
Added the jekyll-seo-tag plugin and tried again and it worked as expected 馃帀
Parting notes
Works exactly as expected 馃憤
Issue with theme dependancies, but as seen here there are problems with catering for this
Should plugins error more gracefully? Open question 馃挰
The resulting site is quite blank, maybe my theme isn't working hard enough 馃槼
@daviddarnes thanks for this great feedback. As an initial release, plugins are a bit of a rough edge still. Although #4 is just a placeholder for the moment, I'd love to see a better user experience around plugins. At the very least, we could potentially warn users if the theme requires a plugin that's not in the config, and ideally, we'd be able to require it if it's part of the whitelist (or always require it if not in safe mode).
@benbalter you're very welcome! Totally understand with plugins, I appreciate that you need to take a somewhat delicate approach to this as it could potentially affect a lot of people. If you require any more testing just let us know, I'll probably be dropping by this repo every so often anyway. I'm keen to make my theme versatile for different platforms.
Hi 馃憢, I created the theme Alembic. I was copied in on a thread from @DirtyF to test out this plugin. Here's what I found:
Installation
jekyll new
jekyll_plugins
group in theGemfile
)bundle exec jekyll serve
, but due to my theme using jekyll-seo-tag the site failed to build. I've hit problems before with the specific{% seo %}
so maybe this is more of an issue with that gem? It would be nice if it caused a warning instead?Parting notes
Discussion thread on the Jekyll forums if people want to chat further https://talk.jekyllrb.com/t/plugin-jekyll-remote-theme/1089/5
The text was updated successfully, but these errors were encountered: