-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Add codepens instead of example Vue components (part 1) #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codepens style is a subject to discuss of course 😅 If we decide to use codepens, I will continue migration in this PR |
Great work! Should we take this chance to "rename" the apps to something other than the meaningless |
@phanan omg that's a great idea! 👍 I am all up for it |
@sdras @znck @bencodezen @phanan @shentao could you please review this one? I've just resolved |
Feat/introduction
This PR is moving a part of our example Vue components to codepens and implements multiple fixes to existing docs.
What is done
I'm splitting the work on adding codepens intentionally, otherwise, this PR will become too large to review it thoroughly.
Follow-up MR to continue this work: #60