I'm trying to set up a blog via Jekyll and GitHub Pages. To deploy it was not such a big deal, however, in trying to follow the steps described here I only managed to make it display the dark skin locally. Is there a way to deploy it on GithubPages as well?
I installed it via
gem "minima", git: "https://github.com/jekyll/minima"
then added the following two lines in _config.yml
minima:
skin: dark
This is the repo holding the ruby code.
i had this problem too. I learned that the software used by github pages isn’t updated often, hopefully for stability reasoning. You can check what versions they use at https://pages.github.com/versions/. The newer version of minima has the alternative “skins” sass/css feature, but the one currently on github pages doesn’t—-heck, github pages still hasn’t updated Jekyll to v4!!... You should be able to see the build error by clicking Actions on the github repo, then clicking on the last “workflow”, then click on the red-colored build. It’ll say the key in the config file doesn’t exist or somethin’ like that, on the skin: dark line.
anyway, in the config file, add remote_theme: jekyll/minima to force download the latest version from the github repo upon rebuild. Don’t use ~jekyll-theme: minima (or whatever it’s called). In fact, at the moment, all of the themes that come pre-installed with github pages are quite old now...
but really though, use the jekyll discussion site https://talk.jekyllrb.com/.
I was using Chrome, and apparently the Clear browsing data in the last hour with Cookies and other site data and Cached images and files checked made the local updates appear live.
You can go even further and make your jekyll/minima powered site respect users theme preference
https://alexander-taran.github.io/2022/06/08/adopting-dark-theme-in-jekyll-blog.html
Related
I'm setting up a personal website on GitHub Pages using Jekyll. I'm using the Cayman theme. I used this documentation to override some of the theme's defaults. The documentation said:
making copies of theme files will prevent you from receiving any theme updates on those files.
I'm OK with not receiving feature updates but I'm not OK with missing out on security updates. Do Jekyll themes ever receive security updates? A Google search didn't turn up anything helpful.
I don't think they do (since a Jekyll site is a static site) but I would like some input/confirmation from someone more knowledgable than myself.
I am working on an app that creates automatic blog HTML pages using JSON and also has to provide versioning for that blog.
Creating HTML using JSON files
Creating a GIT tag whenever User creates a version.
If the user wanted to see the previous version of that blog I am simply checking out that file to given tag and fetch the file and again creating HTML using that JSON file.
Questions
Is it right to use GIT for the above purpose?
If yes, Are there any precautions that I have to take?
If no, Is there any alternatives for saving the previous version of a file except saving each file for each version?
Note: I am using Node.js for creating GIT tags and checkout to tags
You should use git for every project, ask if it's right only if you have a ton of binary files.
I've seen people use git for content writing and articles, remember it is an efficient version control systems and as long as you wish to have past versions of your project( you always should), you should use git.
even if you are not pushing to a remote repository, it's better to have some VCS implemented in all your projects.
I host a personal website using GitHub pages and I manage the process of changing and improving the site using Git.
My process is to make changes in a 'development' branch and push these to master.
I believe this is a standard process, but my question is:
Is there a way of seeing how the website changes before going through all the steps to merge with master? Or can I see and test this change earlier on, say in a test environment?
I have been trying to find an answer to this question for some time.
The closest I have got to an answer is here:
Can I run HTML files directly from GitHub, instead of just viewing their source?
However when using http://rawgit.com an index.md file only shows as markdown and when using http://htmlpreview.github.io/ all the markdown text appears bunched together. In both cases I can't see any styling as the website is structured using links to external styling sheets and Jekyll front matter.
How can I solve this and view the page as it is supposed to appear?
While your pages are hosted on GitHub, they are rendered differently depending on your GitHub pages settings.
If you are using Jekyll as a static site generator with GitHub Pages, you can then setup your GitHub Pages site locally with Jekyll.
The idea remain to check your pages before pushing to GitHub.
In my project, http://lacinia.readthedocs.io/en/latest/, the downloads (PDF, epub, single-page HTML) doesn't update on a build. It looks like it builds, but the download link keeps downloading a version from Oct 03. I've done some significant work since then.
The latest link works correctly, showing changes within minutes of my pushing changes.
It's not clear to me whether the build works, but the latest files are simply not put in the correct folder for download, or if the build is broken in some way.
I'd appreciate any clues on how to fix or at least properly diagnose this.
Digging around, I found the "wipe build" functionality; that plus, perhaps, a Cmd-Shift-R, to ensure I was downloading fresh and not from local cache, got me the latest versions.
I found this site that has a link to a .Net project.
The link is to a folder structure.
How do I down load this project without SVN??
Is it specific SVN??
http://svn2.assembla.com/svn/nbdn_web_store/
Source Code
I would say that either you install svn (which is not a huge install), or you have a lot of clicking to do when you download each file separately using your web browser. Can't see any other alternatives, really.
install subversion and check out the file with e.g. the command
svn co http://svn2.assembla.com/svn/nbdn_web_store/trunk/ ndbn_web_store
First of all, I agree that installing svn is a good option.
If you don't want to do that (and don't like clicking tons of links to download each file) you can use an offline browser such as this one recommended by CNET