How Scribe works

Attention

These docs are for Scribe v2, which is no longer maintained. See scribe.knuckles.wtf/laravel for Scribe v3.

Read this page if you want a deeper understanding of how Scribe works (for instance, for the purpose of contributing).

• When the generate command is run, the Generator fetches all your application’s routes from Laravel’s (or DIngo’s) Route facade.
• Next, the RouteMatcher uses the rules in your config to determine what routes to generate documentation for, as well as extract any specific configuration for them. This configuration is passed to the next stages.
• The Generator processes each route. This means fetching the route action (controller, method) and using the configured strategies to extract the following:
  • route metadata (name, description, group name, group description, auth status)
  • url parameters
  • body parameters
  • query parameters
  • headers
  • fields in the response
  • sample responses
• Next, the Writer uses information from these parsed routes and other configuration to generate a Markdown file via Blade templating.
• This Markdown file is passed to Pastel, which wraps them in a theme and converts them into HTML, CSS and JS.
• If enabled, a Postman collection is also generated, via the PostmanCollectionWriter.
• If enabled, an OpenAPI specification is also generated, via the OpenAPISpecWriter.