You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
Here are a couple suggestions that I would make a PR to propose but can't, because, well, GitHub! Most of these are pretty small and don't matter in the grand scheme of things but still are best practice and should be used.
Add a description & link to the website.
Just make the description something basic like "Gettin freaky on a Friday night y'all"
Link to the website with https, not a lot to that on
Add some dang tags!
newgrounds, haxe, haxeflixel, etc., all help with SEO and just make everything look a lot nicer
Separate LICENSE for assets and code
Since this one repo has everyhing, (flash animation files, exported art, music, song data, source code, etc.), there really should be two licenses specified since atm everything falls under the Apache-2.0 license and that isn't really the best for assets.
One file named ASSET_LICENSE and one named CODE_LICENSE is best practice.
Create Wiki
Move the CHANGELOG.md and the Modding.md files to their own page on the wiki too, this makes information much easier to access for people who might not know how to navigate a repo.
Move the Github-Pages site to it's own branch
sorry for all these issues and prs i just have a lot of ideas to help the project even though i dont know haxe lol
This discussion was converted from issue #270 on August 25, 2021 21:33.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Please check for duplicates or similar issues before creating this issue.
What is your suggestion, and why should it be implemented?
Here are a couple suggestions that I would make a PR to propose but can't, because, well, GitHub! Most of these are pretty small and don't matter in the grand scheme of things but still are best practice and should be used.
https
, not a lot to that onnewgrounds
,haxe
,haxeflixel
, etc., all help with SEO and just make everything look a lot nicerASSET_LICENSE
and one namedCODE_LICENSE
is best practice.CHANGELOG.md
and theModding.md
files to their own page on the wiki too, this makes information much easier to access for people who might not know how to navigate a repo.sorry for all these issues and prs i just have a lot of ideas to help the project even though i dont know haxe lolBeta Was this translation helpful? Give feedback.
All reactions