Fork me on GitHub
#hoplon
<
2017-02-18
>
thedavidmeister02:02:32

also, hoplon functions just returns DOM elements

thedavidmeister02:02:12

i haven't tested this but you should just be able to do something like this

thedavidmeister02:02:03

(-> "#foo" js/jQuery (.append (div "My hoplon div")))

thedavidmeister02:02:35

ah wait, i see you want to go the other way

thedavidmeister02:02:16

yeah unless you want to get into scraping html with something like https://github.com/davidsantiago/hickory

thedavidmeister02:02:34

you pretty much have to stick the html from jekyll into hoplon as-is

thedavidmeister02:02:02

@anisk just taking a step back here, what's the main advantage of jekyll?

thedavidmeister02:02:34

if it's just markdown + file structure organisation, why not just implement something for markdown and namespaces in hoplon

thedavidmeister03:02:31

should be possible to make something like (def ^:blog-post my-post {:date "2017-02-18" :markdown "# Markdown in here"}) and have it turned into a browsable blog

alandipert03:02:04

There also perun, a boot based static site thing. Could theoretically compose with boot Hoplon app

alandipert03:02:39

It does permalink and markdown etc, in a cool bootish way

anisk19:02:05

Sorry, I didn't have notifications on here... @thedavidmeister I don't think I'd thought this one through very well... It seems like some blogging software (like wordpress, for example) take care of a lot of things ranging from keyword / date searching to SEO and the like. Granted, the SEO doesn't really mean much to me because I'm not actually trying to become a blogger, but still, it's nice that they do all of that for me. So I think I'm just going to go with that solution for now. @alandipert I've bookmarked it and once I have the time to refactor the site I think I'll end up going with that solution (for continuity and whatnot). Thanks again, guys. You guys are awesome. 🙂