Code Monkey home page Code Monkey logo

vuejs.org's Introduction

vuejs.org

This site is built with hexo. Site content is written in Markdown format located in src. Pull requests welcome!

Writing

See the Vue Docs Writing Guide for our rules and recommendations on writing and maintaining documentation.

Developing

$ npm install
$ npm start # dev server at http://localhost:4000

Deploying

The site is automatically deployed when commits land in master, via Netlify.

If you are the maintainer of a community translation fork and would like to deploy via Netlify instead of GitHub pages, please ping @yyx990803 in an issue to request a Netlify team membership and DNS update.

On Translations

Translations for this documentation project are currently maintained in separate repositories forked from this original one.

Arabic

Arabic translation is maintained by Interstellar Club

French

French translation is maintained by Vuejs-FR.

Italian

Japanese

Japanese translation is maintained by Vue.js japan user group

Korean

Korean translation is maintained by Vue.js Korean User group.

Mandarin

Persian (Farsi)

Persian translation is maintained by VueJS-fa.

Português-Br

Português-Br translation is maintained by Vuejs-Br.

Russian

Russian translation is maintained by Translation Gang.

Spanish

Spanish translation is maintained by:

1950Labs & Vue.js Montevideo:

Vietnamese

Vietnamese translation is maintained by Vue.js Vietnam User group.

Want to help with the translation?

If you feel okay with translating quite alone, you can fork the repo, post a comment on the Community Translation Announcements issue page to inform others that you're doing the translation and go for it.

If you are more of a team player, Translation Gang might be for you. Let us know somehow that you're ready to join this international open-source translators community. Feel free to contact Grigoriy Beziuk or anybody else from the team.

And thank you in advance ;)

vuejs.org's People

Contributors

01abhishekjain avatar alex-sokolov avatar alexandro86 avatar alphacentauri82 avatar azamat-sharapov avatar changjoo-park avatar chrisvfritz avatar defcc avatar fadymak avatar faliure avatar fedekau avatar flarra avatar gbezyuk avatar jinjiang avatar justineo avatar kazupon avatar lex111 avatar linusborg avatar machinisteweb avatar marktinsley avatar pablorn avatar phanan avatar posva avatar sdras avatar shentao avatar sxcamacho avatar tintef avatar yanxyz avatar yilber avatar yyx990803 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vuejs.org's Issues

Se ha olvidado eliminar el texto original después de traducción

En el archivo src/v2/api/index.md se ha olvidado eliminar un párrafo inglés después de traducción:

vm.$props

Nuevo en 2.2.0+

  • Tipo: Object

  • Detalles:

    Un objeto representando las propiedades actuales que un componente recibió. La instancia Vue provee acceso a estas propiedades en su objeto props.

    An object representing the current props a component has received. The Vue instance proxies access to the properties on its props object.

Podemos ver que el último párrafo es un duplicación ya no es necesario.

No se recomienda traducir los claves como "false" a "falso"

Hola todos! muchas gracias a tus esfuerzos para traducir Vue a la lengua Español, cuando leo el versión Español me encuentro que algunos claves son también traducido como otras palabras al mismo tiempo, por ejemplo:

Un hook errorCaptured puede devolver falso para evitar que el error continúe propagándose. Esto esencialmente diría "este error ya ha sido manejado y debe ignorarse". Evitará cualquier hook adicional de ErrorCaptured y el error invocará el config.errorHandler global.

En este caso creo que es mejor dejar false sin cambios porque no devolvemos falso en realidad :)

Lack of information on debugging in the browser with Vite, VSCode, and Bunjs in Docker or Podman on link https://github.com/1950Labs/vuejs.org/blob/master/src/v2/cookbook/debugging-in-vscode.md, especially as it only discusses vue-cli

Dear team,

I hope this message finds you well. I am reaching out to inform you about a lack of information on the provided link: https://github.com/1950Labs/vuejs.org/blob/master/src/v2/cookbook/debugging-in-vscode.md.

On this link, there is no information on how to debug in the browser using Vite, Visual Studio Code (VSCode), and Bunjs, especially when running within a container. This is crucial for developers working in containerized environments and using these technologies.

It would be highly beneficial to have specific details on configuring and utilizing debugging tools in this scenario, ensuring a smooth and efficient development experience.

I would also like to note that the current content refers to vue-cli; however, this is not applicable to new projects as they are built with Vite.

I look forward to your prompt attention and would appreciate any updates or corrections to the mentioned link.

Thank you for your time and collaboration.

Best regards,
Andrés Eduardo García Márquez

VuePress Migration Feedback

Hello @sxcamacho and other others I might have missed!

My name is Ben Hong and I'm a Vue.js Community Partner that is currently working with the Vue.js Core Docs Team to help with updating the platform from Hexo to VuePress. During this time, we plan to have a content freeze in order to ensure all of the sites stay in sync with one another.

As maintainers for the Spanish translation site, are there any pain points or concerns that you might have about this migration? We would love to hear from you and make sure your thoughts are taken into consideration before starting work on this.

Looking forward to your response!

`contendo` se parece una errata de `contenido`?

Parece que contenido es más apropiado en vez de contendo cuando se refiere al sustantivo content de inglés en algunos lugares, lo he visto que por casi todo el documento src/v2/api/index.md el texto del vínculo Distribución de contendo con Slots usa contendo en vez de contenido, me parece que es una errata? por ejemplo:

  1. en sección vm.$scopedSlots hay un vínculo:
  • Vea también:

Creo que en el texto del segundo vínculo contenido es más apropiado que contendo, y hay otros vínculos cuyos textos son también Distribución de contendo con Slots, no pongo más ejemplos aquí.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.