Update readme for docs #2061
Update readme for docs #2061
Conversation
* master: Update CF_API_KEY example for docker run (itzg#2060) With AUTO_CURSEFORGE handle modpacks not allowed for distribution by author (itzg#2059) Redacts sensitive headers from debugs like with AUTO_CURSEFORGE (itzg#2058) Downloads handle content disposition filename with RFC 2047 encoding (itzg#2057)
|
It makes me nervous 😀, but does seem like clearing out the rest of the docs is the best way to avoid duplicate effort with updates. I'm thinking "Intro" would be the only section that would remain with perhaps your new link just below that. I wish I could remember where I generated this image that use in the Docker Hub README: |
|
Maybe rename README for the time being. so that the full docs are available (in case anything was missed) |
Great idea. Would you prefer I do the big switcheroo to make it "official"? |
|
how ever you want to do it. |
itzg
left a comment
itzg
left a comment
There was a problem hiding this comment.
Forgot to actually merge this one...got distracted with the discussion I started 😀
* master: Tweak level of new docs link (itzg#2063) updated the readme to include the link to the docs site. (itzg#2061) Update CF_API_KEY example for docker run (itzg#2060) With AUTO_CURSEFORGE handle modpacks not allowed for distribution by author (itzg#2059) Redacts sensitive headers from debugs like with AUTO_CURSEFORGE (itzg#2058) Downloads handle content disposition filename with RFC 2047 encoding (itzg#2057) Auto CurseForge, added docs to use env file (itzg#2054)
2 participants
Added a link at the top of the readme to the new documentation site.
Should the rest of the readme be "cleared" out, or just contain some basic info, or stay as it is?