title: gatsby.js - advanced starter - Implement 2 url prefixes (2 different sections of site)?
body: <p>It looks as though if you put your jsx files in the 'pages' folder of most gatsby starters, the urls follow the directory structure out of the box, so you can implement whatever urls you need (<a href="http://blah.com/" rel="nofollow noreferrer">http://blah.com/</a><strong>foo</strong>/post1, <a href="http://blah.com/" rel="nofollow noreferrer">http://blah.com/</a><strong>bar</strong>/post2) just by nesting folders in the source tree (<code>pages/foo/post.jsx</code>, <code>pages/bar/post2.jsx</code>).</p>
  
  <h1>The issue</h1>
  
  <p>I used the <strong>gatsby advanced starter</strong> (<a href="https://github.com/Vagr9K/gatsby-advanced-starter" rel="nofollow noreferrer">https://github.com/Vagr9K/gatsby-advanced-starter</a>). It puts all content files not in <code>pages/</code>, but in a top-level <code>content/</code> folder and I can't figure out the wiring to replicate foo/xxx, bar/xxx urls even after creating <code>content/foo/post1.md</code>, <code>content/bar/post2.md</code> folders.</p>
  
  <p>It <em>does</em> have a siteconfig.js that sets a single path prefix, but I want <strong>two</strong> different prefixes for the 2 different sections of the site, so I just set it to "/" for now (builds seem to ignore whatever value I set for this config param anyway, so... shrug).</p>
  
  <h1>What I tried</h1>
  
  <ul>
  <li>I tried adding <code>path</code> to the frontmatter of the .md files and set it to the parent foldername. This was completely ignored (in any case I don't think that's what I want... I'd like to keep the generated slug as part of the url).</li>
  <li>Separated use of <code>gatsby-source-filesystem</code> one for each subfolder hoping it would change graphql graph to recognize 2 separate data sources but it made no difference.</li>
  </ul>
  
  <p>What am I doing wrong?</p>