If you want to be able to re-order pages in the in the Explorer admin,
you're going to have to make a Node that acts like a Page, and the
easiest way to do that is
probably making a dummy
RoutablePage that effectively consumes your app's
urls.py to generate its routes.
On
several projects I found it to be desirable/necessary to have global
navigation menus that weren't strictly derived from the page hierarchy, and the
approach I used was to create a navigation menu object that you can
edit through the snippets interface. I wound up with the code in
this gist.
(It's for an older version of Wagtails so it may not work without
modification; also, the LinkFields mixin is taken from the wagtaildemo
project, but it contains fields for things like Page, Document, URL).
For example take a look at
https://www.wsiassn.org
— the navigation on the top is built from the sitemap, but the footer
navigation is built from three different NavigationMenu snippets. The
items are independent of the site map (which may or may not work for
your use case), and the site adminstrators have the ability to link URLs
that aren't pages managed by Wagtail, such as would be the case with
your app.
Not included is the template tag and template code to
make this work, if this approach solves your problem and you want some
more context/pointers, let me know.