-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC: Death to readthedocs #667
Conversation
hydroflame
commented
Jul 10, 2023
•
edited
Loading
edited
- Implement markdown with MUI.
- Move and convert all rst documentation to md
- Rework documentation a little bit.
- Rename Tutorial tab to Documentation tab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code generally looks good. I didn't try running it, though.
import { getPage } from "./root"; | ||
import { Navigator, useHistory } from "../../ui/React/Documentation"; | ||
|
||
const resolveRelativePath = (folder: string, relative: string): string => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty sure we already have utility functions for these.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do but there is a little finessing needed to get the existing resolveFilePath to work here, since it defaults to using an absolute path unless the path actually starts with ./
or ../
I posted a suggestion but this can easily be dealt with later once everything is working correctly, even in a followup PR.
@@ -0,0 +1,3 @@ | |||
# Bladeburners | |||
|
|||
PLACEHOLDER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a lot of files like this still. This is a lot of docs to bite off in one chunk. IMO it would make more sense to delete each RST as it is converted, and do them in batches, but if you want to do them all in one go I'm not gonna stop you.
Just committing a minimal fix so there's a working base for anyone doing testing Build: fixed filename on an import Lint: Removed empty function on useEffect, then removed unused useEffect import Format: Removed a double-newline in autogen file
@hydroflame I see what you mean with renaming the directory not working right, it works fine locally but the rename doesn't actually get reflected in the commit, so the committed version still fails to build. I'm renaming that folder to Markdown, that way the change is not strictly capitalization and it should go through. Sorry for any inconvenience, not trying to step on your toes just trying to get this in a state where people can continue to test it without needing to apply local fixes to make the game build. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think addressed everything. @Snarling No need to feel bad for fixing my stuff. I appreciate it. I didn't know it prevented other people from building though. Now I'm going to fill in all the placeholders. |
I had to rename the folder |
There are still some placeholder files but it's too mind numbing to write these things. I hope a user will get annoyed enough to write it for us. |
Fix #624 |
Noooooo why not Edit: Replied to the wrong comment, but this comment is important too. This is exactly what I was worried about when you started by deleting all the .rst. Writing documentation is mind-numbing; you can't count on anyone else doing it. I don't think we should be deleting the unconverted docs until they have converted replacements. |