5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Plugins"
|
|
sidebar_current: "plugins"
|
|
description: |-
|
|
Vagrant comes with many great features out of the box to get your environments
|
|
up and running. Sometimes, however, you want to change the way Vagrant does
|
|
something or add additional functionality to Vagrant. This can be done via
|
|
Vagrant plugins.
|
|
---
|
|
|
|
# Plugins
|
|
|
|
Vagrant comes with many great features out of the box to get your environments up
|
|
and running. Sometimes, however, you want to change the way Vagrant does something
|
|
or add additional functionality to Vagrant. This can be done via Vagrant
|
|
_plugins_.
|
|
|
|
Plugins are powerful, first-class citizens that extend Vagrant using a
|
|
well-documented, stable API that can withstand major version upgrades.
|
|
|
|
In fact, most of the core of Vagrant is [implemented using plugins](https://github.com/mitchellh/vagrant/tree/master/plugins).
|
|
Since Vagrant [dogfoods](https://en.wikipedia.org/wiki/Eating_your_own_dog_food) its own
|
|
plugin API, you can be confident that the interface is stable and well supported.
|
|
|
|
Use the navigation on the left below the "Plugins" section to learn more
|
|
about how to use and build your own plugins.
|