Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring Jekyll for User and Project GitHub Pages #5

Open
wireddown opened this issue Aug 15, 2015 · 5 comments
Open

Configuring Jekyll for User and Project GitHub Pages #5

wireddown opened this issue Aug 15, 2015 · 5 comments
Assignees

Comments

@wireddown
Copy link
Owner

This is the comment thread for Configuring Jekyll for User and Project GitHub Pages.

@wireddown wireddown self-assigned this Aug 15, 2015
@darcemac
Copy link

Hi there,

Thanks for the detailed post on permalinks and the correct usage of url's. I wonder if you can help? I've got a client repo where the config files has been set to the latest jekyll 3 guidelines and recently when I updated the domain name to another host all of my blog posts get 404 messages, I have tried everything with no success!

For info the client repo is on the master branch of the user as I found this easiest and the post links use "href="{{ site.baseurl }}{{ post.url }}" and also href="{{ post.url }}" to test both.

I notice in your config file for this particular site, you have set permalinks true, isn't that against Github's recommendation?

Regards,
Darcy

@wireddown
Copy link
Owner Author

Hi @darcemac :-)

I notice in your config file for this particular site, you have set permalinks true, isn't that against Github's recommendation?

Yes, that setting is now against GitHub's recommendations. My to-do list has updating my site and posts for Jekyll 3 (which is the version that makes permalinks difficult/impossible on GitHub pages). At the moment, my posts do not apply to this new version of Jekyll pages.

I'm still willing to help/troubleshoot, though! Do you have an example of the failure you're encountering? I want to inspect the raw input as well as the rendered HTML output.

@darcemac
Copy link

Hi there,

Thanks for your response, appreciate it!!

I did try a few config settings even going back to jekyll 2.0 config settings. The issue was that I had this piece of code: "collections: null" and for some reason this breaks my jekyll posts.

Its all fixed now, again many thanks for your response and have a great day!

cheers,
Darcy

On 24/02/2016, at 2:54 PM, Down to the Wire [email protected] wrote:

Hi @darcemac :-)

I notice in your config file for this particular site, you have set permalinks true, isn't that against Github's recommendation?

Yes, that setting is now against GitHub's recommendations. My to-do list has updating my site and posts for Jekyll 3 (which is the version that makes permalinks difficult/impossible on GitHub pages). At the moment, my posts do not apply to this new version of Jekyll pages.

I'm still willing to help/troubleshoot, though! Do you have an example of the failure you're encountering? I want to inspect the raw input as well as the rendered HTML output.


Reply to this email directly or view it on GitHub.

@johnpitchko
Copy link

This was extremely useful as a Jekyll newbie seeking best practices. Thank you for posting.

@wireddown
Copy link
Owner Author

@darcemac wrote:
I notice in your config file for this particular site, you have set permalinks true, isn't that against Github's recommendation?

Yes, that setting is now against GitHub's recommendations. My to-do list has updating my site and posts for Jekyll 3 (which is the version that makes permalinks difficult/impossible on GitHub pages). At the moment, my posts do not apply to this new version of Jekyll pages.

I've finally updated my site for Jekyll 3 😅 See commit 33003da.

One very small clarification: permalinks are still supported by Jekyll 3.0 and github-pages; rather only relative permalinks were dropped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants