4 ms·
Well, they're not really Jekyll plugins -- just Javascript plugins on the front-end (hence disqus comments instead of your own database of comments, google cust
by jordanlev 15y ago
Well, they're not really Jekyll plugins -- just Javascript plugins on the front-end (hence disqus comments instead of your own database of comments, google custom search instead of your own internal search engine, etc.)
- rcfox 15y agoSorry, I was referring to these plugins: http://octopress.org/docs/plugins/ http://octopress.org/docs/plugins/
- jordanlev 15y agoOh, I get it. Those plugins are "compile-time" -- so they happen during the HTML generation process, before going up to github -- all github ever sees is static HTML and CSS files.
- rcfox 15y agoI played with Jekyll on GitHub several months ago, but as I recall, you commit your source files to the repo, and the GitHub would run Jekyll to compile them to HTML. (And send you an annoying message every time that it was successful...)
- calloc 15y agoBut github does that part for you. You push up the raw files AND Github runs Jekyll and generates the HTML files.
- mkopinsky 15y agoCould you have this as a two stage process? Make changes to files, push to my repo, repo hook runs jeckyll, commits new static assets, and pushes to github? This does require using a central server other than github I guess, though...
- pyre 15y agoYou could make a local shell script or Makefile that pulls together those commands and then pushes to github. No need for a central server.