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

Indexes for POSTS subfolders #1980

Closed
da2x opened this issue Aug 26, 2015 · 7 comments
Closed

Indexes for POSTS subfolders #1980

da2x opened this issue Aug 26, 2015 · 7 comments
Assignees

Comments

@da2x
Copy link
Contributor

da2x commented Aug 26, 2015

Generate indexes (default) or lists for subfolders of POSTS. Treat them as categories, deprecate existing categories (which are just tags) in v8/9 timeframe. No additional metadata is needed along with the post, but rather reflect output folder as set in POSTS.

The following options will be introduced:

POSTS_CATEGORIES = True
POSTS_CATEGORY_ARE_INDEXES = True
POSTS_CATEGORY_COLORS = { 'en': { 'pants': '#ff00ff' } }
POSTS_CATEGORY_DESCRIPTION = { 'en': { 'pants': 'Excellent pant selection' } }
POSTS_CATEGORY_FROM_META = False
POSTS_CATEGORY_NAMES = { 'en': { 'pants': 'Pants and Trousers' } }
POSTS_CATEGORY_TITLES = { 'en': { 'pants': 'Posts about Pants and Trousers' } }

In addition to the new category pages, each posts will be assigned with the following properties to facilitate category-oriented styling and functionality in templates and themes:

  • post.category_color()
  • post.category_link()
  • post.category_name()
  • post.category_slug()

Feature-creep: To facilitate automatic color assignment, an additional option will be added. I’ll also add a <meta content=#ff00ff name=theme-color> (consumed by many browsers and other systems). Ideally, this option will also be used to colorize themes based on user preference in the future.

THEME-COLOR = '#ff00ff'
@da2x da2x self-assigned this Aug 26, 2015
da2x added a commit that referenced this issue Aug 27, 2015
da2x added a commit that referenced this issue Aug 28, 2015
functions available in themes (Issue #1980)

Minor changes.
@da2x
Copy link
Contributor Author

da2x commented Aug 28, 2015

What I’ve actually implemented in pull request #1981 seem to be closer to sections than categories. WordPress calls sections for categories, which was what got me confused. What I wanted were sections and not categories. We can keep the old categories (even though they don’t make sense and just duplicates tags), and I could rename this feature SECTIONS.

@Kwpolska, @ralsina: thoughts? I’m fine with calling this feature categories as it does a more useful thing than the existing categories and the naming would be aligned with WordPress. But then we’d have to phase out the other category system sometime (v8). Or rename this section and go with naming comparable to TextPattern, MovableType, and news papers?

@ralsina
Copy link
Member

ralsina commented Aug 28, 2015

I like the name sections. Categories is very poorly defined in general (which is what brought us here into this particular mess :-) so a clean name with a clear meaning is awesome to me.

@Kwpolska
Copy link
Member

Let’s go with sections then, and categories will die in v8.

@da2x
Copy link
Contributor Author

da2x commented Aug 28, 2015

Sections it is.

@da2x
Copy link
Contributor Author

da2x commented Aug 28, 2015

Leaving the fallback name for sections as “Uncategorized” as “Unsectioned” sounds just silly.

@ralsina
Copy link
Member

ralsina commented Sep 2, 2015

@Aeyoun sections are implemented, right? Is there anything of this Issue left to do?

@da2x
Copy link
Contributor Author

da2x commented Sep 2, 2015

Nope.

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

3 participants