You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ABlog uses the path to the source file for blog post permalinks, similar to any other Sphinx page. It is a common practice in the blogging world to instead have a user-defined permalink structure (e.g. /:year/:month/:day/:filename). This allows you to organize your local filesystem without requiring you to use the same URL link structure (e.g. many blogs are now only using the page title in the URL instead of adding date-based subfolders).
Proposed solution
ABlog could provide a configuration option like ablog_permalink_structure, which would take a string with a few keyword arguments that were supported. E.g.:
year
month
day
category
slug
And so the value could be something like:
# Month and year-based pagesablog_permalink_structure="{year}/{month}/{slug}"# Just the slugablog_permalink_structure="{slug}"# Would error because the variable doesn't existablog_permalink_structure="{year}/{foo}/{slug}"
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently,
ABlog
uses the path to the source file for blog post permalinks, similar to any other Sphinx page. It is a common practice in the blogging world to instead have a user-defined permalink structure (e.g./:year/:month/:day/:filename
). This allows you to organize your local filesystem without requiring you to use the same URL link structure (e.g. many blogs are now only using the page title in the URL instead of adding date-based subfolders).Proposed solution
ABlog could provide a configuration option like
ablog_permalink_structure
, which would take a string with a few keyword arguments that were supported. E.g.:year
month
day
category
slug
And so the value could be something like:
The text was updated successfully, but these errors were encountered: