Skip to content

Commit

Permalink
Fix plugin name in documentation (#496)
Browse files Browse the repository at this point in the history
  • Loading branch information
ismailarilik authored and ashmaroli committed Sep 23, 2019
1 parent 61ed01f commit e170d87
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: Jekyll Admin exists in two parts, a Ruby back end and a Javascript

## How Jekyll Admin hooks into Jekyll

Jekyll Admin piggybacks on Jekyll's built-in Webrick server. We monkey patch the `jekyll serve` command to hook in two Sinatra servers, one to serve the static front end that lives in `lib/jekyll-admin/public/dist` via `/admin`, and one to serve the Ruby API via `/_api`. Once the Sinatra servers are mounted, they work just like any other Jekyll server (and we rely on third-party plugins like `sintra-json` and `sinatra-cross_origin`).
Jekyll Admin piggybacks on Jekyll's built-in Webrick server. We monkey patch the `jekyll serve` command to hook in two Sinatra servers, one to serve the static front end that lives in `lib/jekyll-admin/public/dist` via `/admin`, and one to serve the Ruby API via `/_api`. Once the Sinatra servers are mounted, they work just like any other Jekyll server (and we rely on third-party plugins like `sinatra-json` and `sinatra-cross_origin`).

## How Jekyll Admin formats Jekyll objects for the API

Expand Down

0 comments on commit e170d87

Please sign in to comment.