Do we want to generate MDX and test files for all generated files?

Right now only the Component generator creates MDX and test files along side the actual component JS file. Do we want to create them for Pages, Cells, Services, etc?

If we do create them for Services we’ll probably want to start putting them in a subdirectory just like we do for components. Otherwise we’re going to have a LOT of files in that one directory.

.
├── prisma
│   ├── dev.db
│   ├── migrations
│   ├── schema.prisma
│   └── seeds.js
└── src
    ├── functions
    │   └── graphql.js
    ├── graphql
    │   ├── contacts.sdl.js
    │   └── posts.sdl.js
    └── services
        ├── contacts
        │   ├── contacts.js
        │   ├── contacts.mdx
        │   └── contacts.test.js
        └── posts
            ├── posts.js
            ├── posts.mdx
            └── posts.test.js

[mojombo]

I would add test files, but not mdx files right now. Rob is right that it’s important to get people into the “everything in one directory” mindset right away, and we can put simple test stubs in there without causing any problems. I expect we’ll get some proper testing methodology going soon after we launch, it’s high priority. I would also NOT produce mdx files for anything right now. When we integrate Storybook, we can add mdx in all the right places.

[cannikin]

Created #137 to handle this. Closing this one, we can revisit MDX files in the future.