The IFC community is an amazing place with a lot of activity, especially within the ‘Features’ category. Unfortunately, lots of activity can also leads to heaps of topics to sort through. One unpleasant side effect is a vast number of duplicate threads.
One potential way to reduce the clutter is to add additional organization. In this case, it would be an additional layer of tags for the topics in the feature category to allow for easier distinction between the various types of requests (e.g. new liveries, ATC commands, etc.). This would benefit both readers and those in the process of launching a new topic. This could methodology could also extend to other categories in the future (as needed).
As a starting point, I’d throw out the following categories:
- Autopilot: Changes, additions, or other modifications to the autopilit system (e.g. adding VNAV)
- ATC: Changes, additions, or other modifications to the ATC system (e.g. new commands)
- New Liveries: Requests for additional or updated liveries for existing aircraft (e.g. “New Roo” for A330)
- New Aircraft: Requests for new aircraft types that are not currently available IF (e.g. A350)
- Existing Aircraft: Requests for reworks or new variants of aircraft that are already available in IF (e.g. rework 757-200, add 737Max)
- Scenery/Terrain: Changes, additions, or other modifications to scenery and terrain (e.g. taxiway lights, 3D buildings)
- Maps: Changes, additions, or other modifications to the maps available in IF (e.g. add taxiway designations, add gates during flight)
- Other: All other request types
Implementation would take awhile, as there are many existing topics that have not been tagged, but would would progress through a combination of new topics and moderator tagging of the most popular topics