Various outdated docs

[ACrazyTown]

There's a good chunk of pages in the handbook and community sections of the documentation that haven't been updated in a bit and are no longer entirely accurate. I've gone through some of them and documented some of the issues I've found here. I'll mainly keep this to just issues with the existing content, I think there's several pages that could be expanded, though that's another discussion!

Handbook

• HaxeFlixel specific conditionals
  • Missing some newly added conditionals, for example: Project.xml additions flixel-templates#51
• HaxeFlixel targets
  • Missing mentions of Hashlink, Neko?
  • General HTML5 Guidelines
    • The page mentions that you should prefer .ogg because of SoundJS. I'm not sure what SoundJS is, perhaps a component of older versions of Lime/NME? Either way, this should be changed to something like "Audio format support is determined by the used web browser. While most audio formats should work, for compatibility sakes you might want to prefer using more common formats like mp3 or ogg"
    • Also mentions seemingly worse performance with particles, though this was added in 2014, before OpenFL added support for WebGL so I think it's safe to assume this is no longer an issue
• Desktop targets
  • Mentions NME and drawTiles(), both of which are no longer used by modern Flixel
  • Need to check if the Project.xml settings are correct nowadays. Should probably link to Lime/OpenFL instead?
  • The test command for linux also has an additional -64 flag that might not be necessary nowadays
• Mobile targets
  • Modern phones aren't as weak as they used to be. I don't think this page has much useful info aside from maybe the table with max texture sizes... featuring devices that are like 15+ years old lol.
• Android, iOS
  • Both of these talk mainly about OpenFL/Lime specifics. Perhaps link to OpenFL/Lime docs instead?
• Neko
  • Neko is old, deprecated, and going to be dropped in Flixel 7.0 (Remove Neko Target flixel#3437). Should probably remove this page altogether, or maybe replace it with a page for Hashlink?
• Troubleshooting
  • Perhaps add more solutions to some confusing issues? (e.g. FlxAtlasFrames returning unknown type for FlxGraphicAsset flixel#3555, [Bug] Unable to press anything in debugger with mouse flixel#3038)

Resources

• Cheat sheet
  • Was last updated in 2021. One thing I noticed was that the state switching syntax wasn't updated, there might be more issues

Community

• About
  • The graphic that shows off the targets is insanely outdated. No mentions of HTML5 while it mentions WebOS and Blackberry which I'm pretty sure are no longer supported.
  • We could probably update the "features overview" with some more cooler eye-catching stuff, than "Group objects together for simplicity" and "Math & Color utilities".
  • Perhaps update the core members list? No mention of George here, and everyone who is listed seems to no longer be involved with HaxeFlixel much.
• Why a Haxe version
  • Another mention of the old drawTiles() API
• Introduction to OpenFL
  • Old logo
  • The "previously known as NME" part is odd to me, because NME is still going as a seperate project
  • Another mention of the old drawTiles() API
• Code contributions
  • Link the contribution guide here?

IMO some of these pages (e.g introductions to various targets, Haxe...) could be completely gutted and possibly replaced with a link to whatever source page. That's not my call though