Initial commit for refresh of the mdnext ecosystem.

[domitriusclark]

THIS IS A WIP CHANGE TO ECOSYSTEM

This will be the main area for updates and discussion around refreshing the mdnext ecosystem with better DX

Problems with the current ecosystem:

Every template created is created in our repo, forcing maintainers to have to keep up with mdnext's issues and notifications, rather than basing the template out of their own accounts. This becomes another layer of mostly unnecessary maintenance for our maintainers and those who want to create their own spin on the starter template.

@mdnext/components serves a lesser purpose than originally intended. Once you begin to think about trying to build a component lib on top of another component lib, you start to realize how deep you're baking opinions in. There's probably a better way to offer up components to the ecosystem. Components, alongside other helpful code snippets could help round out this ecosystem, while providing opinions in a way that give the control the user. Better DX while just elevating tools that we use to outfit the templates / build separately in other apps that are built on top of mdnext

With the reduction of maintaining other templates in the ecosystem, the focus then becomes on the templates that remain. Focusing on creating helpful defaults and templates was the initial concept of mdnext. How quickly can we assist someone in creating something new, with some really fun technologies?

Solutions:

• Removing both @mdnext/components and all community submitted templates from the repo

• Add new toolkit directory that will house components & blocks / serverless functions / utility functions / custom hooks

• Create mdnext website to better focus on DX and onboarding. This will allow us a place for exploring our toolkit code snippets & create a few How To examples