-
Notifications
You must be signed in to change notification settings - Fork 450
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
Comments
functions available in themes (Issue #1980) Minor changes.
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? |
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. |
Let’s go with sections then, and categories will die in v8. |
Sections it is. |
Leaving the fallback name for sections as “Uncategorized” as “Unsectioned” sounds just silly. |
@Aeyoun sections are implemented, right? Is there anything of this Issue left to do? |
Nope. |
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:
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:
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.The text was updated successfully, but these errors were encountered: