When a request is served by WebEngine, it reads the url path and attempts to match the url path to a content item resources. URL are checked against resource in a specific order, and will resolve the resource first if a match is found. If two resources share a URL path, then the one that loads first will resolve and the other is ignored.
Resource load order:
Static files generated by Zesty.io: site.css and site.js
Instant JSON API e.g. /-/instant/7-zyx-zyxzyc.json
GQL API e.g. /-/gql/*
Static files generated by Zesty.io: sitemap.xml, feed.xml, robots.txt
Legacy JSON endpoints e.g. /-/custom/
Well Known Files e.g. /.well-known/*
Custom endpoints e.g. /custom/endpoints.json
Legacy HTML endpoints e.g. /ajax/
Content Models Views if a content item's meta path matches the request page e.g. /about/team/
Wild Card Views e.g. /store/*/cool-shirt/
301 redirects
404 Pages e.g. when no resources match the url pattern