Skip to content

Readme rewrite#936

Open
LucretiaArc wants to merge 4 commits into
HackerN64:develop/2.4.0from
LucretiaArc:readme-rewrite
Open

Readme rewrite#936
LucretiaArc wants to merge 4 commits into
HackerN64:develop/2.4.0from
LucretiaArc:readme-rewrite

Conversation

@LucretiaArc
Copy link
Copy Markdown

Credits have been moved to CONTRIBUTORS.md, and mentions of the users that made any given change were removed. It would be best to keep that information (if kept separately from the commit log) in one place outside of the readme. This file probably needs some attention but that might be a project we defer for later in the name of readying this for 2.4.

Changes have also been shuffled around into rough categories, with mentions of many minor ones removed, since most people looking for a summary of the project aren't interested in every little change. If we want to maintain a list of features or changes, we should do that as part of a separate document. That seems like tedious work, and something that's easy to have desynchronise from the state of the project, but it could help with feature discoverability.

Comment thread CONTRIBUTORS.md Outdated
Comment thread README.md
Copy link
Copy Markdown
Collaborator

@gheskett gheskett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would maybe add a Q+A answer for when to use HackerSM64 vs ultrasm64 or something (maybe along with other common Q+A cases if we're gonna bother adding the category).

Comment thread README.md Outdated
@LucretiaArc
Copy link
Copy Markdown
Author

I've added a short FAQ with only two questions for now, but if you can think of any pressing ones feel free to add/mention them.

Copy link
Copy Markdown
Collaborator

@gheskett gheskett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made a few of my own additional changes. While I don't think it's perfect (probably missing a lot of things that don't come to mind atm), it's probably good enough right now at least for me.

@gheskett gheskett added documentation Improvements or additions to documentation enhancement New feature or request cleanup Removal of useless or bloat code/features labels May 11, 2026
@gheskett gheskett added this to the 2.4 milestone May 11, 2026
@gheskett gheskett linked an issue May 11, 2026 that may be closed by this pull request
@gheskett gheskett added the blocker This MUST be resolved before the feature branch can be merged. label May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocker This MUST be resolved before the feature branch can be merged. cleanup Removal of useless or bloat code/features documentation Improvements or additions to documentation enhancement New feature or request

Projects

Status: Needs Review

Development

Successfully merging this pull request may close these issues.

README Cleanup

3 participants