One of the urls for my page is:
http://blog.theofekfoundation.org/general%20computer%20programming/2015/12/30/2d-array-copy-speeds.html
(note the %20s)
While the jekyll sitemap entry is:
<loc>
http://blog.theofekfoundation.org/general%2520computer%2520programming/2015/12/30/2d-array-copy-speeds.html
</loc> # Note the %2520s
I added the sitemap using github's sitemap gem:
gems:
- jekyll-sitemap
in my _config.yml.
Any idea what's going wrong or how to fix it?
At the moment, jekyll-sitemap always encode the URLs and is not smart enough to detect that the URL already contains encoded text, which is causing it to encode the % character (hence the %25).
You can open an issue on the jekyll-sitemap repository, and see if there are any plans to improve this story.
However, if that is an option, I would recommend you to not use spaces, and instead use a dash -, which is more user-friendly and easier to read... With the added benefit that it doesn't break the sitemap.
Also, get rid of the .html at the end.
e.g.
http://blog.theofekfoundation.org/general-computer-programming/2015/12/30/2d-array-copy-speeds/
Related
I'm attempting to create a badge using shields.io for a GitHub project I'm involved in. Shields.io allows you to add your logo with base-64 encoding. Pretty cool, however it's pretty unwieldy to place into your readme. Given that I want to make it convenient for associated projects to paste our badge into their project, I don't want the markdown to be ten lines long.
I've noticed that not everyone has this problem. Gitter, for example has a very simple url for its shield that contains a logo.
Bithound also has a very nice badge url.
Are these special deals that they've worked out with Shields.io? Or is this sort of slickness available to everyone?
Shields.io has default support for a number of vendors displayed on the front page. Some of those custom integrations rely on corresponding logos: https://github.com/badges/shields/tree/master/logo.
I understand how having a large URL can be inconvenient. However, referencing external resources in images can yield unfortunate results, and is therefore disallowed (as does GitHub, which has had its share of sneaky DDoSes in the past years).
However, I believe using a URL shortener like bit.ly or goo.gl can help you have small URLs in your project files.
Folks, help is needed and MUCH appreciated with a fuzzy behaviour of Jekyll site deployed to Github.
The site works perfectly when putting it up and using it in the local machine (through 'jekyll serve'). The surprise came up upon deployment to Github, the HTML 'posts.html' page created to show the post list does not get rendered at all. The rest of the site is up and running fine, but once the link is clicked to reach the mentioned page the browser is trying to DOWNLOAD the file, instead of rendering.
If you need to have a peek at the code:
https://github.com/zekdeluca/zekdeluca.github.io
And the site can be seen at:
http://zekdeluca.github.io/
Thanks in advance!
It has to do with the permalink and how the extension-less urls are working. If you add a trailing slash to your url it will work. If you are trying to do it without the trailing slash, I was under the impression that what you did would work on GH.
Something like permalink: /my-page/ will work and it creates a folder called my-page with an index.html file in it. The url will show as /my-page/ without the index.html - pretty except the trailing slash.
If you do permalink: /my-page it should be making a file my-page.html, but in your case it seemed to have made just my-page with no extension, which is then being served as a file by github and it doesn't seem to know what it is so it is downloading it instead of serving it.
There seems to be a lot of conflicting info on this, I think the behavior has changed recently, and maybe the version GH is using is able to output a file with no extension? I did not think that was the case.
more reading:
http://overengineer.net/pretty-extensionless-urls-in-github-pages-using-jekyll/
Jekyll extension-less permalinks with markdown
I'd like to use Jekyll for my website, but I can't figure out how to set it up. All of the documentation I've seen shows how to use Jekyll to set up a blog. I just want to write Markdown and have Jekyll convert it to a website.
I understand that this question is a bit vague and the terminology may not be perfectly accurate. I'm new to creating a website and I don't want to learn HTML.
(Disclosure: My website will be for a project on GitHub.)
There's four types of document that you can find in a Jekyll site :
Static files like js, css or even html page. They don't have a front matter, are simply copied at generation time and can be found in the site.static_files hash,
posts they are located in _posts folder, have a front matter and can be found in the site.posts hash by liquid,
pages they can be anywhere in your folder structure, have a front matter and can be found in the site.pages hash by liquid,
collections that are more elaborated pieces of datas with a front matter and can be found in site.collections hash by liquid.
You can choose to use any of them. If you don't want to use posts, just remove or empty the _posts folder and just use pages.
If all you want to do is write markdown and have that generate a single page for a project, consider using the GH-pages automatic generator.
In step 3 you write the content for your page in Github-flavoured Markdown and then select a layout to publish it in.
I am using the free version of Google Custom Search. The 2-page version.
They gave me 1 javascript for the search box, and one for the search results page.
It seems fine, except that spaces in the request get converted to %2520 instead of %20, which leads to 0 results.
If I write my OWN simple HTML form that points to the result page, it works fine (it uses '+' for spaces).
I had a similar issue.
It was found that the url was rewritten to another one which resulted in extra encoding of the query term.
In my case, www.sub.domain.com/?q=some text was redirected (301) to sub.domain.com/?q=some%2520text
It was an error in usage. The link should not have contained 'www' for a sub domain.
Avoiding the redirection fixed the issue. Check if your query link is getting rewritten/redirected.
I've got a gist which contains a markdown file and an image.
Is there a way to do a relative link to this image?
Something like  instead of 
Here is an example
As of now, relative image links are working for me, in both a repository and a wiki. I'm using syntax like this:
Here's an example:
https://github.com/mark-anders/relative-image-url
According to http://blog.rodneyrehm.de/archives/35-Including-Data-From-Github.html, the problem in using
https://gist.github.com/user/605560c2961cb3025038/raw/b75d2...6e8/img.png
is that the b75d2...6e8 part varies per file (a quick experimentation confirms it is the git blob id). However you can drop that part resulting in a URL pointing to the latest version:
https://gist.github.com/user/605560c2961cb3025038/raw/img.png
or to take a working example:
https://gist.githubusercontent.com/cben/46d9536baacb7c5d196c/raw/dodgetocat_v2.png
Relative path?
This also works as relative path raw/dodgetocat_v2.png!
However (as of late 2017) github can render the same gist from 2 URLs:
When viewed from https://gist.github.com/cben/46d9536baacb7c5d196c/ (with trailing slash), the relative path is appended, resolves to https://gist.github.com/cben/46d9536baacb7c5d196c/raw/dodgetocat_v2.png — works :-)
When viewed from https://gist.github.com/cben/46d9536baacb7c5d196c (no trailing slash), the relative path replaces the last part of the URL, resolves to https://gist.github.com/cben/raw/dodgetocat_v2.png — broken :-(
[UPDATED Dec 2017. Previous problems of raw files served as Content-Type: application/octet-stream and rewriting src attributes of images to camo.githubusercontent.com no longer happen, at least not for images from same gist.]
Alas, we can't just use the first URL and trust it to always work.
Currently neither form returns a redirect, nor serves a rel=canonical link. I wouldn't bet on Github to never change this!
All internal gist links (e.g. from user's page https://gist.github.com/cben/) omit the trailing slash :-(
Gists in Google search results omit the trailing slash :-(
(You could use relative path 46d9536baacb7c5d196c/raw/dodgetocat_v2.png that would only work without trailing slash, but that's also questionable idea, and less worth it — not really more flexible than full URL.)
Using a proxy?
Both can be worked around with a proxy fixing the Content-Type, e.g. Rawgit or Bl.ocks.org (not by Github, don't abuse them). Unfortunately Rawgit doesn't render Markdown, only serves files as-is, and Bl.ocks.org does render markdown but the URL structure is such that relative links won't work. This means you can either reference full external URL in Markdown, or relative in HTML :-(
See https://gist.github.com/cben/46d9536baacb7c5d196c/ forked off your gist,
and its index.html viewed via:
http://rawgit.com/cben/46d9536baacb7c5d196c/raw/index.html
http://rawgit.com/cben/46d9536baacb7c5d196c/raw/
http://bl.ocks.org/cben/raw/46d9536baacb7c5d196c
http://bl.ocks.org/cben/46d9536baacb7c5d196c
Yes, the relative link is working for me. I am using pancake.io to host my pages.
http://pancake.io/2c8aa8/topics/cpp/cpp.md
The images on that page are in the cpp folder.
The markdown code used for the first image is
The markdown code (actually html) used for the second image is
<div style='float: center'>
<img style='width: 600px' src="prefixpostfixincrement.png"></img>
</div>
NOTE: I missed the gist part. Try the html way if gist doesn't support the markdown relative image path syntax.
tested just now...
i was unable to use relative urls on the github wiki.
i had to add the image to the wiki repo, then browser the repo and have github show it to me (so i could grab the url). then use the full url in the markdown. but luckily, the urls are simple to predict: https://github.com/*username*/*reponame*/wiki/*imagename.png*
i submitted this isse to the github support.
No, the relative URL to an image from markdown doesn’t work, so you’ll have to stick with the long, static URL:
https://gist.github.com/mattborn/c346c8689a5eaf86e823
However, relative URLs to some files work:
http://bl.ocks.org/mattborn/c346c8689a5eaf86e823
After scratching my head around this for good 15 minutes I realized:
Relative paths to images do work, but when you're writing a markdown file directly from the github web app, the images don't show up in preview. Once you commit the file the images are visible as expected