Initial commit for refresh of the mdnext ecosystem. #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
THIS IS A WIP CHANGE TO ECOSYSTEM
This will be the main area for updates and discussion around refreshing the
mdnext
ecosystem with better DXProblems 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 thestarter
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 ofmdnext
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 repoAdd new
toolkit
directory that will housecomponents & 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 ourtoolkit
code snippets & create a fewHow To
examples