- {blogPosts.map(blogPost => (
- <>
- Title: {blogPost.node.content.title.value}
-
- Author: {blogPost.node.content.author.value[0].content.name.value}
-
- {blogPost.node.content.content.value}
-
-
- ))}
-
-)
-
-export default BlogIndex
-```
-
-This template fetches your blog posts from the `pageContext` (passing your data along with this variable), and iterates over all the posts. For each post, it prints the title, the author's name, the content, and whatever you'd like to add that is present in the GraphQL data. For instance, you might also fetch things like tags, categories, snippets, image headers, etc.
-
-Once you have created your template, connect your data to it! Check out the `gatsby-node.js` file found in your root directory. Note that you will need a GraphQL query that you can generate automatically through the web interface. Select all the fields you want to use in your template and copy/paste this query into the new file:
-
-```javascript:title=gatsby-node.js
-const blogQuery = `
- query MyQuery {
- allSeamsCmsBlogpost {
- edges {
- node {
- content {
- title {
- value
- }
- content {
- value
- }
- author {
- value {
- content {
- name {
- value
- }
- }
- }
- }
- categories {
- value {
- content {
- name {
- value
- }
- }
- }
- }
- }
- }
- }
- }
- }
-`
-```
-
-You're almost there! Next, create and export a `createPages` function in the same `gatsby-node.js` file that will create your page:
-
-```javascript:title=gatsby-node.js
-exports.createPages = async ({ graphql, actions: { createPage } }) => {
- const query = await graphql(blogQuery)
-
- createPage({
- path: `/blogs`,
- component: require.resolve("./src/templates/blog-index.js"),
- context: {
- blogPosts: query.data.allSeamsCmsBlogpost.edges,
- },
- })
-}
-```
-
-Finally, when you run `gatsby develop` again, it should generate a `/blogs` page with your content. You can visit this at `http://localhost:8000/blogs`.
-
-## Other resources
-
-For more detailed information about setting up Seams-CMS with Gatsby, see the [Seams-CMS blog](https://blog.seams-cms.com/entry/using-seams-cms-with-gatsbyjs/).
diff --git a/docs/docs/using-gatsby-professionally/answering-it-security.md b/docs/docs/using-gatsby-professionally/answering-it-security.md
deleted file mode 100644
index a6a26433d1935..0000000000000
--- a/docs/docs/using-gatsby-professionally/answering-it-security.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Answering IT & Security Questions
----
-
-At larger companies, such as the Fortune 500, there are Security teams that audit new technologies being used inside the company.
-
-If security engineers are interested in your project, some talking points that can help answer their questions include:
-
-- Because Gatsby compiles your site to flat files, rather than having running app servers and databases users are targeting, it reduces the attack surface of the site to outsiders.
-- Gatsby adds a layer of indirection which obscures your CMS -- so even if your CMS _is_ vulnerable, bad actors have no idea where to find it. This is in contrast to systems where bad actors can easily locate the admin dashboard at, e.g., `/wp-admin` and attempt to hack in.
-- Gatsby lets you serve your site from a global CDN, likely whatever CDN your company is using (e.g. Akamai, Cloudflare, Fastly...), which effectively eliminates the risk of DDoS attacks.
-
-It's helpful to emphasize to security personnel that these benefits were a factor in why Gatsby was selected for the project. You chose Gatsby, in part, because it is _more_ secure.
-
-Read about security in Gatsby: [https://www.gatsbyjs.com/blog/2019-04-06-security-for-modern-web-frameworks/](/blog/2019-04-06-security-for-modern-web-frameworks/)
-
----
-
-**Note:** do you have additional ideas on how to answer IT and security questions for Gatsby projects? We welcome contributions to the Gatsby docs. Find out [how to contribute](/contributing/docs-contributions/).
diff --git a/docs/docs/using-gatsby-professionally/best-practices-for-orgs.md b/docs/docs/using-gatsby-professionally/best-practices-for-orgs.md
deleted file mode 100644
index 16de8256e132a..0000000000000
--- a/docs/docs/using-gatsby-professionally/best-practices-for-orgs.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Best Practices for Organizations
-issue: https://github.com/gatsbyjs/gatsby/issues/14042
----
-
-When you have multiple teams building Gatsby sites, there are some best practices to ensure you're working well at scale. These docs explain those practices.
-
-