currently: researching a ton of cms offerings.
-
currently: researching a ton of cms offerings. and i mean a ton.
-
@trwnh please post what you find out!
-
@tech_himbo my main takeaway is that wow pretty much everything is a paid premium offering. but i am looking at Keystone/Keystatic for now. but also there is a potential future timeline in which i write my own CMS-like thing based on foundational theory and principles. mostly i am not super happy with what currently exists as-is that is freely available
-
in researching content management theory a lot of talk seems to focus on defining schemas and relations. the prevailing model seems to be putting objects into collections, but the assumption seems to be that all collection-items have the same schema/type. so for example you might have a collection of Articles and one for Images. i’m not sure i like this fully. of course it is possible to make collections like Blog and Docs, but you can do that with taxonomies too…
-
something like a stream or feed would be a taxonomy, that much i can agree with. taxonomies don’t have to contain the same type of content. but i’m kind of questioning how useful it is to mentally organize things into types. i guess it makes sense if the type never changes, but as we know with text content, you have things like Note and Article and no immediately obvious distinction between them. it is possible that a Note later becomes an Article, no?
-
we have to think about the nature of identity here. when you take a Note and refine it into an Article, is it still the same content piece? should our content model allow for that?
i guess it depends on how you define types like Article, but in an http web sense, you should be able to publish it at the same URI and that in effect makes it the “same thing”. so how do we model this? say a life cycle of some content piece as it starts off as unrefined Note and then later becomes a Page or Article
-
part of identity is usually the slug, and choosing an easy-to-mentally-map slug is a philosophy in itself. (i currently try to make the first term of the slug be the primary subject or topic of the content piece, then follow up with other words to more specifically describe the piece)
but to me, my brain wants to qualify that slug with a category first. so i have a hugo section for /monologues and another for /theorycrafting, but this could just as well be a taxonomy instead…
-
really when defining types of content, i think the two i would be most likely to deal with are:
- chronology-based like a blog
- topic-based like an encyclopediabut that doesn’t seem like a clean enough distinction on its own. where do generic informational pages fit in? and for chronological stuff, the chronology of it is often not the most relevant factor (like, i don’t generally remember if i wrote a post in 2018 or 2019). so i need to figure out something better…
-
i guess that means i have to consider:
- chronology-based (“post”, but be more strict about what fits here)
- subject-based (wiki, kb?)
- purpose-based (give info, maybe lead to a cta?)there’s definitely other aspects i could consider but i can’t come up with them rn, having a bit of a mental block
