We want to jump on the "PatternFly Next" train and not waste our time implementing current PF.

However:

• PF-next might be quite some time away from being stable enough to use
• customers are disconcerted by visual differences between other middleware products and 3scale (and moving to PF-next now wouldn't address that problem).
• We want to make structural navigation changes (navigate by service) for which current PF has some usable patterns

So it might be a good in-between step to use current PF for new 3scale navigation. Lets find out.