Resource Resolution

The order in which specific types of behavior or views load, from 301 redirects to 404s.

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:

  1. Static files generated by site.css and site.js

  2. Instant JSON API e.g. /-/instant/7-zyx-zyxzyc.json

  3. GQL API e.g. /-/gql/*

  4. Static files generated by sitemap.xml, feed.xml, robots.txt

  5. Legacy JSON endpoints e.g. /-/custom/

  6. Well Known Files e.g. /.well-known/*

  7. Custom endpoints e.g. /custom/endpoints.json

  8. Legacy HTML endpoints e.g. /ajax/

  9. Content Models Views if a content item's meta path matches the request page e.g. /about/team/

  10. Wild Card Views e.g. /store/*/cool-shirt/

  11. 301 redirects

  12. 404 Pages e.g. when no resources match the url pattern

Base Directory Setting will default all automated assets to the root / directory unless there is a setting on the instance with category:general key:base_directory with a directory set as its value e.g. /blog/

Automated files this rule applies to:

Other files created in the code editor must be manually named to follow the path of your choice. Content items must also be parent to a content item with the base name of your choice. For example if you are using WebEngine for only the /blog/ path of your website you need to setup a content item as a holder with the path /blog/ as its URL, and also create a setting with category:general key:base_directory with the value /blog/