Tag Info

Hot answers tagged

4

Typically, user agents wouldn’t dereference these URIs. There should be absolutely no problem in using the Schema.org HTTP URIs on a HTTPS site. In fact, many other vocabularies (used for Microdata or RDFa) provide only HTTP URIs, so you have no choice there. I’d even say it’s bad practice to provide multiple vocabulary URIs for the same concept, as ...


2

Almost all feed readers will follow redirects when fetching feeds. You should be able modify your .htaccess file to redirect the old url to the new. Redirect 301 /feed http://carlboettiger.info/atom.xml


1

Two easy ways to fix this, depending on whether you want to customise just one blog post or make the change site-wide. For just one post, manually set its URL in the YAML front matter like so: --- permalink: /2013/11/10/mypost.html --- To change every post site-wide, you would edit your _config.yml to switch from the default 'date' permalink pattern you ...


1

It requires two things; Add a file called CNAME at the root of the project which only contains the domain name, see the docs In your DNS server, add an entry. This is done at your domain name service provider, or named/bind zone file Follow the instructions on setting up a custom domain with GitHub pages


1

Breno Salgado posted this simple Jekyll plugin on StackOverflow: ./_plugins/markdown_tag.rb: module Jekyll class MarkdownTag < Liquid::Tag def initialize(tag_name, text, tokens) super @text = text.strip end require "kramdown" def render(context) "#{Kramdown::Document.new(File.read(File.join(Dir.pwd, '_includes', ...


1

GitHub allows you to create a custom 404 page but there is a caveat. The 404 will be displayed only if you use a custom domain or for user pages. Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. A custom 404 page on project pages that are not using a custom ...


1

According to the GitHub documentation on custom 404s you are out of luck: Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. It looks like sub-folders are not supported. Only the root folder.


1

You should be fine if you use 301 redirects and update all the internal links. Several years ago, I moved my most popular page to its own sub-domain and then expanded it into an entire mini-site on that sub-domain. During that process, it continued to receive search engine referrals uninterrupted.


1

See Fork a repo / Clone your fork.



Only top voted, non community-wiki answers of a minimum length are eligible