The Gateway WP Admin page is known internally as the Raptor Editor. This is an example of infinite canvas editing that integrates React Flow. Thanks to the amazing MIT licensed product for being a part of bringing this functionality to WordPress. In this lesson we’ll make sure you know what features are available in the Raptor editor and know how to navigate around it efficiently.
Shows stats for usage and recent week of API requests to collection routes. Also shows helpful links to docs and support.
Shows Registered Extensions first, branches off to show Extension Editor. The difference between these two views is that the first shows actual registered extensions including code-based extensions, while the Extension Editor is for extensions made in the Raptor Editor only and which live in the database. Typically if you make an extension, let’s say “Events” in the Extension Editor it will get built and then presented on the Registered Extension list. However in some cases you might later deactivate that extension, but this will only remove it from the Registered Extensions because that no longer finds the active code version. The database version or “Raptor Mirror” will continue to exist and will appear in the Extension Editor.
The Extension Editor utilizes graph editing powered by React Flow. It enables users to view all their extensions and click to edit the details. Extensions can also be deleted here which uses cascading delete to remove all related collections/packages/fields etc.
A similar interface to the extension we covered previously. After adding an extension this is the logical next step. Add one or more packages to provide an admin page for the extension and to group related collections. Some projects will skip packaging, opting to manage the content in the default Gateway > Records location instead. There are two unique screens available, the List View shows all registered (actual) packages that live in code. The graph shows only the database stored (mirrored) database packages, which were created using the Raptor Editor.
Now we get to the vital aspect of any Gateway extension, the collections. There are 3 screens available under Gateway > Collections. The default is the Editable Collections. These are collections made in Raptor that live in the database and can be edited using the Raptor Editor. Next we have the Registered Collections, a list of all collections that live in code and are registered with Gateway. Options here include making the migration file, or running a migration manually for the given collection. The final screen is dedicated to making relationships between collections.