Was the Jekyll home page made with Jekyll? And if so what theme did they use and is it publicly available.
I recently noticed that the site dev assets looks very similar to the Jekyll home page and uses Jekyll, however while looking through the source I could not find the name of the theme in any of the config files.
Thanks in advance for any help.
I went through the docs/ directory of the jekyll repository. They're definitely using Jekyll. In _sass/, only two files are not original:
_gridism.scss, GitHub Repo: gridism
_normalize.scss, GitHub Repo: normalize.css
All the rest are essentially original, as in the developers of the website made the theme themselves.
Related
I want to upload a small website I did using pure JS and some SASS to Github pages.
Now that I uploaded I realized Github pages will not precompile SASS on its own, so I was wondering how could I precompile the SASS file through Github pages.
The simplest way will be to precompile the SASS. Just an example site, input your code here and it will spit out css code for you to put in the files and then you rename them to (whatever).css.
https://beautifytools.com/sass-compiler.php
You could also look into a PHP compiler to compile on-the-fly if it needs to be updated dynamically. This will not work with Github pages though.
I've been using the Emerald jekyll theme for my blog on GitHub Pages. It all works great on GitHub, but I've wanted to move to GitLab.
I got the blog working with all necessary gems (like jekyll and jekyll-paginate), but the blog posts aren't working and I get 404.
Test it live here
I made the repo public so everyone can have a look and possibly identify my problem.
Just add a .html extension to your links.
https://remieditor.gitlab.io/blog/plausible-gitlab-moving.html
Github provides an option for serving without the extension, however I don't believe that Gitlab allows this yet. See this thread: https://gitlab.com/gitlab-org/gitlab-pages/issues/95
Change your permalink configuration:
permalink: /:title:output_ext
Since GitLab 11.8 (February 2019) this should work
.html extensions are now automatically resolved for Pages sites
A file in your Pages site called /sub-page.html can now also be accessed as /sub-page, giving you more options over how your site appears to your users.
See documentation and gitlab-org/gitlab-pages issue 95
I am trying to use Jekyll to build my portfolio site which is hosted through Github Pages. However, after going through the setup process and watching some tutorials this is what I have in my project folder:
As you'll notice, it seems to be missing some important folder such as _layouts, but it also seems to be working fine. What am I missing here?
The tutorials or docs you saw may be missing gem themes, Jekyll 3.2.0 introduced gem based themes: By default you won't have these typical directories:
/assets
/_layouts
/_includes
/_sass
But you can always overwrite them or copy to your jekyll instance to modify them.
I'd like to start designing a website using Jekyll or Hugo. The plan is to publish it on GitHub or GitLab pages.
After hours of searching I'm pretty confused about all the facts. Hugo support natively a multilanguage utility while Jekyll not. There are some plugins for Jekyll but plugins are not supported on GitHub pages anyway.
With Jekyll I tried to follow this solution without any concrete solution for the translation of the layouts while with Hugo I've found the instruction pretty confused (but that's my fault).
What I'm looking for is a theme (Jekyll or Hugo it doesn't matter) that is already designed with 2 (or more) languages.
Beside the official Hugo instructions for creating a multilingual site, you also have:
multilingual examples which has been recently updated
multilingual mode
themes with multilingual already baked in as (from the Hugo themes list site):
hugo-scriptor-theme
dimension
docuapi
Plus, with Hugo 0.87 (Aug. 2021), you also have Date/time formatting layouts and localized string for the current language.
As well as the themes that VonC linked to, there is the Beautiful Hugo theme which I recently updated to work with multilingual sites.
I also recently made an example of a multilingual Hugo site in hugo-multilingual-example at Github, so you can compare that with the example in the Hugo repository that VonC linked to.
With Hugo, you should ignore the "Create a Multilingual Site" tutorial, as it was made before the native multilingual support was added, and is now outdated. Instead, you should base everything on the "multilingual mode" documentation.
Hopefully that should be enough to get you started, but let us know if you have any other problems.
I localized a Jekyll theme to output to German and Japanese here. It depends what requirements you're trying to support. We sent out translated files to a translation agency and then reimported them back into the project.
My strategy in defining the theme was to put each language in its own collection. Each collection defines default values for top nav and footer to be in that language.
Additionally, I used a different config file for each language. The language's config file defined strings for that language. File names and URLs remained in English.
I created a middleman blog using this tutorial and documentation. Since I had an older blog, I copied few of my posts and pasted into source folder.
Now when I start server, I don't see any of my posts. Can someone help me with this?
Latest code is hosted on github-pages.
Resolved this one by moving my posts to source/blog folder.
My config.rb I had following set up as -
blog.prefix = "blog"
Hence, it was looking into blog folder for articles. Moving them resolved my issue.