gonna need approval from @j0rge for this but we'd appreciate anything yea, and thanks for suggesting
gonna need approval from @j0rge for this but we'd appreciate anything yea, and thanks for suggesting neocities Pez i forgot that existed lol
Pif you have a slim layout and follow certain rules you can have docs that load REALLY easily
POfficial Mapping and Core documentation for the Quake project Nazi Zombies: Portable
JYESSSSSSS
Jthis is what we need:
INeocities is nice but you have GH pages right there
Pgh pages enforces a heavy webframe etc.
Pit's honestly kinda gross..
Jbasically we want to slurp the
documentationoh that's a sinch
JI am familiar with hugo, I know some of the authors, I just suck at it lol
Twe had a github mkdocs page before this so discourse was actually a better solution 
Pbut for $5 you get way better hosting than ghpages as far as policies go
Pand you are supporting a good crew
Jplus here's the thing, that'd be an awesome action for tons of oss projects. Discourse gives away their forum to OSS people, github hosts gh-pages, make it trivial for OSS projects to make awesome docs by using discourse as a CMS for hugo.
IAs someone who’s written docs professionally (I was at AWS for four years) I can say that just maintaining some markdown files as a GH repo is far preferable to maintain than scraping a live forum.
Forums are for ephemeral and non-essential content
Forums are for ephemeral and non-essential content
Jwe ran our own static site generator for a while
Pthe forum posts are just pinned topic headers anyway
Pthe ones they're directly referencing i assume
Jthe problem is no one contributes to raw markdown files in a github repo
Jwhereas on the forum we just organize by tag and use them as wiki page, it's just the presentation sucks
I? If you have a link to update the page that takes you straight to the editor, people do.
Ti mean tbh jorge nobody outside of the ublue/bazzite contributors really contrbutes to the docs anyways
P^
Jright, but that's independent of the tech we use.
Pyou have to babysit the people that are gonna want to do that stuff anyway.
Tgiven i will daily drive bazzite when my new PC comes in, i guess i would have no problem contributing to docs
Ttrue
Jlike, no one is reading nor writing the docs no matter what we pick except nickname and me lol
Pnext time somebody does offer
Ti like reading my own docs
Plike this kind person above
Pgotta take them under your wing a bit
IYou’d be surprised
Pmake sure they're happy with putting that effort in
Tstill trying to find the justfile that involves "configure-nvidia" where i wanted to add additional kargs as i wrote in #bazzite-dev haha
Pmost people don't stick around for nothing
IA lot of people updated the stuff I was responsible for when I was at aws, and that was just “click button, make change, submit Pr
WRebasing to :testing. Got this:
Jyeah but this is nothing like our day jobs, haha
Pdocs really is a hard one and if people want to contribute they're probably gonna write the stuff up-front with little regard for how it gets hosted in the end
WCan't seem to rebase with this python error. Something weird I need to fix?
Pyou just have to be a facilitator where you can :v
JI mean, I freaking wish it was just like contributing to the k8s docs, but it's a totally different crowd
Krpm-ostree status
Tye, i wouldnt mind anything in particular, really
IThen be the half of the equation you’re missing.
Pwhat we do for the NZ:P docs is just API mirror the content from github to a server
Pand we also accept submissions from people up-front because it's not like they all use github
IU2F.garden has had a handful of people submit fixes and updates over time
