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

Post title for display vs for URL? #100

Open
protobi opened this issue Jul 15, 2014 · 3 comments
Open

Post title for display vs for URL? #100

protobi opened this issue Jul 15, 2014 · 3 comments

Comments

@protobi
Copy link

protobi commented Jul 15, 2014

Crossposting here from StackOverflow. New to Poet, the post title is not behaving as I'd expect from the example.

I expect that if a post were in the file hello.md and had the configuration {{{ title: 'hello-world', ...}}} that this would be available at the route http://hostname/post/hello and have the display render the title to the reader as <h1>hello-world</h1>. That's the way it seems to be working in the reference blog, e.g.:

However, in my case it seems to be using the title attribute for both the URL and the display string. In my case, the post is accessible only at http://hostname/posts/hello-world and the page title is also rendered as <h1>hello-world</h1>.

What might I be doing wrong?

@jsantell
Copy link
Owner

The url is generated from either the slug property, or the title, updated in 73712ba from back in January in 1.0.0rc4 -- so that'll fix the issue (so there's no coupling with filename and url). Leaving this open to update the docs

@protobi
Copy link
Author

protobi commented Jul 15, 2014

Perfect, thanks so much! The aha for me:

  • Can set set { "title": "this is the title I want!", "slug": "this-is-the-slug-i-want", ...}
  • The default rule is to convert spaces to dashes, and remove any non-alphanumerics,

So without the slug property, the slug would be "this-is-the-title-I-want"

@jsantell
Copy link
Owner

Hmm it should also convert to lowercase, I'll make a separate bug for that -- thanks for the report!

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

No branches or pull requests

1 participant