DONE

• Dynamic Groups Improvements: Classes will have a lot more "optional" spells in DF, the best way to lay that out is argueably dynamic groups. We might need more layout options, and dynamic groups sort/layout too often. => bunch of tickets
• Evoker's essence => Power trigger done. As it's own trigger with progress per essence waiting for more stable API. And that stable api is missing even 4 days before the release. I guess they don't care enough.
• Styling Inspirations from new default UI => #4054
• Show/Magnetic to the UI Edit grid (?) = #4053
• Rewrite BT2 again: https://wowpedia.fandom.com/wiki/Patch_10.0.0/API_changes#Unit_Aura_Changes => #4052
• UnitTokenFromGUID. We actually have no use for that. We don't really use guids much, the combat log trigger could mabye use it to fetch more information. The other place where we use guids a lot is in the buff trigger's multi tracking. But the main purpose of that code is to also augment match datas if we later get a unit id for a guid and that means we need the tracking code anyway.
• Stop Motion: Add FlipBook textures ?
• C_TooltipInfo ?
• Test and improve conversion from existing settings. (Talent, Covenant, BT1, BT2)
• FontStrings in 10.0 have gained Get/SetRotation APIs now (Postponed, the api is too buggy atm)
• MajorFaction support for Reputation trigger (renown)
• Enable Swipe by default for Icons (That'll break some very old auras, but it's been long enough I think)
• Talent Known trigger needs a rework
• Reenable SetTransform via CreateVector3D, see: https://discord.com/channels/327414731654692866/1014994401644269670/1023663373382058014
• Revert 1522aaf and use new API instead.
• Cast Trigger: Empower => need to think about automated ticks placement
• Adjust to new talent system => widget still need to be looked at for optimization, like not create frame for all buttons if not open, check if frames are correctly released when switching tab
• Remove BT1
• Remove covenant load option
• Protect WeakAurasSaved and introduce a supported mechanism for saving data
• Clean up WeakAuras table some more
• Warn about WeakAuras.region usage
• Remove GetLegendariesBonusIds
• Deprecate sending all events to custom triggers, keep same behaviour for existing auras, but add a "OPTIONS_CLOSE"? event for new auras.
• Don't create all regions on login, make most region creation lazy

Cast trigger has to use new EMPOWER api, and ideally Tick subregions should be able to use it without custom code

I'm (slowly) working on an ace3 widget to replace the dropdown with a mini talent window, it will need a dedicated version for each extension

Not TODO, but i see an increase in animations usage & mask textures for castbars, ticks and other ui elements, so i expect feature requests to be able to mimic what wow ui does

All good points! And yeah we should take a look at what blizzard does and add sub elements if possible.

Reputation trigger => check changes made to framexml/reputationframe.lua and framexml/reputationbar.lua with new MajorFaction stuff

Evoker's essence may needs it's own trigger like DK Rune, or rename DK rune and support essences in same trigger
I have not look how their internals works yet

Probably its own trigger, the dk trigger is a rather complex beast. But let me add it to the todo list.

All done or distributed to its own triggers.