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
Spina allows users to customize page parts because it heavily uses the attr_jsonjsonb data type component, which enables the storage of unstructured metadata. In that jsonb data column, any number of custom "page parts" can be stored and processed upon retrieval.
spina-blog stores its content in a more traditional database table with defined columns for content, image_id, excerpt text, etc. The limitation is that you can't add new types of data without creating new columns.
Have you considered making the Spina::Blog::Post type flexible in the way that Spina::Page is through attr_json? I'd like to add an additional type of metadata column for tags but can't do that without running my version of the gem as a fork.
Just wanting to know if such plans are in the works for possible collaboration.
The text was updated successfully, but these errors were encountered:
Spina allows users to customize page parts because it heavily uses the
attr_json
jsonb
data type component, which enables the storage of unstructured metadata. In thatjsonb
data column, any number of custom "page parts" can be stored and processed upon retrieval.spina-blog
stores its content in a more traditional database table with defined columns forcontent
,image_id
,excerpt
text, etc. The limitation is that you can't add new types of data without creating new columns.Have you considered making the
Spina::Blog::Post
type flexible in the way thatSpina::Page
is throughattr_json
? I'd like to add an additional type of metadata column for tags but can't do that without running my version of the gem as a fork.Just wanting to know if such plans are in the works for possible collaboration.
The text was updated successfully, but these errors were encountered: