Closed xedmain closed 1 month ago
This makes the README table of contents somewhat outdated though. But I'm not sure if we wanna keep maintaining that listing by hand, as it seems the new GitHub web UI has a "Headings" tool in the top-right hamburger menu already, making it somewhat redundant:
Alternatively could set up some GitHub action that rebuilds the ToC for changes to README.md in master.
This makes the README table of contents somewhat outdated though. But I'm not sure if we wanna keep maintaining that listing by hand, as it seems the new GitHub web UI has a "Headings" tool in the top-right hamburger menu already, making it somewhat redundant:
Alternatively could set up some GitHub action that rebuilds the ToC for changes to README.md in master.
I could manually edit the ToC if needed, but I decided that there would be too many subheadings or sth imo, would you want it to have subheadings for Server Ops and Testers/Devs?
I could manually edit the ToC if needed, but I decided that there would be too many subheadings or sth imo, would you want it to have subheadings for Server Ops and Testers/Devs?
I'm ok with keeping the current headings as-is for now. @nullsystem do you have any opinions on this?
@Rainyan @xedmain I'm tempted to just say remove the manual listing and just direct people to use that button for table of content. Admittedly I didn't realize it's a thing but it's automatic and interactive. Also change it for CONTRIBUTING.md.
Yeah, I have to agree we should probably get rid of the handwritten table of contents entirely, for maintainability sake. Could perhaps sneak that change in this PR @xedmain
Sure, should I also edit CONTRIBUTING.md as well?
Sure, should I also edit CONTRIBUTING.md as well?
@xedmain Yes
@Rainyan @nullsystem done