Moved to root for better integration with zeit now

Author: jacob-ebey

.forestry/settings.yml

@@ -15,15 +15,15 @@ sections:
 - type: heading
   label: Config
 - type: document
-  path: src/data/config.json
+  path: data/config.json
   label: Site Info
-upload_dir: src/static
-public_path: "/static"
+upload_dir: public
+public_path: "/"
 front_matter_path: ''
 use_front_matter_path: false
 file_template: ":filename:"
 build:
-  preview_output_directory: src/.next
+  preview_output_directory: .next
   install_dependencies_command: yarn install
   preview_docker_image: node:10
   mount_path: "/srv"

README.md

@@ -2,9 +2,6 @@
   <a style="padding-right: 16px;" href="https://tinacms.org">
     <img src="https://app.forestry.io/assets/forestry-logotype-pos-c71a6bd237d9199d0457ba2811553997ff5bab0d2cd0e740686ab26c00d9c240.svg" width="112" height="28">
   </a>
-  <a href="https://www.nextjs.org/">
-    <img src="src/static/nextjs-black-logo.svg" width="80" height="28">
-  </a>
 </p>
 <h1 align="center">
   Brevifolia
@@ -52,8 +49,8 @@ This will start a dev server, navigate to localhost:3000 to check it out.
 - Site-level configuration is stored in `data/config.json`. 
 - Edit styles within each component or page file within the `<style jsx>` tags. 
 - Global styles live in the `Meta` component. 
+- `public/` is where you images live and will get uploaded.
 - `src/posts/`contains all your markdown blog posts.
-- `src/static/` is where you images live and will get uploaded.
 - `src/pages` is where you page components live. 
 - The blog pages are dynamically generated with a `slug` parameter. See the template in `src/pages/blog/[slug].js`. 
 - The pages & template are comprised of components from `src/components`.

src/components/app-shell/desktop.jsx renamed to components/app-shell/desktop.jsx

@@ -30,7 +30,7 @@ module.exports = ({
       '/': { page : '/'},
     };
     //get all .md files in the posts dir
-    const blogs = glob.sync('src/posts/**/*.md');
+    const blogs = glob.sync('./posts/**/*.md');
 
     //remove path and extension to leave filename only
     const blogSlugs = blogs.map(file => file.split('/')[2].replace(/ /g, '-').slice(0, - 3).trim());

src/components/app-shell/footer.jsx renamed to components/app-shell/footer.jsx

@@ -6,12 +6,12 @@
   "version": "0.1.0",
   "author": "Jacob Ebey",
   "scripts": {
-    "dev": "next src",
-    "build": "next build src",
-    "start": "next start src",
-    "export": "next export src",
+    "dev": "next",
+    "build": "next build",
+    "start": "next start",
+    "export": "next export",
     "deploy": "yarn build && yarn export",
-    "forestry-preview": "next src -p 8080 -H 0.0.0.0"
+    "forestry-preview": "next -p 8080 -H 0.0.0.0"
   },
   "dependencies": {
     "buffer": "^5.5.0",

src/components/app-shell/index.jsx renamed to components/app-shell/index.jsx

@@ -54,7 +54,7 @@ export default function HomePage() {
               </p>
             </Grid.Column>
             <Grid.Column floated="right" width={6} textAlign="center">
-              <Image size="large" src="/static/federation-diagram.svg" style={{ margin: '0 auto 1rem auto' }} />
+              <Image size="large" src="/federation-diagram.svg" style={{ margin: '0 auto 1rem auto' }} />
               <p>
                 Teams can consume components at runtime instead of as part of their build pipeline
               </p>

src/components/app-shell/mobile.jsx renamed to components/app-shell/mobile.jsx

@@ -21,7 +21,7 @@ We are going to build out two separate Single Page Applications (SPA) that use M
 
 `Application A` will contain a `SayHelloFromA` component that will be consumed by `Application B` while `Application B` will contain a `SayHelloFromB` component that will be consumed by `ApplicationA`. This looks like:
 
-![](/static/get-started-diagram.svg "Architecture Diagram")
+![](/get-started-diagram.svg "Architecture Diagram")
 
 This architecture will allow each SPA to be developed and deployed independantly along with instantly recieving updates from other federated applications with zero deployments.
 
@@ -412,10 +412,10 @@ ReactDOM.render(
 
 Looking at the network log for `Application A` you will see that we load two files from `Application B`, the `remoteEntry.js` file, then the `977.js` that contains the `SayHelloFromB` component.
 
-![](/static/application-a-network-log.png)
+![Application B Network Log](/application-a-network-log.png)
 
 Visiting `Application B` for the first time, you'll notice we have already cached the remoteEntries for both `Application B` and `Application A`.
 
-![](/static/application-b-network-log.png)
+![Application B Network Log](/application-b-network-log.png)
 
 **You have just created your first Webpack 5 Federated projects. Now go out and build something awesome!**