Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for content as modules #5973
A Hugo Component can currently provide this:
A quick and naive approach would be to add
It would, however, obviously be great if I as an enterprise documentation project owner could compose my content from versioned "content components" (partitioned by language or some other topic) so I could say:
There are some obvious missing pieces in the above (language, mapping to some section etc. and all the things coming in #5074 ).
This is crazy. I have been thinking about the exact same thing this afternoon, but you beat me to it!
What I would like is to let a content provider just write content (no frontmatter) in a file hierarchy, for example in a markdown editor, i.e no technical stuff at all. Commit to git and thats it. Yeah, that’s more to it, but maybe it fits with the issue about getting content from other endpoints. (Now I seen you mentioned that issue above #5074)
I don’t think content should be a theme component but an own module type (as you also seem to think). This separates content from site and theme in a nice way.
referenced this issue
May 19, 2019
@zivbk1 yes, I actually stumbled upon a YouTube presentation on Antora some days ago (but probably after I created this particular issue ... :-).
I think the big difference between this and that is that this is a versioned graph. Playbook looks líke a "flat thing" with manual versioning -- I guess you could do nesting, there, too with submodules, but I think that will get hard to manage as it grows.
@bep I'm not sure what you mean by 'this is a versioned graph' and Antora would use manual versioning.
Here is how you specify the content sources to pull from and the content version (branches/tags) to include for each content source. https://docs.antora.org/antora/2.0/playbook/configure-content-sources/
You could point to master branch and always pull the latest, but you can also pull from specific branches/tags in that repository to allow for the user to select previous (or future/dev) versions of the content to view in the same site UI.
@zivbk1 what I mean is that it's a fairly shallow graph (one level) and by "manual versioning" I mean that you need to be fairly explicit when you tell what you want (give me