fokimarket.blogg.se

1. #Rmarkdown github pages section url link how to
2. #Rmarkdown github pages section url link update
3. #Rmarkdown github pages section url link software

Now, the theme is no longer redundantly tracked in my website repo, and every time I want to update the theme, I can use git submodule update and get any security updates taken care of as well. Run git config -global diff.ignoreSubmodules dirty per this Stack Overflow post to get git to ignore all “dirty” untracked submodule folders (because they’re actually perfectly fine and accounted for).This would protect against double-uploading the submodule files to my GitHub repo. Run git rm -cached -r themes/hugo-theme-terminal in a terminal window to stop git-tracking (“delete” in git’s eyes) the folder that is now submodule-linked.Delete the old version of the folder, leaving only the new submodule version of the folder.When I was ready to delete the old (temporarily renamed) version of the theme folder, I had to do a couple things to get git to cooperate:

I renamed the old theme folder to remove name conflicts with the incoming updated theme, and then git submodule add-ed the hugo-theme-terminal repo into my themes folder. Too many GitHub Dependabot updates that went over my head! I decided to sync back on to Radek’s updated theme repo using a git submodule for the theme instead.

#Rmarkdown github pages section url link software

However, I eventually realized that it was too bothersome to try to keep the theme dependency software updated (turns out I don’t fully understand all the front-end code that Radek uses to render the aesthetics!). I figured this would let me make the theme edits I wanted without accidentally harming the upstream theme, or getting overwritten if I kept the theme as a git submodule and updated the theme regularly.

#Rmarkdown github pages section url link how to

When I first set this website up, I didn’t know how to override default theme layouts without editing in the theme folder itself, so I grabbed a static copy of the theme folder from GitHub. Overriding one or two layouts of a git submodule theme Predictably, I never finished writing up this post until months later.Īnyway, here it is! I will describe tidbits I learned (and am still learning) in the process of setting this site up that might help you if you find yourself plumbing the blogdown waters in the future. That way, anyone else setting up a blogdown site running into similar problems might be able to refer to my experience and save themselves some trouble. In case others might want to read my R Markdown ramblings, I want to put them online!Īfter a couple days of not insignificant headache, I got the website up and (mostly) running! At the time, while it was fresh in my mind, I meant to immediately publish a summary of all of the website setup headaches. I’m happy to trade in a less impressive theme for blog post compatibility with R Markdown. I’d been thinking of moving to a self-maintained static site for a while, especially one that would easily let me post R Markdown blog posts to the internet. Further, I hadn’t integrated my Squarespace site with any blogging tools, so I wasn’t able to have much regularly updated content beyond adding things onto the CV section of my About Me page. Squarespace is incredibly powerful if you want more sophisticated site features (floating navbars, clicking and dragging to set up complex text box layouts, etc), but I always felt that it was a bit overkill feature-wise (and subscription-wise) for an aesthetically pleasing, yet ultimately information-light website. My previous personal website was through Squarespace. I decided the most useful thing I could handle doing with my day inside was scratching a (hopefully) fun technical to-do off of my list would be moving my personal website over to blogdown.

Prism.js, and the mysterious case of pre vs code classesĪbout two weeks into (the first) CoVID-19 lockdown, my social distancing brain was starting to feel quite out of sorts.Pointing Squarespace DNS to GitHub Pages URL.Re-pointing my old Squarespace domain name.Setting public as the GitHub Pages root directory.Understanding Hugo’s expected structure.Overriding one or two layouts of a git submodule theme.Blogdown-ing with a different Hugo theme.