Notes from reading cristijora/vue-paper-dashboard SidebarPlugin
Usually components are suited for most cases. I would say 80-90% of the cases. For the rest 10-20%, you might find yourself using directives and plugins. Plugins usually incorporate some logic (data, component registration, maybe mixins or even directives)
- cristijora
Step 1. create a directory for the plugin
This is side-document providing details for some highlighted changes in 2.5.0. For a full list of changes, see the full release note.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <link rel="apple-touch-icon" sizes="76x76" href="static/img/apple-icon.png"> | |
| <link rel="icon" type="image/png" sizes="96x96" href="static/img/favicon.png"> | |
| <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" /> | |
| <title>Vue Paper Dashboard</title> | |
| <!-- Bootstrap core CSS --> |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
