Open ClaytonJY opened 7 years ago
@ClaytonJY is this something we want to do?
@ellisvalentiner I think so. Not sure when I'll find the time, but here's what I've been thinking:
We should probably make a new repo for it, unless we want to put the source in a branch like blogdown
and have some CI build it and pop the public
folder into master
. I kinda like the repo-level decoupling, but unless we want to buy a domain name it probably doesn't matter. Automating this is basically the same as what you did for the bookdown workshop materials, though I keep hoping there's a slightly simpler, less bash-y way, or a way that avoids tying the build-and-push commits to a single user. Haven't seen one yet.
The first trick is picking a nice theme, the second is appropriately converting all the posts. The YAML will probably need to change, but that should be scriptable.
If you have the time/energy to get started, that'd make it easier for me and anyone else (@mooreaw?) to jump in I think; picking a theme is what scares me the most
I kinda like the repo-level decoupling, but unless we want to buy a domain name it probably doesn't matter.
I wouldn't necessarily mind covering that cost.
Automating this is basically the same as what you did for the bookdown workshop materials, though I keep hoping there's a slightly simpler, less bash-y way, or a way that avoids tying the build-and-push commits to a single user. Haven't seen one yet.
Neither have I. But I don't have a problem with the bash script way.
The YAML will probably need to change, but that should be scriptable.
I don't think it needs to change, but we might want to go back and update them anyway.
Tentative steps:
I'll do some research on what's needed to migrate-- I think I've seen at least one guide on how to convert straight from Jekyll to blogdown
On Thu, Jul 20, 2017 at 4:30 PM Ellis Valentiner notifications@github.com wrote:
I kinda like the repo-level decoupling, but unless we want to buy a domain name it probably doesn't matter.
I wouldn't necessarily mind covering that cost.
Automating this is basically the same as what you did for the bookdown workshop materials, though I keep hoping there's a slightly simpler, less bash-y way, or a way that avoids tying the build-and-push commits to a single user. Haven't seen one yet.
Neither have I. But I don't have a problem with the bash script way.
The YAML will probably need to change, but that should be scriptable.
I don't think it needs to change, but we might want to go back and update them anyway.
Tentative steps:
- pick a theme
- create new repo(s)
- migrate content
- ???
- prophet
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/AnnArborRUserGroup/AnnArborRUserGroup.github.io/issues/34#issuecomment-316821081, or mute the thread https://github.com/notifications/unsubscribe-auth/AIOCqV7sgqx6QsV23psSHAhPPVk9DMziks5sP7j8gaJpZM4MaolN .
as for domain name cost, I almost bought one for AARUG when I bought mine the other week, but held off mostly because if there is a chance we merge into a larger groups with others, an AARUG-specific domain would become useless. So, I don't mind covering or splitting that cost either. Might make it real easy to just use netlify and be done with it.
@mooreaw I'm down to try the conversion route, unless it ends up being an overcomplicated mess at the end. Jekyll has a bit more complicated filestructure I think, and I don't want to force our old style into Hugo-world. Our current blog is kinda ugly too, so I definitely would prefer to avoid copying style elements over.
Because we don't actually have any Rmd's, we don't have to use blogdown at all, and could just use Hugo...but we are an R group, so doing it the R way feels like an appropriate level of dogfooding. Also gotta love making updates and seeing them in RStudio - that's the real killer feature.
oh wow, you're right-- they're all just markdown files (but yes, being able to edit and refresh in Rstudio is very satisfying)
On Thu, Jul 20, 2017 at 6:12 PM Clayton Yochum notifications@github.com wrote:
Because we don't actually have any Rmd's, we don't have to use blogdown at all, and could just use Hugo...but we are an R group, so doing it the R way feels like an appropriate level of dogfooding. Also gotta love making updates and seeing them in RStudio - that's the real killer feature.
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/AnnArborRUserGroup/AnnArborRUserGroup.github.io/issues/34#issuecomment-316844923, or mute the thread https://github.com/notifications/unsubscribe-auth/AIOCqVB7NLc9ac9RGxovcZKN5-KaugHoks5sP9DdgaJpZM4MaolN .
Because blogdown >>> jekyll?