-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Change Vuetron link #1933
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
Merged
Merged
Change Vuetron link #1933
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since vuetron.io domain was expired and redirects to some news/malware sites, I changed Vuetron link to it's github site.
Thanks @artn! I took a look at the domain and indeed it's redirecting to a malware host. However, I'm kind of tempted to remove Vuetron altogether, as the project doesn't look very active (the fact that the domain expired at least more than a month ago and no one seems to care is among the indications). @sdras What do you think? |
Pinging @yyx990803. |
Agreed, let's remove it. |
Removing Vuetron as the project is no longer active.
lex111
added a commit
to lex111/vuejs.org
that referenced
this pull request
Jan 28, 2019
In continuation to this PR vuejs#1933
Merged
phanan
pushed a commit
that referenced
this pull request
Jan 28, 2019
In continuation to this PR #1933
vuejs-jp-bot
pushed a commit
to vuejs-jp-bot/jp.vuejs.org
that referenced
this pull request
Jan 28, 2019
In continuation to this PR vuejs/v2.vuejs.org#1933
potato4d
pushed a commit
to vuejs/jp.vuejs.org
that referenced
this pull request
Jan 29, 2019
In continuation to this PR vuejs/v2.vuejs.org#1933
Jinjiang
pushed a commit
to vuejs/v2.cn.vuejs.org
that referenced
this pull request
Jan 30, 2019
In continuation to this PR vuejs/v2.vuejs.org#1933
Jinjiang
added a commit
to vuejs/v2.cn.vuejs.org
that referenced
this pull request
Feb 13, 2019
* Update render-function.md (#1887) Unnecessary escape character: \- * Link to VNode info where it is first mentioned (#1855) Otherwise, VNode is used without definition the first time you encounter it in the Guide. Fixes #1799. * Format examples (#1895) So they don't require horizontal scrolling * Unify examples HTML formatting (#1894) * Unify examples HTML formatting * Unify examples HTML formatting * improve phrasing in conditonal key demo link * Docs/add community partner (#1906) * docs: Add Ben Hong to Community Partners * style: Remove new lines from autoformatting * Recommend Vue CLI 3 instead of Vue CLI 2 (#1891) * brush up tooling section with redirects to CLI * secretly sneak Gusto into core team (#1911) * Update coc (#1908) * Adds Code Of Conduct via contributor-covenant version 1.4 * Change community email * Resolve conflict * Specified accurate url. (#1909) * Specify which types are allowed as values for 'key' of 'v-for' (#1900) [List Rendering](https://vuejs.org/v2/guide/list.html#key) guide doesn't mention what types of values user can supply for `key` of `v-for`. There is a console warning for this already but it's hard to point people to it. This pull request fixes the issue. * Add version that properties were introduced in (#1914) `$attrs` and `$listeners` were introduced in v2.4.0. The docs should mention this in order to avoid confusion. * add package-lock.json to .gitignore * Add Vuejs Amsterdam (#1904) * Add Vuejs Amsterdam * fix profiles for vue.js amsterdam organizers * Fix mixin data merging documentation (#1902) * Elaborate on what types of handlers are allowed in Array watchers (#1898) * add VueConf US organizers to community partners * Use product name instead of package name * added the link to funcitonal components (#1926) * chore: update deps * chore: prune unused images * Update unit-testing-vue-components.md (#1934) * Update dockerize cookbook (#1944) * Update dockerize cookbook Node 9 has been EOL for a while, this will make sure people will always use the latest LTS version, instead of a hardcoded version number * Update dockerize-vuejs-app.md * chore: Update links to new JSX plugin (#1942) * Add comments about $watch behavior with a function (#1946) * translated the last commit * Update invalid live demo link (#1951) The link to the live demo is not up-to-date. I've updated it to the same one as noted in [vue-hackernews-2.0](https://github.com/vuejs/vue-hackernews-2.0/blob/master/README.md) * Update team.md (#1957) * chore: add clarkdo into members list (#1958) * add soda to core team * add Pine to core team * update team page per governance document definitions * Fix roadmap link (#1961) * update teams * Fix Rollup instructions (#1920) This commit fixes broken instructions on how to bundle the Runtime + Compiler with Rollup. Related: rollup/rollup#2609 * Fix the async_function syntax in the example (#1878) The example of using async_function syntax is wrong, fix it. * Remove Vuetron (#1933) Removing Vuetron as the project is no longer active. * Adding Quasar Framework (#1857) * Fix #1802; Update docs to avoid misconceptions around emitting events (#1838) * Updates render function tip with note about `h` not always being required (#1774) * Remove Vuetron image (#1963) In continuation to this PR vuejs/v2.vuejs.org#1933 * Clarify that "slot-scope" is named "scope" before 2.5.0 (#1956) * Clarify that "slot-scope" is named "scope" before 2.5.0 * Improve wording * Update Key Modifiers to suggest KeyboardEvent.key (#1850) Fixes [#1765](vuejs/v2.vuejs.org#1765). I left the "define custom key modifier aliases" section at the bottom, below the deprecated key codes information. Definitely open to changing / re-arranging as needed! * remove deprecated repos from my team page profile (#1966) * vuejs-templates/* is deprecated because of Vue CLI 3 * vue-touch has been depreceated because of lack of development * Added community partner Filip Rakowski (#1960) Added myself as a community partner  * Remove myself from emeriti and add official repo back (#1967) * synced sponsors info * Update src/v2/guide/components.md Co-Authored-By: Jinjiang <zhaojinjiang@me.com> * Update src/v2/guide/deployment.md Co-Authored-By: Jinjiang <zhaojinjiang@me.com> * Apply suggestions from code review Co-Authored-By: Jinjiang <zhaojinjiang@me.com> * Apply suggestions from code review Co-Authored-By: Jinjiang <zhaojinjiang@me.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since vuetron.io domain was expired and redirects to some news or malware sites, I changed Vuetron link to it's github site.