Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions lib/content/best-practices/index.js
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,9 @@ module.exports = {
'schwifty-across-plugins': {
title: 'Extending schwifty models across plugins',
subtitle: 'This example of creating a general-purpose "users" plugin demonstrates that, with the help of schwifty, it\'s possible to create highly reusable, data-oriented hapi plugins.'
},
"nested-boilerplate-projects": {
title: "Nested boilerplate projects",
subtitle: "Anything built with pal boilerplate is a Hapi plugin, see how your plugins could hang together.",
}
};
15 changes: 15 additions & 0 deletions lib/content/best-practices/nested-boilerplate-projects.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Nested boilerplate projects

The pal [boilerplate](link:boilerplate) is a proven starting point for your next hapi project, but did you know it also exposes your app as a Hapi plugin?

Hapi plugins are a super-power, and combining them with the pal [tooling](link:tooling) is a perfect way to contain & compose API verticals.

The following diagram is an example of how multiple APIs, all built with [boilerplate](link:boilerplate) can create the fictional service _My Awesome Project_.

![Diagram showing a more advanced structure](/public/img/nested-boilerplate-projects.jpg)

Diagram credit [@yoannma](https://github.com/YoannMa)

[boilerplate]: https://github.com/hapipal/boilerplate
[haute]: https://hapipal.com/docs/haute-couture
[tooling]: https://hapipal.com/docs
Loading