Skip to content
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

migrated VFG docs to newer GitBooks, created GitHub Repo for Docs to … #564

Merged

Conversation

zoul0813
Copy link
Member

…allow for easier maintenance, updated JSFiddle to use "latest" VFG, and created a CodePen version as well

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
    Docs Update
  • What is the current behavior? (You can also link to an open issue here)
    Docs currently point to a JSFiddle that is no longer up-to-date (v2.2.1) and the core documentation is hosted on Legacy GitBooks.
  • What is the new behavior (if this is a feature change)?
    JSFiddle has been updated and now points to the "latest" version of VFG (and should auto-update as it's no longer bound to a specific version).

Migrated the Legacy GitBooks documentation over to the vue-form-generator-docs repo, and synced this repo with a new GitBooks account that will auto-update from the GitHub repo. Documentation can now be updated through GitHub PR's and should hopefully stay more up to date.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
    No
  • Other information:

If you'd like to be added to the GitBook Team, send me a message with your email address. Apparently I can't just add GitHub users by username to the team. It requires me to send an "invite link".

…allow for easier maintenance, updated JSFiddle to use "latest" VFG, and created a CodePen version as well
@coveralls
Copy link

Coverage Status

Coverage remained the same at 89.916% when pulling d372f5b on zoul0813:feature/update-readme-migrate-docs into 1ce7045 on vue-generators:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 89.916% when pulling d372f5b on zoul0813:feature/update-readme-migrate-docs into 1ce7045 on vue-generators:master.

Copy link
Member

@icebob icebob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! Thanks!

@zoul0813 zoul0813 merged commit 20270ed into vue-generators:master Dec 14, 2018
@zoul0813 zoul0813 deleted the feature/update-readme-migrate-docs branch December 14, 2018 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants