Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[blog] post for gatsby-plugin-page-creator #6339

Merged
merged 6 commits into from
Jul 12, 2018
Merged
Changes from 1 commit
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
Prev Previous commit
Next Next commit
add gatsby manor clarification
  • Loading branch information
nodox committed Jul 10, 2018
commit 157c923833f93c3d54ff0305adec84efc1c260d5
4 changes: 2 additions & 2 deletions docs/blog/2018-07-07-the-gatsby-plugin-page-creator/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ problem that sparked the creation of this plugin. Afterwards, we'll talk about h
use this plugin to auto create pages without having to place your components in the **src/pages** directory.

# The problem with static values
Here's how it all got started. The goal with [Gatsby Manor](https://gatsbymanor.com)
Here's how it all got started. The goal with [Gatsby Manor](https://gatsbymanor.com) (a separate project, unaffiliated with the Gatsby core team)
is to create professional designed Gatsby starters
to give your site a clean, modern look the moment you create a new project.
to give your site a clean, modern look the moment you create a new project.
While creating our newest starter
[gatsby-starter-eventually](https://gatsbymanor/demo/eventually),
I wanted to organize the directory structure of the project to better fit my
Expand Down