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

Feature Request: Slug override #12

Open
ivuorinen opened this issue Jan 29, 2012 · 2 comments
Open

Feature Request: Slug override #12

ivuorinen opened this issue Jan 29, 2012 · 2 comments

Comments

@ivuorinen
Copy link

Possibility to override post slug (and destination).

For example IMDb movie reviews, you could specify "slug: /reviews/movies/0379217" for review of Coffee and Cigarettes -review on your site.

Other use cases: automatically generated entries, twitter timeline mirroring ("slug: /twitter/[tweet id]").
You could check if the output folder has the entry.

@marcoarment
Copy link
Owner

Interesting idea. Keep in mind that the way the document root is structured, the only ways to do this would be:

  • Add a Redirect to .htaccess for every custom slug, which is probably not a good idea.
  • Actually generate the folders and files to correspond to the custom slugs. So there would actually be a file in the document root at /reviews/movies/0379217, with all of the parent folders created as well.

I don't love either solution, but I guess the second would probably have fewer problems.

@ivuorinen
Copy link
Author

The second solution would be more like what I had in mind.

It would be important to be able to check does a specific entry exist. Wouldn't want to overwrite changes.
Current output naming scheme prevents reliable testing.

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

2 participants