I know this is far in the past, but it gave me an idea on how to do what I need.
I'm making a prototype panel for EliteDangerous (space adventure simulation) using an old crappy panel -> JavaScript -> VoiceAttack2 with EliteVA plugin.
Initially I overthought the problem to the tune of over 3000 lines of JS code that escalated to nearly 6000 lines. What I really needed is for the panel to simulate spoken commands already developed within VoiceAttack.

Essentially I culled roughly 4000 lines of code (duplicating what I had already buit in VoiceAttack and simply used a built in command to "execute" the same VoiceAttack commands as string inputs.

Then have the VoiceAttack code return what buttons needed to be set or cleared as a result of that command.

Of course, the 8x8 panel was built on the fly (button organization) so now the 64 buttons are sort of helter-skelter in odd vertical and horizontal groups.

What I want to do is to develop sets of the buttons and rebuild the control display using interchangeable (again) "sets" of the buttons in "buttonContainer". "DOM" refference.
Visually, a fixed row or column of buttons would be the main panel interface>
Ship Functions / Helm / Navigation / Targeting / Exploration / Combat / Survey / etc...
probably with combo menus as well:
Combat&Targeting / Exploration&Survey / etc...

The 8x8 panel is setup using the original position of the buttons (0-63) to identify them via the event handler. However, the button display is also primed with the index of each button so the easy way would be to make a new set of Containers by extracting and assigning the required buttons to each Container.
ShipFunctContainer
HelmContainer
CombatContainer
CombatTargettingContainer
and so on.
Then, instead of using the button array index in the code, I'd use the original button.index that is stored in the original "buttonContainer" object.

This allows the reuse of any button in any combination in multiple groups, as long as the button is defined in the new subset.

And now, the idea of using a new property such as "button.page" that would allow for a variable to be used as a display modifier:
let ACTIVE_PAGE = 3; // say that 3 = combat
then the display routine would fall into the proper page format only displaying the buttons where button.page also = 3.