A1grammar points: Our list is designed especially for beginners, all difficult vocabulary and grammar banished to the later levels. Easy examples, each one with pinyin. Try clicking on one of the images below:
B1 grammar points: For when you're ready to really consolidate your grammar knowledge and fill in the gaps, but really don't want to slog through a grammar textbook. Our self-contained grammar points give you just the right amount to work on.
B2 grammar points: These aren't easy, and often involve more formal language or finer points of the more basic grammar points. It's getting hard to find explanations that really address your needs, but this is one place you can find them!
All of our A1 and A2 grammar points have pinyin throughout, but if you want pinyin for all the Chinese characters in this wiki, you can do that using free browser plugins. Also try clicking on the little cog at the top right of any page to add spaces between characters.
It's not yet time to throw out those textbooks! We all use the internet for everything now, but we see also the value in textbook grammar explanations and exercises, and are doing our best to link textbooks to our own Chinese Grammar Wiki content. To see how it works, click on one of the book covers below or try finding your own textbook in our list, and then seeing what it links to.
AllSet Learning is a Shanghai-based learning consultancy dedicated to helping foreigners better learn Mandarin Chinese. This wiki is maintained by John Pasden and the rest of the team at AllSet Learning. While many of the company's services are only available to clients physically in Shanghai, this wiki is open to the public through a Creative Commons license.
All content on the Chinese Grammar Wiki 2011-2024 AllSet Learning, and may not be used for commercial purposes or without attribution. For more information on how to legally use this content, please see our Creative Commons license unless otherwise noted.
These are the basic 26 grammar points a beginner needs to master in order to start using and comprehending Mandarin Chinese. The Grammar Wiki BOOK series brings to ebook format everything that made the online wiki the internet's #1 reference for Mandarin Chinese grammar:
The 26 grammar points contained in this book are also contained in the longer "Elementary" book; this book is intended as a shorter introduction for beginners who are just looking for a taste in the Chinese Grammar Wiki's friendly format.
This is the community maintained wiki covering all sorts of information on the next-generation peer-to-peer technology platform built by the Ethereum Foundation, including Ethereum, the generalized blockchain for smart contract development, as well as sister protocols like Whisper, the private low-level datagram communication platform, and Swarm, a distributed storage platform and content distribution service. See here for an introduction, and other pages in the sidebar.
If you have a technical issue with a specific client, application or tool, e.g. those listed here, please ask in the Gitter room of that project, and if your issue is still not resolved, post an issue in the repo for that project. Please only create an issue if you can't fix it by editing yourself, it doesn't get resolved via the Gitter documentation room (including pinging someone who knows how to handle the issue, or asking/finding out who knows then pinging them) and only if it is related to the wiki.
If you had an issue that has been closed, and feel that it could be reopened after following the above steps, feel free to request to reopen it. Do not make a pull request; chances are that all PRs will be ignored, since any content in the codebase can be in this wiki instead. About 180 issues and 30 PRs were closed on May 29 2018, due to deleting the codebase and referring people to this wiki, in order to reduce the burden on maintenance by following the above steps. This fits well with Ethereum's ethos of decentralization, which includes minimising bureaucracies, and gives contributors more time to build Ethereum and satisfy the long-term interests of current and future users. If you had an issue or PR that was closed without explanation, I apologize, but it is time-consuming to reply to every one; I'm hoping that people will see the updated readme and this section.
While having good documentation is certainly important to help onboard new people including users and contributors of all kinds, there is a lot to do at the moment in terms of design and implementation, and editing documentation is something that seems best to be done when you are reading or learning about something, using something, building upon something, etc., not usually just for the sake of reading and editing for other users, although reviewing one's own writing is certainly a good practice.
If you notice that a page is vandalized, such as the footer (which has been frequently vandalized), this home page, or the sidebar, please view the page history (which is the link of a page with a /_history appended), and revert to the last known good version (which are listed below for convenience for the above pages), by ticking it and the most recent revision, selecting "Compare revisions", and then "Revert changes":
Avoid changing the title of a page, as the link for it will change. In particular, if you change the title for a page, any link to it will just direct to a blank page. (In the case of this page, also the Wiki tab in the header of this repo, as well as any link to the Home page, will just direct to a list of pages.) If you really want to change the title, then create a new page with the new title, move the contents of the old page to the new page, and update the old page with a redirect link to the new page. If you want to translate a page, create a new page and translate the original there. Consider previewing your changes before saving them, and if you detect any errors, fix them. If you happen to get directed to a page that doesn't exist with a prompt to create a new page, do that, without changing the title. Then check the history of the newly created page. It may be that there is a history of changes to the page that you just created, with the second most recent change (second to you creating the page) being that someone renamed the page. If so, please fix the page (restore it to the revision before the title was changed or redirect to the new page) and tag the person who renamed the page in this issue here or on Gitter.
Wikipedia has five pillars which provide a good standard for contributing that we can adapt for our needs. If you have experience with editing on Wikipedia, then that will help with knowing how to edit this wiki, although the contribution rules are less strict. Referencing facts is a key writing and proofreading task, as well as checking that information is up-to-date (and updating it if otherwise), correcting grammar, typos, and spelling; and making the wiki comprehensive and easy to understand. Other rules, such as a neutral point of view and no original research are desirable, but may be hard to maintain. Notability is less relevant, this wiki is about all things Ethereum.
The title of the page should start with [Language]: title, e.g. "[German] White Paper" or "[中文] 以太坊Wiki目录". Then add a Table of Contents (ToC) page linking for the language, linking to all pages of that language, and add a link to it in the footer.
Please permit your contributions to be under the CC0 license [1], which makes your contributions have no rights reserved, putting them in the public domain. This will help to allow for the dissemination of information about Ethereum, the Ethereum ecosystem and Web 3 to the public, in a completely permissive manner. To state that you accept your contributions to be under a CC0 license, please add yourself to the list of external contributors here. Otherwise, without adding yourself to the list, your contributions will be all rights reserved. Some previous contributions may have all rights reserved (by contributors that have not agreed to a CC0 license at pull request 528), since no copyright permission was stated explicitly. Until all previous contributors agree to a CC0 license, and to provide clarity of licensing, you may also wish to add a HTML comment to the top of pages or sections that you contribute to, like so: .
Users signed in with GitHub can edit and add pages using a browser or locally. To view the wiki locally, scroll to the bottom of the sidebar, and get the link to clone the wiki, (posting here for convenience: ), then press CTRL+ALT+T to open a terminal, run git clone and then view the files from a file explorer or using cd wiki.wiki; ls; // Enter a command to open a file from a terminal, e.g. gedit Home.md.
If you change the headers of the page then it's a good idea to update the contents to reflect that change, using doctoc, but you will need to have access permissions to push changes to this repo; you could ask in , and if there's no response from anyone in the EF after a couple of days, you could ping @Souptacular.
To get the basic concepts of Ethereum visit For another introduction targeted for end users but also for developers and others, see here. If you want to get a deeper understanding, start by reading the whitepaper and the design rationale. For a more formal review, read the yellow paper or the Jello Paper. If you are interested in being a core developer, find a project such as these ones that interests you, and start contributing to that (maybe pro-bono initially, until maintainers like you and decide to hire you). If you start your own project, tell the world about it e.g. on Twitter, Peepeth, Status, and Akasha and see and -foundation-grants-update-wave-4/. For Ethereum research and protocol architecture, visit as well as If you are interested in developing smart contracts you can see here, as well as under App Development (which is also in the sidebar).
3a8082e126