Related Posts affected by files all saved with -title slug

[randomecho]

On a page such as Material Organization Refactoring the Related Posts section only has one working link.

The others all point to:

http://teach.github.com/articles/title

Looks like fallout from posts using the same -title slug end like:

0002-01-01-title.md

Where otherwise it would benefit with a unique slug to help create the hyperlinks.

0002-01-01-pull-vs-fetch.md

[matthewmccullough]

You are so right. I'll try to hit those up along with some @github/training-team members.

[matthewmccullough]

There are still a few more slide to rename.

[matthewmccullough]

@jordanmccullough I think I need some help here to filter out slides from appearing in the recommended links, if there's even a way to do that.

[jordanmccullough]

Did some hacking on this yesterday, and hit a blocker with some Jekyll weirdness. Might need to chat with an expert in Liquid and Jekyll to resolve.

[matthewmccullough]

Calling an awesome @cobyism for Jekyll help. @jordanmccullough can you recap for Coby what the barrier is here in a nutshell?

[cobyism]

@jordanmccullough Happy to try and help 😀 —what kind of stuff did you run into, exactly?

[jordanmccullough]

@cobyism, thank for offering to help.

For the teach.github.com "presentations" slide deck HTML files, we've put a front matter of categories: ['presentations']. With the /presentations/index.md using the Jekyll include categorycontents, we're seeing all _posts included in the output, not just the Markdown files with the category presentations front matter.

Clearly I'm totally overlooking something here, but any insight would be appreciated.

[cobyism]

@jordanmccullough Ok, I’m pretty sure I know why you’re seeing this.

The way Jekyll works is that categories are derived from the directory structure above the _posts directory. For example, a post located at /work/code/_posts/2008-12-24-closures.textile would have this field automatically set to ['work', 'code'] (without setting it in the YAML front-matter. They can also be specified in the front-matter, but the inheritance from the directory structure is likely what is causing your problem here.

Basically, because you have a _posts directory underneath a /presentations directory, this means any markdown file in that /presentations/_posts folder will inherit a categories value of ['presentations'] whether you specify it in the YAML front-matter or not.

There’s a couple of ways you could get around this:

1. Alter the directory structure so the inherited category and the YAML-specified category are not the same.
2. Alter the YAML-specified category to be different from the directory-inherited category name.
3. Add a secondary, arbitrary category name to the YAML front-matter for posts you want to show up, and make that the one you specify in the {% assign selectedcategory = ... %} line of index.md.

I’d probably recommend option 2, with changing the YAML-specified category to maybe be just ['presentation'] (no 's', singular) since that’s what that specific file represents so it makes a little bit of sense—or possibly option 3. Option 1 would suck because it would necessarily affect the URL structure, and I’m guessing that’s not ideal.

I hope that helps you troubleshoot? Let me know if there’s anything I can do (or clarify further) to help get things working as you want them to and I can have a dig 😄

[brntbeer]

Link to #66 as a related issue.

[jordanmccullough]

@brntbeer Thanks for associating these two issues. Looking into these and should have word on them tomorrow (03/13/13).

[jordanmccullough]

Almost done with a major refactor. All markdown files will have the title embedded, no Front Matter "title" attribute requirement, etc. The HydeSlides control panel will now show like so...

[brntbeer]

This is so awesome. happy to see progress updates!

[cobyism]

Woah, nice!