Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upConsider migrating to Jekyll for easy maintenance #5
Comments
This comment has been minimized.
This comment has been minimized.
Yep, and also from here: https://gupsych.github.io/acadweb/project.html What would the benefits of migrating the website be..? |
This comment has been minimized.
This comment has been minimized.
You don't change any HTML files directly, you merely edit the |
This comment has been minimized.
This comment has been minimized.
Ah, this is what I've been doing anyway, I think, simply in RStudio. Seems to be working okay.. :) |
This comment has been minimized.
This comment has been minimized.
@RaoOfPhysics just visiting this again now after way too long. I hope you're doing splendid! Do you think this is still something worth doing? Atm I can write the site content in markdown, and then just build the site in RStudio to create all the HTML files, and then push to make it all live online. Is Jekyll still worth looking into..? |
This comment has been minimized.
This comment has been minimized.
Doing well. :) Are you travelling? Yeah, I still think it's better to keep just the Markdown files under version control and let GitHub handle the generation of the HTML files via Jekyll. At the moment, if you go through your commit history, you effectively have a duplicate set of commits: Instead, you could have only Unless you're using any |
This comment has been minimized.
This comment has been minimized.
Gah, sorry for missing this @RaoOfPhysics. Yes, traveling a bit ;) OK, so, migrating to Jekyll. Reckon we should do this? :) |
This comment has been minimized.
This comment has been minimized.
Consider my knowledge of this to be close to, or less than, zero. |
This comment has been minimized.
This comment has been minimized.
I'd be up for it, but not in any reasonable time scale, unfortunately. How active is the website and when do you think you might want to work on the migration? |
This comment has been minimized.
This comment has been minimized.
Understandable. I just spoke about this with @msantolini and he agreed the migration would be a good idea too. The website is, er, variably active. I just updated it and you're now on it! https://meta-paleo.github.io/index.html Congrats on the citation ;) |
RaoOfPhysics commentedJun 3, 2018
Hey @Protohedgehog,
I'm guessing you used Rmarkdown to build the website using these instructions? http://nickstrayer.me/RMarkdown_Sites_tutorial/
Perhaps you would consider migrating the website to Jekyll instead, given that it works closely with GitHub pages: https://help.github.com/articles/using-jekyll-as-a-static-site-generator-with-github-pages/
It's really easy to set up -- I'm happy to help! -- and you don't need any special software on your end to work with it. If you do want to test the website before you push it to GitHub, you can install Jekyll locally, but in theory you can work directly (and only!) with
.md
files for all your content. Jekyll also simplifies any changes people want to make to your website, as they can edit the Markdown files straight in GitHub and you can merge it without anyone having to runRmarkdown::render_site()
from R.Just a thought. Let me know if you think it's worth doing and if you would like my help. :)