Are we headless yet?
But there’s plenty we could improve for Wagtail’s developers
Get Started
After you’ve set up your Rust and worked yourself through “The Book”, you might want to check any of these resources:
- Educational Rust Live Coding - Web App From Scratch
- Actix-Web Auth Microservice
- Zero to Production in Rust (Series)
- Practical Rust Web Development (Series)
- Rocket Quickstart Guide
There are also some real world examples that can be looked at for reference
- Plume, a Federated blogging app (Rocket)
- Yew realworld app (WebAssembly)
- Seed realworld app (WebAssembly)
- Lemmy, a Federated alternative to Reddit (Actix-web)
- Rust + Rocket RealWorld example
If you find yourself stuck and looking for help, you can check out the official Rust forum, the Rust tag on Stackoverflow, or the Rust Discord server where you are welcome to post your questions and will find excellent help.
News
Development updates, 13th May 2015
Brace yourselves, 1.0 is coming. Luckily, it is not scary as the winter from Game of Thrones.
Development updates, 13th May 2015
Brace yourselves, 1.0 is coming. Luckily, it is not scary as the winter from Game of Thrones.
Topics
Page URL Routing
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Rich text rendering
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Images
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Multi Site support
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Page URL Routing
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Multi Site support
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Images
URL patterns on a headless site are usually configured in the frontend framework (such as Next.js or Gatsby). Wagtail by default, resolves URLs to pages using their slugs and location in the page tree.
Issues
Github issues tagged #headless
Resources
After you’ve set up your Rust and worked yourself through “The Book”, you might want to check any of these resources:
- Educational Rust Live Coding - Web App From Scratch
- Actix-Web Auth Microservice
- Zero to Production in Rust (Series)
- Practical Rust Web Development (Series)
- Rocket Quickstart Guide
- Educational Rust Live Coding - Web App From Scratch
- Actix-Web Auth Microservice
- Zero to Production in Rust (Series)
- Practical Rust Web Development (Series)
- Rocket Quickstart Guide
Help Out
After you’ve set up your Rust and worked yourself through “The Book”, you might want to check any of these resources: