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
{{ message }}
This repository has been archived by the owner on Nov 24, 2021. It is now read-only.
The current Blog shipping with keystone is very basic. In order to make it a viable alternative to that one popular platform (which shall not be named), the features of the default blog need to be expanded.
Proposed new features:
Search
Tags
Archive
Author Biography/Profile
Comments
Statistics Counters
Considerations:
Generating Statistics and Computing a list of available tags on the front end would hinder performance. In the case of tags, we can use a simple model to store this data with schema.post('save') hooks on our models that will affect said lists. in this way we move the perf hit to place where the change occurs, keeping the front end light. statistics counters, such as the number of views and number of comments can reside right on the Post model and be updated as changes occur vary easily.
here is the proposed model i would use to store any aggregate data. really its just a list of string arrays. super duper easy and flexible:
In my opinion to keep this model flexible it would be advantageous to use slugs instead of relationships.
As you might imagine, i've already got most of the code for this, including the templates for twig. We would need some help on the templates for : nunjucks, handlebars, and possibly jade. Any other help, comments or ideas is greatly appreciated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current Blog shipping with keystone is very basic. In order to make it a viable alternative to that one popular platform (which shall not be named), the features of the default blog need to be expanded.
Proposed new features:
Considerations:
Generating Statistics and Computing a list of available tags on the front end would hinder performance. In the case of tags, we can use a simple model to store this data with
schema.post('save')
hooks on our models that will affect said lists. in this way we move the perf hit to place where the change occurs, keeping the front end light. statistics counters, such as the number of views and number of comments can reside right on the Post model and be updated as changes occur vary easily.here is the proposed model i would use to store any aggregate data. really its just a list of string arrays. super duper easy and flexible:
Notice the usage of slugs here. the slugs are used to retrieve the list. for example, to retrieve the list of all tags:
In my opinion to keep this model flexible it would be advantageous to use slugs instead of relationships.
As you might imagine, i've already got most of the code for this, including the templates for twig. We would need some help on the templates for : nunjucks, handlebars, and possibly jade. Any other help, comments or ideas is greatly appreciated.
The text was updated successfully, but these errors were encountered: