Split page and articles ? #37
Labels
No labels
Compat
Breaking
Domain
admin
Domain
content
Domain
plugin
Domain
sidebar
Domain
themes
Kind
Bug
Kind
Dev Experience
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#44 Support repost/reshare}
kazhnuz/koblog
Reference: kazhnuz/koblog#37
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would allow for a better admin UI
an article objecta new PageType metadata where we can have "static" or "articles"Make article have as URI /articles/{{article-name}}(nope)Add a redirect for articles that use the old URI if "converted-from-bludit" is true(compat) Make all page in "static" mode when created with the editorThe downside is that it could add a small performance hit for converted site that want to keep their redirections.
The "conversion path" should be a separate php file.
The biggest question is the new/edit UI that'll to change some stuff, but will be 99% identical (but that won't handle tags, category, publication mode, etc)
Maybe only split them in the UI, and keep them related internally ? It would avoid bug and keep backward compatibility, but also won't allow performance by only searching for article when they're relevant.
Another possibility is a system of posts/pages-types that would allow some features or not, CMS-builder likes. We add a "pageType". It would allow configuring if it use category, if it use systems, etc.
( Events and Notes will have a separate system still )
A MVP could simply have PostKind but not customisable