-
-
Version 3, 19 November 2007 Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>
-
-
Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-##
Preamble
-
-The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-Developers that use our General Public Licenses protect your rights
-with two steps: **(1)** assert copyright on the software, and **(2)** offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate. Many developers of free software are heartened and
-encouraged by the resulting cooperation. However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community. It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server. Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals. This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-##
TERMS AND CONDITIONS
-
-### 0. Definitions
-
-“This License” refers to version 3 of the GNU Affero General Public License.
-
-“Copyright” also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-“The Program” refers to any copyrightable work licensed under this
-License. Each licensee is addressed as “you”. “Licensees” and
-“recipients” may be individuals or organizations.
-
-To “modify” a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy. The resulting work is called a “modified version” of the
-earlier work or a work “based on” the earlier work.
-
-A “covered work” means either the unmodified Program or a work based
-on the Program.
-
-To “propagate” a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-To “convey” a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-An interactive user interface displays “Appropriate Legal Notices”
-to the extent that it includes a convenient and prominently visible
-feature that **(1)** displays an appropriate copyright notice, and **(2)**
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-### 1. Source Code
-
-The “source code” for a work means the preferred form of the work
-for making modifications to it. “Object code” means any non-source
-form of a work.
-
-A “Standard Interface” means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-The “System Libraries” of an executable work include anything, other
-than the work as a whole, that **(a)** is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and **(b)** serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-“Major Component”, in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-The “Corresponding Source” for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-The Corresponding Source for a work in source code form is that
-same work.
-
-### 2. Basic Permissions
-
-All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force. You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright. Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-Conveying under any other circumstances is permitted solely under
-the conditions stated below. Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-### 3. Protecting Users' Legal Rights From Anti-Circumvention Law
-
-No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-### 4. Conveying Verbatim Copies
-
-You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-### 5. Conveying Modified Source Versions
-
-You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-* **a)** The work must carry prominent notices stating that you modified
-it, and giving a relevant date.
-* **b)** The work must carry prominent notices stating that it is
-released under this License and any conditions added under section 7.
-This requirement modifies the requirement in section 4 to
-“keep intact all notices”.
-* **c)** You must license the entire work, as a whole, under this
-License to anyone who comes into possession of a copy. This
-License will therefore apply, along with any applicable section 7
-additional terms, to the whole of the work, and all its parts,
-regardless of how they are packaged. This License gives no
-permission to license the work in any other way, but it does not
-invalidate such permission if you have separately received it.
-* **d)** If the work has interactive user interfaces, each must display
-Appropriate Legal Notices; however, if the Program has interactive
-interfaces that do not display Appropriate Legal Notices, your
-work need not make them do so.
-
-A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-“aggregate” if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-### 6. Conveying Non-Source Forms
-
-You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-* **a)** Convey the object code in, or embodied in, a physical product
-(including a physical distribution medium), accompanied by the
-Corresponding Source fixed on a durable physical medium
-customarily used for software interchange.
-* **b)** Convey the object code in, or embodied in, a physical product
-(including a physical distribution medium), accompanied by a
-written offer, valid for at least three years and valid for as
-long as you offer spare parts or customer support for that product
-model, to give anyone who possesses the object code either **(1)** a
-copy of the Corresponding Source for all the software in the
-product that is covered by this License, on a durable physical
-medium customarily used for software interchange, for a price no
-more than your reasonable cost of physically performing this
-conveying of source, or **(2)** access to copy the
-Corresponding Source from a network server at no charge.
-* **c)** Convey individual copies of the object code with a copy of the
-written offer to provide the Corresponding Source. This
-alternative is allowed only occasionally and noncommercially, and
-only if you received the object code with such an offer, in accord
-with subsection 6b.
-* **d)** Convey the object code by offering access from a designated
-place (gratis or for a charge), and offer equivalent access to the
-Corresponding Source in the same way through the same place at no
-further charge. You need not require recipients to copy the
-Corresponding Source along with the object code. If the place to
-copy the object code is a network server, the Corresponding Source
-may be on a different server (operated by you or a third party)
-that supports equivalent copying facilities, provided you maintain
-clear directions next to the object code saying where to find the
-Corresponding Source. Regardless of what server hosts the
-Corresponding Source, you remain obligated to ensure that it is
-available for as long as needed to satisfy these requirements.
-* **e)** Convey the object code using peer-to-peer transmission, provided
-you inform other peers where the object code and Corresponding
-Source of the work are being offered to the general public at no
-charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-A “User Product” is either **(1)** a “consumer product”, which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or **(2)** anything designed or sold for incorporation
-into a dwelling. In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage. For a particular
-product received by a particular user, “normally used” refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product. A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-“Installation Information” for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source. The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed. Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-### 7. Additional Terms
-
-“Additional permissions” are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-* **a)** Disclaiming warranty or limiting liability differently from the
-terms of sections 15 and 16 of this License; or
-* **b)** Requiring preservation of specified reasonable legal notices or
-author attributions in that material or in the Appropriate Legal
-Notices displayed by works containing it; or
-* **c)** Prohibiting misrepresentation of the origin of that material, or
-requiring that modified versions of such material be marked in
-reasonable ways as different from the original version; or
-* **d)** Limiting the use for publicity purposes of names of licensors or
-authors of the material; or
-* **e)** Declining to grant rights under trademark law for use of some
-trade names, trademarks, or service marks; or
-* **f)** Requiring indemnification of licensors and authors of that
-material by anyone who conveys the material (or modified versions of
-it) with contractual assumptions of liability to the recipient, for
-any liability that these contractual assumptions directly impose on
-those licensors and authors.
-
-All other non-permissive additional terms are considered “further
-restrictions” within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-### 8. Termination
-
-You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated **(a)**
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and **(b)** permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-### 9. Acceptance Not Required for Having Copies
-
-You are not required to accept this License in order to receive or
-run a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-### 10. Automatic Licensing of Downstream Recipients
-
-Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
-An “entity transaction” is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-### 11. Patents
-
-A “contributor” is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's “contributor version”.
-
-A contributor's “essential patent claims” are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, “control” includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-In the following three paragraphs, a “patent license” is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To “grant” such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either **(1)** cause the Corresponding Source to be so
-available, or **(2)** arrange to deprive yourself of the benefit of the
-patent license for this particular work, or **(3)** arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. “Knowingly relying” means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-A patent license is “discriminatory” if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License. You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license **(a)** in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or **(b)** primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-### 12. No Surrender of Others' Freedom
-
-If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all. For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-### 13. Remote Network Interaction; Use with the GNU General Public License
-
-Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software. This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-### 14. Revised Versions of this License
-
-The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License “or any later version” applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation. If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-### 15. Disclaimer of Warranty
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-### 16. Limitation of Liability
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-### 17. Interpretation of Sections 15 and 16
-
-If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-##
END OF TERMS AND CONDITIONS
-
-###
How to Apply These Terms to Your New Programs
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the “copyright” line and a pointer to where the full notice is found.
-
-
- Copyright (C)
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU Affero General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU Affero General Public License for more details.
-
- You should have received a copy of the GNU Affero General Public License
- along with this program. If not, see .
-
-Also add information on how to contact you by electronic and paper mail.
-
-If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source. For example, if your program is a web application, its
-interface could display a “Source” link that leads users to an archive
-of the code. There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-You should also get your employer (if you work as a programmer) or school,
-if any, to sign a “copyright disclaimer” for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<>.
\ No newline at end of file
diff --git a/doc/themes/next/docs/ALGOLIA-SEARCH.md b/doc/themes/next/docs/ALGOLIA-SEARCH.md
deleted file mode 100644
index 998d8dcec..000000000
--- a/doc/themes/next/docs/ALGOLIA-SEARCH.md
+++ /dev/null
@@ -1,87 +0,0 @@
-Algolia Search
-
-
-NexT provides Algolia search plugin for index your hexo website content. To use this feature, make sure that the version of NexT you are using is after the v5.1.0 release. What you should note here is that only turn on `enable` of `algolia_search` in `next/_config.yml` cannot let you use the algolia search correctly, you need to install corresponding [Hexo Algolia](https://github.com/oncletom/hexo-algolia) plugin to seach your website with Algolia. Follow the steps described below to complete the installation of Algolia search.
-
-1. Register at [Algolia](https://www.algolia.com/), you can log in directly using GitHub or Google Account. Upon Customer’s initial sign-up for an Account, Customer will have a free, fourteen (14) day evaluation period (the “Evaluation Period”) for the Algolia Services commencing on the Effective Date, subject to the limitations on Algolia’s website. After that, Algolia offers a free, branded version for up to 10k records and 100k operations per month.
-
-1. If a tutorial pops up, you can skip it. Go straight to create an `Index` which will be used later.
-
- 
-
-1. Algolia requires users to upload their search index data either manually or via provided APIs. Install and configure [Hexo Algolia](https://github.com/oncletom/hexo-algolia) in your Hexo directory. This plugin will index your site and upload selected data to Algolia.
-
- ```
- $ cd hexo
- $ npm install --save hexo-algolia
- ```
-
-1. Go to the `API Keys` page and find your credentials. You will need the `Application ID` and the `Search-only API key` in the following sections. The `Admin API key` need to keep confidential. Never store your Admin API Key as apiKey in the` _config.yml` file: it would give full control of your Algolia index to others and you don't want to face the consequences.
-
- 
-
-1. In the `API Keys` page, click the `ALL API KEYS` and the `edit` option in the created APIKEY to activate a pop-up box where you can setup authorizations and restrictions with a great level of precision. Check `Add records`, `Delete records`, `List indices`, `Delete index` features in ACL permissions that will be allowed for the given API key. And then click the `Update` button.
-
- 
- 
-
-1. In your site's `_config.yml`, add the following configuration and replace the `applicationID` & `apiKey` & `indexName` with corresponding fields obtained at Algolia.
-
- ```yml
- algolia:
- applicationID: 'Application ID'
- apiKey: 'Search-only API key'
- indexName: 'indexName'
- chunkSize: 5000
- ```
-
-1. Run the following command to upload index data, keep a weather eye out the output of the command.
-
- ```
- $ export HEXO_ALGOLIA_INDEXING_KEY=Search-Only API key # Use Git Bash
- # set HEXO_ALGOLIA_INDEXING_KEY=Search-Only API key # Use Windows command line
- $ hexo clean
- $ hexo algolia
- ```
-
- 
-
-1. Change dir to NexT directory, and install module to `source/lib` directory.
-
- ```
- $ cd themes/next
- $ git clone https://github.com/theme-next/theme-next-algolia-instant-search source/lib/algolia-instant-search
- ```
-
- If you want to use the CDN instead of clone this repo, then need to **set vendors** in NexT `_config.yml` file:
- ```yml
- vendors:
- ...
- # Internal version: 1
- # https://www.algolia.com
- algolia_instant_js: https://cdn.jsdelivr.net/npm/instantsearch.js@2.4.1/dist/instantsearch.js
- algolia_instant_css: https://cdn.jsdelivr.net/npm/instantsearch.js@2.4.1/dist/instantsearch.min.css
- ...
- ```
-
-1. In `next/_config.yml`, turn on `enable` of `algolia_search`. At the same time, you need to **turn off other search plugins** like Local Search. You can also adjust the text in `labels` according to your needs.
-
- ```yml
- # Algolia Search
- algolia_search:
- enable: true
- hits:
- per_page: 10
- labels:
- input_placeholder: Search for Posts
- hits_empty: "We didn't find any results for the search: ${query}"
- hits_stats: "${hits} results found in ${time} ms"
- ```
-
-Known Issues
-
-1. The latest version of the [Hexo-Algolia](https://github.com/oncletom/hexo-algolia) plugin removes the content indexing feature, given Algolia's free account limitation.
-
-1. The [Hexo-Algoliasearch](https://github.com/LouisBarranqueiro/hexo-algoliasearch) plugin provides content indexing functionality, but requires the replacement of keywords in the NEXT theme. The same problem exists with `Record Too Big` for Algolia's free account.
- - Replace all `applicationID` in `source/js/algolia-search.js` with `appId`
- - Replace all `applicationID` in `layout/_partials/head/head.swig` with `appId`
diff --git a/doc/themes/next/docs/AUTHORS.md b/doc/themes/next/docs/AUTHORS.md
deleted file mode 100644
index f54eef7bb..000000000
--- a/doc/themes/next/docs/AUTHORS.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# «NexT» Authors
-
-NexT theme was initially developed by:
-
-- **IIssNaN**: [NexT](https://github.com/iissnan/hexo-theme-next) (2014 - 2017)
-
-With collaborators from initially repository:
-
-- **Ivan.Nginx**: [DIFF highlight](https://github.com/iissnan/hexo-theme-next/pull/1079),
- [HyperComments](https://github.com/iissnan/hexo-theme-next/pull/1155),
- [`{% note %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1160),
- [`seo` option](https://github.com/iissnan/hexo-theme-next/pull/1311),
- [`{% button %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1328),
- [VK API](https://github.com/iissnan/hexo-theme-next/pull/1381),
- [WordCount plugin support](https://github.com/iissnan/hexo-theme-next/pull/1381),
- [Yandex verification option](https://github.com/iissnan/hexo-theme-next/pull/1381),
- [`{% exturl %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1438),
- [`b2t` option](https://github.com/iissnan/hexo-theme-next/pull/1438),
- [`scrollpercent` option](https://github.com/iissnan/hexo-theme-next/pull/1438),
- [`save_scroll` option](https://github.com/iissnan/hexo-theme-next/pull/1574),
- [Star rating](https://github.com/iissnan/hexo-theme-next/pull/1649),
- [`mobile_layout_economy` option](https://github.com/iissnan/hexo-theme-next/pull/1697),
- [`{% tabs %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1697),
- [`{% label %}` tag](https://github.com/iissnan/hexo-theme-next/pull/1697),
- [**`Gemini`** scheme](https://github.com/iissnan/hexo-theme-next/pull/1697),
- [Menu & Sidebar icons in 1 line](https://github.com/iissnan/hexo-theme-next/pull/1830),
- [Sidebar scrollable](https://github.com/iissnan/hexo-theme-next/pull/1898),
- [Responsive favicons](https://github.com/iissnan/hexo-theme-next/pull/1898)
- and many other [PR's with fixes and enhancements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Aivan-nginx)
-- **Acris**: [Many PR's with fixes and updates](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3AAcris)
-
-And best contributors from initially repository:
-
-- **Rainy**: [Gentie comments](https://github.com/iissnan/hexo-theme-next/pull/1301),
- [Han](https://github.com/iissnan/hexo-theme-next/pull/1598)
- and many [PR's with fixes and optimizations](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Ageekrainy)
-- **Jeff**: [Local search](https://github.com/iissnan/hexo-theme-next/pull/694)
- and many [PR's with fixes and improvements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Aflashlab)
-- **Haocen**: [Footer enhancements](https://github.com/iissnan/hexo-theme-next/pull/1886)
- and some other [PR's with improvements](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3AHaocen)
-- **uchuhimo**: [Greatest enhancements for local search](https://github.com/iissnan/hexo-theme-next/pulls?utf8=%E2%9C%93&q=is%3Apr%20author%3Auchuhimo)
-- **Kei**: [Change static file setting to support subdirectory](https://github.com/iissnan/hexo-theme-next/pull/4)
-- **Jolyon**: [Swiftype](https://github.com/iissnan/hexo-theme-next/pull/84)
-- **xirong**: [404 page](https://github.com/iissnan/hexo-theme-next/pull/126)
-- **PinkyJie**: [Fix Swiftype](https://github.com/iissnan/hexo-theme-next/pull/132)
-- **Tim Kuijsten**: [Split javascript into separate files](https://github.com/iissnan/hexo-theme-next/pull/152)
-- **iamwent**: [Friendly links](https://github.com/iissnan/hexo-theme-next/pull/250)
-- **arao lin**: [Option to lazyload images](https://github.com/iissnan/hexo-theme-next/pull/269)
-- **Konstantin Pavlov**: [Microdata, opengraph and other semantic features](https://github.com/iissnan/hexo-theme-next/pull/276)
-- **Gary**: [FastClick](https://github.com/iissnan/hexo-theme-next/pull/324)
-- **Octavian**: [Baidu site vertification](https://github.com/iissnan/hexo-theme-next/pull/367)
-- **Henry Chang**: [Facebook SDK](https://github.com/iissnan/hexo-theme-next/pull/410)
-- **XiaMo**: [LeanCloud visitors](https://github.com/iissnan/hexo-theme-next/pull/439)
-- **iblogc**: [Fix UA in Duoshuo](https://github.com/iissnan/hexo-theme-next/pull/489)
-- **Vincent**: [Automatic headline ID's](https://github.com/iissnan/hexo-theme-next/pull/588)
-- **cissoid**: [Tencent analytics](https://github.com/iissnan/hexo-theme-next/pull/603)
-- **CosmoX**: [AddThis](https://github.com/iissnan/hexo-theme-next/pull/660)
-- **Jason Guo**: [Reward for post](https://github.com/iissnan/hexo-theme-next/pull/687)
-- **Jerry Bendy**: [CNZZ counter](https://github.com/iissnan/hexo-theme-next/pull/712)
-- **Hui Wang**: [Wechat subscriber](https://github.com/iissnan/hexo-theme-next/pull/788)
-- **PoonChiTim**: [Busuanzi counter](https://github.com/iissnan/hexo-theme-next/pull/809)
-- **hydai**: [Facebook comments](https://github.com/iissnan/hexo-theme-next/pull/925)
-- **OAwan**: [`canonical` option](https://github.com/iissnan/hexo-theme-next/pull/931)
-- **Jim Zenn**: [Google Calendar](https://github.com/iissnan/hexo-theme-next/pull/1167)
-- **Abner Chou**: [Disqus improvements](https://github.com/iissnan/hexo-theme-next/pull/1173)
-- **Igor Fesenko**: [Application Insights](https://github.com/iissnan/hexo-theme-next/pull/1257)
-- **jinfang**: [Youyan comments](https://github.com/iissnan/hexo-theme-next/pull/1324)
-- **AlynxZhou**: [`canvas_nest` option](https://github.com/iissnan/hexo-theme-next/pull/1327)
-- **aleon**: [Tencent MTA](https://github.com/iissnan/hexo-theme-next/pull/1408)
-- **asmoker**: [LiveRe comments](https://github.com/iissnan/hexo-theme-next/pull/1415)
-- **Jacksgong**: [Copyright on posts](https://github.com/iissnan/hexo-theme-next/pull/1497)
-- **zhaiqianfeng**: [Changyan comments](https://github.com/iissnan/hexo-theme-next/pull/1514)
-- **zproo**: [`canvas_ribbon` option](https://github.com/iissnan/hexo-theme-next/pull/1565)
-- **jjandxa**: [`three_waves`](https://github.com/iissnan/hexo-theme-next/pull/1534),
- [`canvas_lines` and `canvas_sphere`](https://github.com/iissnan/hexo-theme-next/pull/1595) options
-- **shenzekun**: [Load bar at the top](https://github.com/iissnan/hexo-theme-next/pull/1689)
-- **elkan1788**: [Upgrade jiathis share](https://github.com/iissnan/hexo-theme-next/pull/1796)
-- **xCss**: [Valine comment system support](https://github.com/iissnan/hexo-theme-next/pull/1811)
-- **Julian Xhokaxhiu**: [`override` option](https://github.com/iissnan/hexo-theme-next/pull/1861)
-- **LEAFERx**: [NeedMoreShare2](https://github.com/iissnan/hexo-theme-next/pull/1913)
-- **aimingoo & LEAFERx**: [Gitment supported with Mint](https://github.com/iissnan/hexo-theme-next/pull/1919)
-- **LeviDing**: [Fix the bug of Gitment](https://github.com/iissnan/hexo-theme-next/pull/1944)
-- **maple3142**: [Firestore visitor counter](https://github.com/iissnan/hexo-theme-next/pull/1978)
-
-It lives on as an open source project with many contributors, a self updating list is [here](https://github.com/theme-next/hexo-theme-next/graphs/contributors).
-
-P.S. If you was do some useful pulls/commits in original repository and you are not in list, let me know and you will be added here.
diff --git a/doc/themes/next/docs/DATA-FILES.md b/doc/themes/next/docs/DATA-FILES.md
deleted file mode 100644
index bdf8ab002..000000000
--- a/doc/themes/next/docs/DATA-FILES.md
+++ /dev/null
@@ -1,61 +0,0 @@
-Data Files
-
-Currently, it is not smooth to update NexT theme from pulling or downloading new releases. It is quite often running into conflict status when updating NexT theme via `git pull`, or need to merge configurations manually when upgrading to new releases.
-
- At present, NexT encourages users to store some options in site's `_config.yml` and other options in theme's `_config.yml`. This approach is applicable, but has some drawbacks:
-1. Configurations are splitted into two pieces
-2. Users may be confused which place should be for options
-
-In order to resolve this issue, NexT will take advantage of Hexo [Data files](https://hexo.io/docs/data-files.html). Because Data files is introduced in Hexo 3, so you need upgrade Hexo to 3.0 (or above) to use this feature.
-
-If you prefer Hexo 2.x, you can still use the old approach for configurations. NexT is still compatible with Hexo 2.x (but errors are possible).
-
-Option 1: Hexo-Way
-
-With this way, all your configurations locate in main hexo config file (`hexo/_config.yml`), you don't need to touch `next/_config.yml` or create any new files. But you must preserve double spaces indents within `theme_config` option.
-
-If there are any new options in new releases, you just need to copy those options from `next/_config.yml`, paste into `hexo/_config.yml` and set their values to whatever you want.
-
-### Usage
-
-1. Check for no exists `hexo/source/_data/next.yml` file (delete it if exists).
-2. Copy needed NexT theme options from theme's `next/_config.yml` into `hexo/_config.yml`, then\
- 2.1. Move all this settings to the right with two spaces (in Visual Studio Code: select all strings, CTRL + ]).\
- 2.2. Add `theme_config:` parameter above all this settings.
-
-### Useful links
-
-* [Hexo Configuration](https://hexo.io/docs/configuration.html)
-* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
-
-Option 2: NexT-Way
-
-With this way, you can put all your configurations into one place (`source/_data/next.yml`), you don't need to touch `next/_config.yml`.
-But option may not accurately procces all hexo external libraries with their additional options (for example, `hexo-server` module options may be readed only in default hexo config).
-
-If there are any new options in new releases, you just need to copy those options from `next/_config.yml`, paste into `_data/next.yml` and set their values to whatever you want.
-
-### Usage
-
-1. Please ensure you are using Hexo 3 (or above).
-2. Create an file named `next.yml` in site's `hexo/source/_data` directory (create `_data` directory if it did not exists).
-
-And after that steps there are 2 variants, need to choose only one of them and resume next steps.
-
-* **Variant 1: `override: false` (default)**:
-
- 1. Check your `override` option in default NexT config, it must set on `false`.\
- In `next.yml` it must not be defined or set on `false` too.
- 2. Copy needed options from both site's `_config.yml` and theme's `_config.yml` into `hexo/source/_data/next.yml`.
-
-* **Variant 2: `override: true`**:
-
- 1. In `next.yml` set `override` option on `true`.
- 2. Copy **all** NexT theme options from theme's `next/_config.yml` into `hexo/source/_data/next.yml`.
-
-3. Then, in main site's `hexo/_config.yml` need to define `theme: next` option (and if needed, `source_dir: source`).
-4. Use standart parameters to start server, generate or deploy (`hexo clean && hexo g -d && hexo s`).
-
-### Useful links
-
-* [NexT Issue #328](https://github.com/iissnan/hexo-theme-next/issues/328)
diff --git a/doc/themes/next/docs/INSTALLATION.md b/doc/themes/next/docs/INSTALLATION.md
deleted file mode 100644
index 3f229994d..000000000
--- a/doc/themes/next/docs/INSTALLATION.md
+++ /dev/null
@@ -1,120 +0,0 @@
-Installation
-
-Step 1 → Go to Hexo dir
-
-Change dir to **hexo root** directory. There must be `node_modules`, `source`, `themes` and other directories:
- ```sh
- $ cd hexo
- $ ls
- _config.yml node_modules package.json public scaffolds source themes
- ```
-
-Step 2 → Get NexT
-
-Download theme from GitHub.
-There are 3 options to do it, need to choose only one of them.
-
-### Option 1: Download [latest release version][releases-latest-url]
-
- At most cases **stable**. Recommended for beginners.
-
- * Install with [curl & tar & wget][curl-tar-wget-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -s https://api.github.com/repos/theme-next/hexo-theme-next/releases/latest | grep tarball_url | cut -d '"' -f 4 | wget -i - -O- | tar -zx -C themes/next --strip-components=1
- ```
- This variant will give to you **only latest release version** (without `.git` directory inside).\
- So, there is impossible to update this version with `git` later.\
- Instead you always can use separate configuration (e.g. [data-files][docs-data-files-url]) and download new version inside old directory (or create new directory and redefine `theme` in Hexo config), without losing your old configuration.
-
-### Option 2: Download [tagged release version][releases-url]
-
- In rare cases useful, but not recommended.\
- You must define version. Replace `v6.0.0` with any version from [tags list][tags-url].
-
- * Variant 1: Install with [curl & tar][curl-tar-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball/v6.0.0 | tar -zxv -C themes/next --strip-components=1
- ```
- Same as above under `curl & tar & wget` variant, but will download **only concrete version**.
-
- * Variant 2: Install with [git][git-url]:
-
- ```sh
- $ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
- ```
- This variant will give to you the **defined release version** (with `.git` directory inside).\
- And in any time you can switch to any tagged release, but with limit to defined version.
-
-### Option 3: Download [latest master branch][download-latest-url]
-
- May be **unstable**, but includes latest features. Recommended for advanced users and for developers.
-
- * Variant 1: Install with [curl & tar][curl-tar-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball | tar -zxv -C themes/next --strip-components=1
- ```
- Same as above under `curl & tar & wget` variant, but will download **only latest master branch version**.\
- At some cases useful for developers.
-
- * Variant 2: Install with [git][git-url]:
-
- ```sh
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next
- ```
-
- This variant will give to you the **whole repository** (with `.git` directory inside).\
- And in any time you can [update current version with git][update-with-git-url] and switch to any tagged release or on latest master or any other branch.\
- At most cases useful as for users and for developers.
-
- Get tags list:
-
- ```sh
- $ cd themes/next
- $ git tag -l
- …
- v6.0.0
- v6.0.1
- v6.0.2
- ```
-
- For example, you want to switch on `v6.0.1` [tagged release version][tags-url]. Input the following command:
-
- ```sh
- $ git checkout tags/v6.0.1
- Note: checking out 'tags/v6.0.1'.
- …
- HEAD is now at da9cdd2... Release v6.0.1
- ```
-
- And if you want to switch back on [master branch][commits-url], input this command:
-
- ```sh
- $ git checkout master
- ```
-
-Step 3 → Set it up
-
-Set theme in main **hexo root config** `_config.yml` file:
-
-```yml
-theme: next
-```
-
-[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
-[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
-[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
-[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
-[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
-
-[git-url]: http://lmgtfy.com/?q=linux+git+install
-[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
-[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
-
-[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/README.md#update
-[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/DATA-FILES.md
diff --git a/doc/themes/next/docs/LEANCLOUD-COUNTER-SECURITY.md b/doc/themes/next/docs/LEANCLOUD-COUNTER-SECURITY.md
deleted file mode 100644
index 9a6c8a0dd..000000000
--- a/doc/themes/next/docs/LEANCLOUD-COUNTER-SECURITY.md
+++ /dev/null
@@ -1,177 +0,0 @@
-Before you make the config, please upgrade your NexT version to v6.0.6 or greater.
-
-Please note the difference between **site config file** and **theme config file**
-
----
-
-# Sign up to Leancloud and create an app
-- Go to Leancloud website [leancloud.cn](leancloud.cn) and sign up to Leancloud. Then login.
-- Click `1` to enter the console:
-
- 
-
-- Then click `1` to create an app:
-
- 
-
-- Type your app name in `1` in the pop up window(eg. "test"), then choose `2`, which means developer's plan, and then click `3` to create the app:
-
- 
-
-# Create Counter class and enable plugin in NexT
-- Click `1`(app name) to enter the app manage page:
-
- 
-
-- then click `1` to create a class for counter:
-
- 
-
-- Type `Counter` in the pop up window in `1`, check `2`, then click `3`:
-
- 
-
-- Click `1` to enter the app setting, then click `2`:
-
- 
-
-- Paste `App ID` and `App Key` to **theme config file**`_config.yml` like this:
- ```yml
- leancloud_visitors:
- enable: true
- app_id: <>
- app_key: <>
- # Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
- security: true
- betterPerformance: false
- ```
-
-- Set domain whitelist: Click`1`, then type your domain into `2`(**protocol, domain and port should be exactly the same**):
-
- 
-
-# Deploy web engine to avoid your data being changed illegally
-- Click `1 -> 2 -> 3` by order
-
- 
-
-- Click`1`:
-
- 
-
-- In the pop up window, click `1` to choose type `Hook`, then choose`beforeUpdate` in `2`, choose `Counter` in `3`. Paste code below into `4`, then click `5` to save it:
- ```javascript
- var query = new AV.Query("Counter");
- if (request.object.updatedKeys.indexOf('time') !== -1) {
- return query.get(request.object.id).then(function (obj) {
- if (obj.get("time") > request.object.get("time")) {
- throw new AV.Cloud.Error('Invalid update!');
- }
- return request.object.save();
- });
- }
- ```
-
- 
-
-- Click `1` to deploy after the message in the red rect shows up:
-
- 
-
-- Click `1` in the pop up：
-
- 
-
-- Click `1` to close the pop up window after the message in the red rect shows up:
-
- 
-
-# Set access control for your database
-- Open **theme config file**`_config.yml`, set `leancloud_visitors: security` to `true`:
- ```yml
- leancloud_visitors:
- enable: true
- app_id: <>
- app_key: <>
- # Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
- security: true
- betterPerformance: false
- ```
-
- **Explaination for `betterPerformance`:**
- Because the Leancloud developer's plan has limits in requst thread amount and running time, counter number may be very slow to load in some times. If set `betterPerformance` to true, counter number will be displayed quickly by assuming the request is accepted normally.
-
-- Open cmd then switch to **root path of site**, type commands to install `hexo-leancloud-counter-security` plugin:
- ```
- npm install hexo-leancloud-counter-security --save
- ```
-
-- Open **site config file**`_config.yml`, add those config:
- ```yml
- leancloud_counter_security:
- enable_sync: true
- app_id: <>
- app_key: <
- username:
- password:
- ```
-
-- Type command:
- ```
- hexo lc-counter register <> <>
- ```
- or
- ```
- hexo lc-counter r <> <>
- ```
-
- Change `<>` and `<>` to your own username and password (no need to be the same as leancloud account). They will be used in the hexo deploying.
-
- - Open **site config file**`_config.yml`, change `<>` and `<>`to those you set above:
- ```yml
- leancloud_counter_security:
- enable_sync: true
- app_id: <>
- app_key: <
- username: <> # will be asked while deploying if be left blank
- password: <> # recommend to leave it blank for security, will be asked while deploying if be left blank
- ```
-
-- Add the deployer in the `deploy` of **site config file**`_config.yml`:
- ```yml
- deploy:
- - type: git
- repo: // your repo
- ...
- - type: leancloud_counter_security_sync
- ```
-
-- Return to the Leancloud console. Click `1 -> 2`, check if there is a record added in the _User (the img below is using username "admin" for example):
-
- 
-
-- Click `1 -> 2 -> 3` by order:
-
- 
-
-- Click `1`(add_fields), then choose `2`:Do as below "create" setting(choose the user you create):
-
- 
-
-- click `1`(create), then choose `2`, type the username in `3`, then click `4 -> 5`:
-
- 
-
- Now your page should be similar to this img after finishing the step.
-
- 
-
-- Click `1`(delete), then choose `2`:
-
- 
-
-Now the bug is fixed.
-
----
-
-See detailed version here: https://leaferx.online/2018/03/16/lc-security-en/
diff --git a/doc/themes/next/docs/LICENSE.txt b/doc/themes/next/docs/LICENSE.txt
deleted file mode 100644
index 40a71e830..000000000
--- a/doc/themes/next/docs/LICENSE.txt
+++ /dev/null
@@ -1,56 +0,0 @@
- «NexT» – Elegant and powerful theme for Hexo.
-
- Copyright © 2017 «NexT» (github.com/theme-next/hexo-theme-next).
-
- Detail attribution information for «NexT»
- is contained in the 'docs/AUTHORS.md' file.
-
- This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU Affero General Public License version 3
-as published by the Free Software Foundation with the addition of the
-following permission added to Section 15 as permitted in Section 7(a):
-FOR ANY PART OF THE COVERED WORK IN WHICH THE COPYRIGHT IS OWNED BY «NEXT»,
-«NEXT» DISCLAIMS THE WARRANTY OF NON INFRINGEMENT OF THIRD PARTY RIGHTS.
-
- This program is distributed in the hope that it will be useful, but
-WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
-or FITNESS FOR A PARTICULAR PURPOSE.
-See the GNU Affero General Public License for more details.
-You should have received a copy of the GNU Affero General Public License
-along with this program; if not, see: https://www.gnu.org/licenses/agpl.txt
-
- In accordance with Section 7(b) of the GNU Affero General Public License:
-
- a) It is not necessary to specify copyright in each source file of
- this program because GitHub fully save commits of all modified files
- with their authors and provides to see for this changes publicly.
-
- b) For any part of the covered work in which the copyright not specified,
- except of third party libraries ('source/lib/*') and '*custom.*' files,
- will mean this part owned by «NexT» in accord with terms in this file.
-
-* c) A covered work must retain «NexT» official website link
- (https://theme-next.org) in footer section of every website created,
- modified or manipulated by using «NexT».
- «NexT» theme configuration must be:
- ```
- footer:
- theme:
- enable: true
- ```
- Collaborators, best contributors and all authors specified in the
- 'docs/AUTHORS.md' file of «NexT» repository under the
- 'https://github.com/theme-next' organization can ignore theme info link
- requirements.
-
- Anyone can be released from the requirements of the license by purchasing
-a commercial license. Buying such a license is mandatory as soon as you
-develop commercial activities involving the «NexT» software without
-disclosing the source code of your own applications.
-These activities include:
- 1. Access to private repository with various premium features.
- 2. Priority support for resolve all possible issues with «NexT».
- 3. Priority support for implement all possible features to «NexT».
-
- For more information, please contact «NexT» Organization at this
-address: support@theme-next.org
diff --git a/doc/themes/next/docs/MATH.md b/doc/themes/next/docs/MATH.md
deleted file mode 100644
index 76498ff04..000000000
--- a/doc/themes/next/docs/MATH.md
+++ /dev/null
@@ -1,286 +0,0 @@
-Math Equations
-
-NexT provides two render engines for displaying Math Equations.
-
-If you choose to use this feature, you don't need to manually import any JS or CSS. You just need to turn on `enable` of `math` and choose a render `engine` for it (located in `next/_config.yml`):
-
-```yml
-math:
- enable: true
- ...
- engine: mathjax
-```
-
-Notice: only turning on `enable` of `math` **cannot let you see the displayed equations correctly**, you need to install the **corresponding Hexo Renderer** to fully support the display of Math Equations. The corresponding Hexo Renderer per engine will be provided below.
-
-Provided Render Engine
-
-For now, NexT provides two Render Engines: [MathJax](https://www.mathjax.org/) and [Katex](https://khan.github.io/KaTeX/) (default is MathJax).
-
-### MathJax (default)
-
-If you use MathJax to render Math Equations, you need to use **only one of them**: [hexo-renderer-pandoc](https://github.com/wzpan/hexo-renderer-pandoc) or [hexo-renderer-kramed](https://github.com/sun11/hexo-renderer-kramed).
-
-Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and install one of the renderer above:
-
-```sh
-npm un hexo-renderer-marked --save
-npm i hexo-renderer-pandoc --save # or hexo-renderer-kramed
-```
-
-Secondly, in `next/_config.yml`, turn on `enable` of `math` and choose `mathjax` as `engine`.
-
-```yml
-math:
- enable: true
- ...
- engine: mathjax
- #engine: katex
-```
-
-Finally, run standard Hexo generate, deploy process or start the server:
-
-```sh
-hexo clean && hexo g -d
-# or hexo clean && hexo s
-```
-
-#### Numbering and referring equations in MathJax
-
-In the new version of NexT, we have added feature to automatically number equations and to refer to equations. We briefly describe how to use this feature below.
-
-In general, to make the automatic equation numbering work, you have to wrap your LaTeX equations in `equation` environment. Using the plain old style (i.e., wrap an equation with two dollar signs in each side) will not work. How to refer to an equation? Just give a `\label{}` tag and then in your later text, use `\ref{}` or `\eqref{}` to refer it. Using `\eqref{}` is preferred since if you use `\ref{}`, there are no parentheses around the equation number. Below are some of the common scenarios for equation numbering.
-
-For simple equations, use the following form to give a tag,
-
-```latex
-$$\begin{equation}
-e=mc^2
-\end{equation}\label{eq1}$$
-```
-
-Then, you can refer to this equation in your text easily by using something like
-
-```
-the famous matter-energy equation $\eqref{eq1}$ proposed by Einstein ...
-```
-
-For multi-line equations, inside the `equation` environment, you can use the `aligned` environment to split it into multiple lines:
-
-```latex
-$$\begin{equation}
-\begin{aligned}
-a &= b + c \\
- &= d + e + f + g \\
- &= h + i
-\end{aligned}
-\end{equation}\label{eq2}$$
-```
-
-We can use `align` environment to align multiple equations. Each of these equations will get its own numbers.
-
-```
-$$\begin{align}
-a &= b + c \label{eq3} \\
-x &= yz \label{eq4}\\
-l &= m - n \label{eq5}
-\end{align}$$
-```
-
-In the `align` environment, if you do not want to number one or some equations, just [use `\nonumber`](https://tex.stackexchange.com/questions/17528/show-equation-number-only-once-in-align-environment) right behind these equations. Like the following:
-
-```latex
-$$\begin{align}
--4 + 5x &= 2+y \nonumber \\
- w+2 &= -1+w \\
- ab &= cb
-\end{align}$$
-```
-
-Sometimes, you want to use more “exotic” style to refer your equation. You can use `\tag{}` to achieve this. For example:
-
-```latex
-$$x+1\over\sqrt{1-x^2} \tag{i}\label{eq_tag}$$
-```
-
-For more information, you can visit the [official MathJax documentation on equation numbering](http://docs.mathjax.org/en/latest/tex.html#automatic-equation-numbering). You can also visit this [post](https://jdhao.github.io/2018/01/25/hexo-mathjax-equation-number/) for more details.
-
-### Katex
-
-The Katex engine is a **much faster** math render engine compared to MathJax. And it could survive without JavaScript.
-
-But, what Katex supports is not as full as MathJax. You could check it from the Useful Links below.
-
-If you use Katex to render Math Equations, you need to use **only one of those renderer**: [hexo-renderer-markdown-it-plus](https://github.com/CHENXCHEN/hexo-renderer-markdown-it-plus) or [hexo-renderer-markdown-it](https://github.com/hexojs/hexo-renderer-markdown-it).
-
-Firstly, you need to uninstall the original renderer `hexo-renderer-marked`, and **install one of selected above**.
-
-```sh
-npm un hexo-renderer-marked --save
-npm i hexo-renderer-markdown-it-plus --save
-# or hexo-renderer-markdown-it
-```
-
-Secondly, in `next/_config.yml`, turn on `enable` option of `math` and choose `katex` as render `engine`.
-
-```yml
-math:
- enable: true
- ...
- #engine: mathjax
- engine: katex
-```
-
-Finally, run the standard Hexo generate, deploy process or start the server:
-
-```sh
-hexo clean && hexo g -d
-# or hexo clean && hexo s
-```
-
-#### If you use hexo-renderer-markdown-it
-
-If you use `hexo-renderer-markdown-it`，you also need to add `markdown-it-katex` as its plugin：
-
-```
-npm i markdown-it-katex --save
-```
-
-And then in `hexo/_config.yml` you need to add `markdown-it-katex` as a plugin for `hexo-renderer-markdown-it`:
-
-```yml
-# config of hexo-renderer-markdown-it
-markdown:
- render:
- html: true
- xhtmlOut: false
- breaks: true
- linkify: true
- typographer: true
- quotes: '“”‘’'
- plugins:
- - markdown-it-katex
-```
-
-#### Known Bugs
-
-1. Firstly, please check [Common Issues](https://github.com/Khan/KaTeX#common-issues) of Katex.
-2. Displayed Math (i.e. `$$...$$`) needs to started with new clear line.\
- In other words: you must not have any characters (except of whitespaces) **before the opening `$$` and after the ending `$$`** ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
-3. Don't support Unicode ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
-4. Inline Math (..`$...$`) must not have white spaces **after the opening `$` and before the ending `$`** ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509)).
-5. If you use math in Heading (i.e. `## Heading`).\
- Then in corresponding TOC item it will show the related LaTex code 3 times ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359018694)).
-6. If you use math in your post's title, it will not be rendered ([comment #32](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359142879)).
-
-We currently use Katex 0.7.1, some of those bugs might be caused by the outdated version of Katex we use.
-
-But, as what is described in the beginning, the render of Math Equations relies on Hexo Renderer. Currently, Katex-related renderers only support Katex version until 0.7.1.
-
-We will continuously monitor the updates of corresponding renderers, if there is a renderer which supports newer version of Katex, we will update the Katex we use.
-
-### Useful Links
-
-* [Speed test between Katex and MathJax](https://www.intmath.com/cg5/katex-mathjax-comparison.php)
-* [Function support by Katex](https://khan.github.io/KaTeX/function-support.html)
-
-Configuration Specifications
-
-ATTENTION! When you edit those configs, **don't change indentation!**
-
-Currently, all NexT config use **2 spaces indents**.
-
-If your content of config is put just directly after the config name, then a space is needed between the colon and the config content (i.e. `enable: true`)
-
-```yml
-# Math Equations Render Support
-math:
- enable: false
-
- # Default(true) will load mathjax/katex script on demand
- # That is it only render those page who has 'mathjax: true' in Front Matter.
- # If you set it to false, it will load mathjax/katex srcipt EVERY PAGE.
- per_page: true
-
- engine: mathjax
- #engine: katex
-
- # hexo-rendering-pandoc (or hexo-renderer-kramed) needed to full MathJax support.
- mathjax:
- # For newMathJax CDN (cdnjs.cloudflare.com) with fallback to oldMathJax (cdn.mathjax.org).
- cdn: //cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML
- # For direct link to MathJax.js with CloudFlare CDN (cdnjs.cloudflare.com).
- #cdn: //cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-MML-AM_CHTML
-
- # hexo-renderer-markdown-it-plus (or hexo-renderer-markdown-it with markdown-it-katex plugin)
- # needed to full Katex support.
- katex:
- # Use Katex 0.7.1 as default
- cdn: //cdnjs.cloudflare.com/ajax/libs/KaTeX/0.7.1/katex.min.css
- # If you want to try the latest version of Katex, use one below instead
- #cdn: //cdn.jsdelivr.net/katex/latest/katex.min.css
-```
-
-### enable
-
-`true` or `false`, default is `false`.
-
-`true` to turn on render of Math Equations, `false` to turn off it.
-
-### per_page
-
-`true` or `false`, default is `true`.
-
-This option is to control whether to render Math Equations every page.
-
-The behavior of default (`true`) is to render Math Equations **on demand**.
-
-It will only render those posts which have `mathjax: true` in their Front Matter.
-
-For example:
-
-```md
-
----
-title: 'Will Render Math'
-mathjax: true
----
-....
-```
-
-```md
-
----
-title: 'Not Render Math'
-mathjax: false
----
-....
-```
-
-```md
-
----
-title: 'Not Render Math Either'
----
-....
-```
-
-When you set it to `false`, the math will be rendered on **EVERY PAGE**.
-
-### cdn
-
-Both MathJax and Katex provide a config `cdn`, if you don't know what is `cdn`, **do not touch it**.
-
-Firstly, both MathJax and Katex use the [jsDelivr](https://www.jsdelivr.com/) as the default CDN.
-
-The reason that jsDelivr is chosen is because it is fast everywhere, and jsDelivr has the valid ICP license issued by the Chinese government, it can be accessed in China pretty well.
-
-And we also provide other optional CDNs, including the famous [CDNJS](https://cdnjs.com/).
-
-For MathJax, we are currently using version 2.7.1.
-
-For Katex, due to the problem described above, we are now using version 0.7.1.
-
-If you want to try the other CDNs not included in the optional list, you must use the corresponding version.
-
-Particularly, if you are a Chinese blogger or most of your visits come from China, please note that **the CDNJS is blocked in some parts of China**, don't use it as your CDN.
diff --git a/doc/themes/next/docs/UPDATE-FROM-5.1.X.md b/doc/themes/next/docs/UPDATE-FROM-5.1.X.md
deleted file mode 100644
index 93ae14ec0..000000000
--- a/doc/themes/next/docs/UPDATE-FROM-5.1.X.md
+++ /dev/null
@@ -1,19 +0,0 @@
-Update from NexT v5.1.x
-
-There are no hard breaking changes between 5.1.x and 6.0.x versions. It's change major version to 6 because:
-
-1. Main repo was rebased from [iissnan's](https://github.com/iissnan/hexo-theme-next) profile to [theme-next](https://github.com/theme-next) organization.
-2. Most libraries under the `next/source/lib` directory was moved out to [external repos under NexT organization](https://github.com/theme-next).
-3. 3rd-party plugin [`hexo-wordcount`](https://github.com/willin/hexo-wordcount) was replaced by [`hexo-symbols-count-time`](https://github.com/theme-next/hexo-symbols-count-time) because `hexo-symbols-count-time` no have any external nodejs dependencies, no have [language filter](https://github.com/willin/hexo-wordcount/issues/7) which causes better performance on speed at site generation.
-
-So, i suggest to update from version 5 to version 6 in this way:
-
-1. You don't touch old `next` dir and just do some copies of NexT files:\
- 1.1. `config.yml` or `next.yml` (if you used [data-files](DATA-FILES.md)).\
- 1.2. Custom CSS styles what placed in `next/source/css/_custom/*` and `next/source/css/_variables/*` directories.\
- 1.3. Custom layout styles what placed in `next/layout/_custom/*`.\
- 1.4. Any another possible custom additions which can be finded by compare tools between repos.
-2. Clone new v6.x repo to any another directory instead of `next`. For example, in `next-reloaded` directory: `git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded`. So, you don't touch your old NexT 5.1.x directory and can work with new `next-reloaded` dir.
-3. Go to Hexo main config and set theme parameter: `theme: next-reloaded`. So, your `next-reloaded` directory must loading with your generation. If you may see any bugs or you simply not like this version, you anytime can switch for 5.1.x version back.
-
-And how to enable 3rd-party libraries see [here](https://github.com/theme-next/hexo-theme-next/blob/master/docs/INSTALLATION.md#plugins).
diff --git a/doc/themes/next/docs/ru/DATA-FILES.md b/doc/themes/next/docs/ru/DATA-FILES.md
deleted file mode 100644
index a1788d74a..000000000
--- a/doc/themes/next/docs/ru/DATA-FILES.md
+++ /dev/null
@@ -1,61 +0,0 @@
-Дата Файлы
-
-Обновление темы NexT через пулы проходит не слишком гладко. Часто происходит конфликтная ситуация при обновлении по команде `git pull`, хотя её и можно обойти, если смерджить настройки в файле конфигурации вручную.
-
- На данный момент, пользователи хранят одни настройки в корневом `_config.yml` (Hexo), а другие настройки в конфиге темы `_config.yml` (NexT). И всё вроде бы ничего, но имеются некоторые недостатки:
-1. Конфигурация разделяется на две части.
-2. Пользователи могут запутаться, в каком файле какие должны быть настройки.
-
-Во избежании проблемы, NexT использует преимущество Hexo [дата-файлов](https://hexo.io/docs/data-files.html). И т.к. дата-файлы были представлены в Hexo 3, необходимо обновиться до Hexo 3.0 (или выше) для использования этой возможности.
-
-Если же Вы предпочитаете Hexo 2.x, то можно использовать старый способ для конфигураций. NexT всё ещё совместим с Hexo 2.x (но возможны ошибки).
-
-Способ 1: Hexo-Путь
-
-Используя этот способ, вся конфигурация будет раположена в корневом конфиге hexo (`hexo/_config.yml`), благодаря чему нет необходимости изменять оригинальный конфиг темы (`next/_config.yml`) или создавать какие-либо новые файлы. Но в этом случае необходимо сохранять двойные отступы внутри `theme_config` параметра.
-
-Если в новых версиях появятся какие-то новые настройки, нужно просто скопировать эти настройки из оригинального `next/_config.yml` в редактируемый `hexo/_config.yml` и настроить по своему усмотрению.
-
-### Использование
-
-1. Проверяем на существование `hexo/source/_data/next.yml` файл (удаляем, если существует).
-2. Копируем необходимые опции из конфига темы NexT `next/_config.yml` в `hexo/_config.yml`, затем\
- 2.1. Сдвигаем все опции вправо на 2 пробела (в Visual Studio Code: выделяем все строки, CTRL + ]).\
- 2.2. Добавляем `theme_config:` параметр перед всеми этими настройками.
-
-### Полезные ссылки
-
-* [Конфигурация Hexo](https://hexo.io/ru/docs/configuration.html)
-* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
-
-Способ 2: NexT-Путь
-
-Используя этот способ, вся конфигурация будет храниться в одном файле (`source/_data/next.yml`), благодаря чему нет необходимости изменять оригинальный конфиг темы (`next/_config.yml`).
-Но с этим способом могут не корректно обрабатываться все внешние библиотеки hexo при использовании их дополнительных опций (например, опции модуля `hexo-server` могут быть считаны только из стандартного конфига hexo).
-
-Если в новых версиях появятся какие-то новые настройки, нужно просто скопировать эти настройки из оригинального `next/_config.yml` во внешний `_data/next.yml` и настроить по своему усмотрению.
-
-### Использование
-
-1. Убеждаемся, что Hexo версии 3 (или выше).
-2. Создаём файл под именем `next.yml` в корневой директории сайта — `hexo/source/_data` (создаём директорию `_data`, если отсутствует).
-
-И после этих шагов есть 2 варианта, нужно выбрать только 1 из них и продолжить следующие шаги.
-
-* **Вариант 1: `override: false` (по-умолчанию)**:
-
- 1. Проверяем опцию `override` в стандартном конфиге NexT'а, должно быть установлено в `false`.\
- В файле `next.yml` эта опция не должна быть вписана вовсе или вписана и установлена в `false`.
- 2. Копируем настройки из конфига темы NexT (`_config.yml`) и из корневого конфига сайта (`_config.yml`) в файл `hexo/source/_data/next.yml`.
-
-* **Вариант 2: `override: true`**:
-
- 1. В файле `next.yml` ставим опцию `override` в `true`.
- 2. Копируем **все** опции из оригинального конфига NexT'а `next/_config.yml` в `hexo/source/_data/next.yml`.
-
-3. Затем, в корневом конфиге сайта `hexo/_config.yml` необходимо установить опцию `theme: next` (и если требуется, `source_dir: source`).
-4. Используем станадартные параметры для запускаь генерации или развёртывания (`hexo clean && hexo g -d && hexo s`).
-
-### Полезные ссылки
-
-* [NexT Issue #328](https://github.com/iissnan/hexo-theme-next/issues/328)
diff --git a/doc/themes/next/docs/ru/INSTALLATION.md b/doc/themes/next/docs/ru/INSTALLATION.md
deleted file mode 100644
index 5cf98afd8..000000000
--- a/doc/themes/next/docs/ru/INSTALLATION.md
+++ /dev/null
@@ -1,120 +0,0 @@
-Установка
-
-Шаг 1 → Идём в директорию Hexo
-
-Меняем каталог на **корневой hexo**. Там должны находиться `node_modules`, `source`, `themes` и другие папки:
- ```sh
- $ cd hexo
- $ ls
- _config.yml node_modules package.json public scaffolds source themes
- ```
-
-Шаг 2 → Скачиваем NexT
-
-Скачиваем тему с GitHub.
-Имеются 3 способа как зделать это, нужно выбрать только 1 из них.
-
-### Способ 1: Скачиваем [последнюю версию релиза][releases-latest-url]
-
- В большинстве случаев **стабильна**. Рекомендуется для начинающих пользователей.
-
- * Установка с помощью [curl & tar & wget][curl-tar-wget-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -s https://api.github.com/repos/theme-next/hexo-theme-next/releases/latest | grep tarball_url | cut -d '"' -f 4 | wget -i - -O- | tar -zx -C themes/next --strip-components=1
- ```
- Этим способом Вы скачаете **только последнюю версию релиза** (без директории `.git` внутри).\
- Поэтому, в дальнейшем будет невозможно обновить эту версию через `git`.\
- Зато всегда можно использовать отдельную конфигурацию (т.е. [дата-файлы][docs-data-files-url]) и скачивать новую версию перезаписывая старую (или создать новый каталог и переопределить параметр `theme` в конфиге Hexo), без потери старой конфигурации.
-
-### Способ 2: Скачиваем [указанную версию релиза][releases-url]
-
- В редких случаях полезно, но не рекомендуется.\
- Необходимо указать версию. Замените `v6.0.0` на любую версию из [списка тэгов][tags-url].
-
- * Вариант 1: Установка с помощью [curl & tar][curl-tar-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball/v6.0.0 | tar -zxv -C themes/next --strip-components=1
- ```
- То же, что и описано выше в способе `curl & tar & wget`, но скачает **только конкретную версию**.
-
- * Вариант 2: Установка с помощью [git][git-url]:
-
- ```sh
- $ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
- ```
- Этот вариант скачает **указанную версию релиза** (включая директорию `.git` внутри).\
- И в любой момент Вы можете переключиться на любую весию тэга, но с лимитом до указанной версии.
-
-### Способ 3: Скачиваем [последнюю мастер-ветку][download-latest-url]
-
- Иногда может быть **нестабильна**, но включает самые последние нововведения. Рекомендуется для продвинутых пользователей и для разработчиков.
-
- * Вариант 1: Установка с помощью [curl & tar][curl-tar-url]:
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball | tar -zxv -C themes/next --strip-components=1
- ```
- То же, что и описано выше в варианте `curl & tar & wget`, но скачает **только последнюю мастер-ветку**.\
- В некоторых случаях полезно для разработчиков.
-
- * Вариант 2: Установка с помощью [git][git-url]:
-
- ```sh
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next
- ```
-
- Этот вариант скачает **весь репозиторий** (включая директорию `.git` внутри).\
- И в любой момент Вы можете [обновить текущую версию через git][update-with-git-url] и переключиться на любую версию тэга или на последнюю мастер или любую другую ветку.\
- В большинстве случаев полезно как для пользователей, так и для разработчиков.
-
- Смотрим список тэгов:
-
- ```sh
- $ cd themes/next
- $ git tag -l
- …
- v6.0.0
- v6.0.1
- v6.0.2
- ```
-
- Например, Вы хотите переключиться на [версию релиза][tags-url] `v6.0.1`. Вводим следующую команду:
-
- ```sh
- $ git checkout tags/v6.0.1
- Note: checking out 'tags/v6.0.1'.
- …
- HEAD is now at da9cdd2... Release v6.0.1
- ```
-
- И если вы хотите переключиться обратно на [мастер-ветку][commits-url], вводим следующее:
-
- ```sh
- $ git checkout master
- ```
-
-Шаг 3 → Конфигурируем
-
-Устанавливаем параметр темы в конфиге `_config.yml` **корневой директории hexo**:
-
-```yml
-theme: next
-```
-
-[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
-[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
-[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
-[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
-[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
-
-[git-url]: http://lmgtfy.com/?q=linux+git+install
-[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
-[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
-
-[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/README.md#%D0%A3%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0
-[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/DATA-FILES.md
diff --git a/doc/themes/next/docs/ru/README.md b/doc/themes/next/docs/ru/README.md
deleted file mode 100644
index 942dcf684..000000000
--- a/doc/themes/next/docs/ru/README.md
+++ /dev/null
@@ -1,139 +0,0 @@
-
-
-# 
e x T
«NexT» — элегантная высококачественная тема под Hexo. Сделана с нуля, с любовью.
-
-
- 
- 
- 
- 
- 
- 
- 
-
-
-## Демо
-
-* :heart_decoration: Muse тема: [LEAFERx](https://leaferx.online) | [Alex LEE](http://saili.science) | [Miaia](https://11.tt)
-* :six_pointed_star: Mist тема: [uchuhimo](http://uchuhimo.me) | [xirong](http://www.ixirong.com)
-* :pisces: Pisces тема: [Vi](http://notes.iissnan.com) | [Acris](https://acris.me) | [Jiaxi He](http://jiaxi.io)
-* :gemini: Gemini тема: [Ivan.Nginx](https://almostover.ru) | [Raincal](https://raincal.com) | [Dandy](https://dandyxu.me)
-
-Больше примеров «NexT» [здесь](https://github.com/iissnan/hexo-theme-next/issues/119).
-
-## Установка
-
-Простейший вариант установки — склонировать весь репозиторий:
-
- ```sh
- $ cd hexo
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next
- ```
-
-Или предлагаю почитать [детальные инструкции по установке][docs-installation-url], если вариант выше не устраивает.
-
-## Плагины
-
-В конфиге NexT'а теперь можно найти зависимости на каждый модуль, который был вынесен во внешние репозитории, которые могут быть найдены по [ссылке основной организации](https://github.com/theme-next).
-
-Например, Вы хотите использовать `fancybox` для своего сайта. Открываем конфиг NexT'а и находим:
-
-```yml
-# Fancybox
-# Dependencies: https://github.com/theme-next/theme-next-fancybox
-fancybox: false
-```
-
-Затем включаем параметр `fancybox` и переходим по ссылке «Dependencies» с дальнейшеми инструкциями по установке этого модуля.
-
-## Обновление
-
-Можно обновить до последней мастер-ветки следующей командой:
-
-```sh
-$ cd themes/next
-$ git pull
-```
-
-А если всплывают ошибки во время обновления (что-то наподобии **«Commit your changes or stash them before you can merge»**), рекомендуется ознакомиться с особенностью хранения [дата-файлов в Hexo][docs-data-files-url].\
-Как бы то ни было, можно обойти ошибки при обновлении если «Закомитить», «Стэшнуть» или «Откатить» локальные изменения. Смотрим [здесь](https://stackoverflow.com/a/15745424/5861495) как это сделать.
-
-**Если нужно обновиться с версии v5.1.x на v6.0.x, читаем [здесь][docs-update-5-1-x-url].**
-
-## Известные баги
-
-Для тех, кто столкнулся с ошибкой **«[Error: Cannot find module 'hexo-util'](https://github.com/iissnan/hexo-theme-next/issues/1490)»**, следует проверить версию NPM.
-
-* `> 3`: Всё равно не работает? Удалите директорию `node_modules` и переустановите с помощью `npm install`.
-* `< 3`: Добавьте `hexo-util` принудительно командой `npm install --save-dev hexo-util` к основным пакетам с Hexo.
-
-## Содействие
-
-Приветсвуется любое содействие, не стесняйтесь сообщать «Баги», брать «Форки» и вливать «Пулы».
-
-## Обратная связь
-
-* Задать вопрос на [Stack Overflow][stack-url].
-* Сообщить об ошибке в разделе [GitHub Issues][issues-bug-url].
-* Запросить новую возможность на [GitHub][issues-feat-url].
-* Голосовать за [популярные запросы возможностей][feat-req-vote-url].
-* Вступить в наши [Gitter][gitter-url] / [Riot][riot-url] / [Telegram][t-chat-url] чаты.
-* Подписаться на новости через [канал Telegram'а][t-news-url].
-
-## Сторонние приложения
-
-* :triangular_flag_on_post: HexoEditor
-
-## Благодарности
-
-
-«NexT» выражает особую благодарность этим замечательным сервисам, которые спонсируют нашу основную инфраструктуру:
-
-
-
- 
-
- GitHub позволяет нам хостить Git-репозиторий, Netlify позволяет нам деплоить документацию.
-
-
-
-
- Crowdin позволяет нам удобно переводить документацию.
-
-
-
- 
-
- Codacy позволяет нам запускать набор тестов, BrowserStack позволяет нам тестировать в реальных браузерах.
-
-
-[browser-image]: https://img.shields.io/badge/browser-%20chrome%20%7C%20firefox%20%7C%20opera%20%7C%20safari%20%7C%20ie%20%3E%3D%209-lightgrey.svg
-[browser-url]: https://www.browserstack.com
-
-[stack-url]: https://stackoverflow.com/questions/tagged/theme-next
-[issues-bug-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Bug&template=bug-report.md
-[issues-feat-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Feature+Request&template=feature-request.md
-[feat-req-vote-url]: https://github.com/theme-next/hexo-theme-next/issues?q=is%3Aopen+is%3Aissue+label%3A%22Feature+Request%22+sort%3Areactions-%2B1-desc
-
-[gitter-url]: https://gitter.im/theme-next
-[riot-url]: https://riot.im/app/#/room/#theme-next:matrix.org
-[t-chat-url]: https://t.me/theme_next
-[t-news-url]: https://t.me/theme_next_news
-
-
-
-
-
-[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
-[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
-
-[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
-[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
-
-[docs-installation-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/INSTALLATION.md
-[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/DATA-FILES.md
-[docs-update-5-1-x-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/UPDATE-FROM-5.1.X.md
diff --git a/doc/themes/next/docs/ru/UPDATE-FROM-5.1.X.md b/doc/themes/next/docs/ru/UPDATE-FROM-5.1.X.md
deleted file mode 100644
index 499302651..000000000
--- a/doc/themes/next/docs/ru/UPDATE-FROM-5.1.X.md
+++ /dev/null
@@ -1,19 +0,0 @@
-Обновление из-под NexT v5.1.x
-
-Между версиями 5.1.x и 6.0.x нет жёстких изменений. Версия сменилась на мажорную 6 по следующим причинам:
-
-1. Основной репозиторий перебазировался из профиля [iissnan'а](https://github.com/iissnan/hexo-theme-next) в [theme-next](https://github.com/theme-next) организацию.
-2. Большинство библиотек в `next/source/lib` директории были вынесены в [отдельные репозитории под организацией NexT](https://github.com/theme-next).
-3. 3rd-party плагин [`hexo-wordcount`](https://github.com/willin/hexo-wordcount) был заменён на [`hexo-symbols-count-time`](https://github.com/theme-next/hexo-symbols-count-time) т.к. `hexo-symbols-count-time` не имеет никаких сторонних nodejs зависимостей, не имеет [языкового фильтра](https://github.com/willin/hexo-wordcount/issues/7) что обеспечивает улучшенную производительность при генерации сайта.
-
-Поэтому, я предлагаю обновиться с версии 5 на версию 6 следующим способом:
-
-1. Вы не трогаете старую директорию `next`, а всего-лишь делаете резервные копии файлов NexT:\
- 1.1. `config.yml` или `next.yml` (если Вы использовали [дата-файлы](DATA-FILES.md)).\
- 1.2. Пользовательских CSS-стилей, которые расположены в `next/source/css/_custom/*` и `next/source/css/_variables/*` директориях.\
- 1.3. Пользовательских layout-стилей, которые расположены в `next/layout/_custom/*`.\
- 1.4. Любые другие всевозможные пользовательские изменения, которые могут быть найдены любым инструментом для сравнения файлов.
-2. Склонировать новый v6.x репозиторий в любую другую директорию, отличную от `next`. Например, в директорию `next-reloaded`: `git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded`. Итак, нет необходимости трогать старую NexT 5.1.x директорию и можно работать с новой `next-reloaded`.
-3. Открываем главную Hexo-конфигурацию и устанавливаем параметр темы: `theme: next-reloaded`. Так Ваша директория `next-reloaded` должна грузиться при генерации. Если Вы будете наблюдать какие-либо баги или Вам попросту не нравится эта новая версия, в любой момент Вы можете использовать старую 5.1.x.
-
-А как активировать 3rd-party библиотеки, смотрим здесь [здесь](https://github.com/theme-next/hexo-theme-next/blob/master/docs/ru/INSTALLATION.md#%D0%9F%D0%BB%D0%B0%D0%B3%D0%B8%D0%BD%D1%8B).
diff --git a/doc/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md b/doc/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md
deleted file mode 100644
index 8aab587ca..000000000
--- a/doc/themes/next/docs/zh-CN/ALGOLIA-SEARCH.md
+++ /dev/null
@@ -1,84 +0,0 @@
-Algolia 搜索
-
-NexT 内部提供 Algolia 的搜索功能，要使用此功能请确保所使用的 NexT 版本在 `v5.1.0` 之后。需要注意的是，仅仅将 `next/_config.yml` 中 `algolia_search` 的 `enable` 打开**并不能让你使用 Algolia 搜索**，你还需要**使用对应的 Hexo-Algolia 插件** 才能真正在博客页面中使用 Algolia 搜索。按照下面介绍的步骤操作即可完成 Algolia 搜索的安装。
-
-1. 前往 [Algolia 注册页面](https://www.algolia.com/)，注册一个新账户。 可以使用 GitHub 或者 Google 账户直接登录，注册后的 14 天内拥有所有功能（包括收费类别的）。之后若未续费会自动降级为免费账户，免费账户 总共有 10,000 条记录，每月有 100,000 的可以操作数。注册完成后，创建一个新的 Index，这个 Index 将在后面使用。
-
- 
-
-1. Index 创建完成后，此时这个 Index 里未包含任何数据。接下来需要安装 [Hexo Algolia](https://github.com/oncletom/hexo-algolia) 扩展，这个扩展的功能是搜集站点的内容并通过 API 发送给 Algolia。前往站点根目录，执行命令安装：
-
- ```
- $ cd hexo
- $ npm install --save hexo-algolia
- ```
-
-1. 在 `API Keys` 页面找到需要使用的一些配置的值，包括 `ApplicationID` 和 `Search-Only API Key`。注意，`Admin API Key` 需要保密保存，不要外泄。
-
- 
-
-1. 在 `API Keys` 页面，点击 `ALL API KEYS` 找到新建 INDEX 对应的 key，**编辑权限**，在弹出框中找到 ACL ，**勾选 Add records、 Delete records、List indices、Delete index 权限**，点击 `update` 更新。
-
- 
- 
-
-1. 编辑 `站点配置文件`，新增以下配置，除了 `chunkSize` 字段，替换成在 Algolia 获取到的值：
-
- ```yml
- algolia:
- applicationID: 'applicationID'
- apiKey: 'apiKey'
- indexName: 'indexName'
- chunkSize: 5000
- ```
-
-1. 当配置完成，在站点根目录下执行一下命令来更新上传 Index。请注意观察命令的输出。
-
- ```
- $ export HEXO_ALGOLIA_INDEXING_KEY=Search-Only API key # 使用 Git Bash
- # set HEXO_ALGOLIA_INDEXING_KEY=Search-Only API key # 使用 Windows CMD 命令行
- $ hexo clean
- $ hexo algolia
- ```
-
- 
-
-1. 切换到 NexT 目录，并安装 algolia-instant-search 到 `source/lib` 目录。
-
- ```
- $ cd themes/next
- $ git clone https://github.com/theme-next/theme-next-algolia-instant-search source/lib/algolia-instant-search
- ```
-
- 如果你想直接使用 CDN 设置 Algolia Search，则需要在`主题配置文件`中添加 vendors 字段：
-
- ```yml
- vendors:
- ...
- # Internal version: 1
- # https://www.algolia.com
- algolia_instant_js: https://cdn.jsdelivr.net/npm/instantsearch.js@2.4.1/dist/instantsearch.js
- algolia_instant_css: https://cdn.jsdelivr.net/npm/instantsearch.js@2.4.1/dist/instantsearch.min.css
- ...
- ```
-
-1. 更改`主题配置文件`，找到 Algolia Search 配置部分，将 `enable` 改为 `true`。同时你需要**关闭**其他搜索插件，如 Local Search 等。你也可以根据需要调整 `labels` 中的文本：
-
- ```yml
- # Algolia Search
- algolia_search:
- enable: true
- hits:
- per_page: 10
- labels:
- input_placeholder: Search for Posts
- hits_empty: "We didn't find any results for the search: ${query}"
- hits_stats: "${hits} results found in ${time} ms"
- ```
-
-已知的问题
-
-1. 考虑到 Algolia 免费账户的限制，目前 [Hexo-Algolia](https://github.com/oncletom/hexo-algolia) 插件最新版本去掉了正文索引功能。
-1. [Hexo-Algoliasearch](https://github.com/LouisBarranqueiro/hexo-algoliasearch) 插件提供了正文索引功能，不过需要替换 NEXT 主题中的关键字。对于免费账户，`Record Too Big` 的问题同样存在。
- - 替换 `source/js/algolia-search.js` 中所有的 `applicationID` 为 `appId`
- - 替换 `layout/_partials/head/head.swig` 中所有的 `applicationID` 为 `appId`
diff --git a/doc/themes/next/docs/zh-CN/CODE_OF_CONDUCT.md b/doc/themes/next/docs/zh-CN/CODE_OF_CONDUCT.md
deleted file mode 100644
index ecc737649..000000000
--- a/doc/themes/next/docs/zh-CN/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-# e x T
e x T
数据文件
-
-目前，通过 pull 或下载新的 release 版本来更新 NexT 主题的体验并不平滑。当用户使用 `git pull` 更新 NexT 主题时经常需要解决冲突问题，而在手动下载 release 版本时也经常需要手动合并配置。
-
-现在来说，NexT 推荐用户存储部分配置在站点的 `_config.yml` 中，而另一部分在主题的 `_config.yml` 中。这一方式固然可用，但也有一些缺点：
-1. 配置项被分裂为两部分；
-2. 用户难以弄清何处存放配置选项。
-
-为了解决这一问题，NexT 将利用 Hexo 的[数据文件](https://hexo.io/docs/data-files.html)特性。因为数据文件是在 Hexo 3 中被引入，所以你需要更新至 Hexo 3.0 以后的版本来使用这一特性。
-
-如果你仍然希望使用 Hexo 2.x，你依旧可以按老的方式进行配置。NexT 仍然兼容 Hexo 2.x（但可能会出现错误）。
-
-选择 1：Hexo 方式
-
-使用这一方式，你的全部配置都将置于 hexo 主要配置文件中（`hexo/_config.yml`），并且不需要修改 `next/_config.yml`，或者创建什么其他的文件。但是所有的主题选项必须放置在 `theme_config` 后，并全部增加两个空格的缩进。
-
-如果在新的 release 中出现了任何新的选项，那么你只需要从 `next/_config.yml` 中将他们复制到 `hexo/_config.yml` 中并设置它们的值为你想要的选项。
-
-### 用法
-
-1. 请确认不存在 `hexo/source/_data/next.yml` 文件（如果已存在，请删除）
-2. 从主题的 `next/_config.yml` 文件中复制你需要的 NexT 配置项到 `hexo/_config.yml` 中，然后\
- 2.1. 所有这些配置项右移两个空格（在 Visual Studio Code 中：选中这些文字，CTRL + ]）。\
- 2.2. 在这些参数最上方添加一行 `theme_config:`。
-
-### 相关链接
-
-* [Hexo 配置](https://hexo.io/zh-cn/docs/configuration.html)
-* [Hexo Pull #757](https://github.com/hexojs/hexo/pull/757)
-
-选择 2: NexT 方式
-
-使用这一方式，你现在可以将你的全部配置置于同一位置（`source/_data/next.yml`），并且不需要修改 `next/_config.yml`。
-但是可能无法让所有 Hexo 外部库都准确处理它们的附加选项（举个例子，`hexo-server` 模块只会从 Hexo 默认配置文件中读取选项）。
-
-如果在新的 release 中出现了任何新的选项，那么你只需要从 `next/_config.yml` 中将他们复制到 `source/_data/next.yml` 中并设置它们的值为你想要的选项。
-
-### 用法
-
-1. 请确认你的 Hexo 版本为 3.0 或更高。
-2. 在你站点的 `hexo/source/_data` 目录创建一个 `next.yml` 文件（如果 `_data` 目录不存在，请创建之）。
-
-以上步骤之后有 两种选择，请任选其一然后继续后面的步骤。
-
-* **选择 1：`override: false`（默认）**：
-
- 1. 检查默认 NexT 配置中的 `override` 选项，必须设置为 `false`。\
- 在 `next.yml` 文件中，也要设置为 `false`，或者不定义此选项。
- 2. 从站点的 `_config.yml` 与主题的 `_config.yml` 中复制你需要的选项到 `hexo/source/_data/next.yml` 中。
-
-* **选择 2：`override: true`**：
-
- 1. 在 `next.yml` 中设置 `override` 选项为 `true`。
- 2. 从 `next/_config.yml` 配置文件中复制**所有**的 NexT 主题选项到 `hexo/source/_data/next.yml` 中。
-
-3. 然后，在站点的 `hexo/_config.yml`中需要定义 `theme: next` 选项（如果需要的话，`source_dir: source`）。
-4. 使用标准参数来启动服务器，生成或部署（`hexo clean && hexo g -d && hexo s`）。
-
-### 相关链接
-
-* [NexT Issue #328](https://github.com/iissnan/hexo-theme-next/issues/328)
diff --git a/doc/themes/next/docs/zh-CN/INSTALLATION.md b/doc/themes/next/docs/zh-CN/INSTALLATION.md
deleted file mode 100644
index 7ea4b8808..000000000
--- a/doc/themes/next/docs/zh-CN/INSTALLATION.md
+++ /dev/null
@@ -1,120 +0,0 @@
-安装
-
-步骤 1 → 进入 Hexo 目录
-
-进入 **hexo 根**目录。这一目录中应当有 `node_modules`、`source`、`themes` 等若干子目录：
- ```sh
- $ cd hexo
- $ ls
- _config.yml node_modules package.json public scaffolds source themes
- ```
-
-步骤 2 → 获取 NexT
-
-从 GitHub 下载主题。
-为了下载这一主题，共有 3 种选项可选。你需要选择其中唯一一个方式。
-
-### 选项 1：下载[最新 release 版本][releases-latest-url]
-
- 通常情况下请选择 **stable** 版本。推荐不熟悉的用户按此方式进行。
-
- * 使用 [curl、tar 和 wget][curl-tar-wget-url] 安装：
-
- ```sh
- $ mkdir themes/next
- $ curl -s https://api.github.com/repos/theme-next/hexo-theme-next/releases/latest | grep tarball_url | cut -d '"' -f 4 | wget -i - -O- | tar -zx -C themes/next --strip-components=1
- ```
- 这种方式将**仅提供最新的 release 版本**（其中不附带 `.git` 目录）。\
- 因此，将来你将不可能通过 `git` 更新这一方式安装的主题。\
- 取而代之的，为了能不丢失你的自定义配置，你可以使用独立的配置文件（例如 [数据文件][docs-data-files-url]）并下载最新版本到旧版本的目录中（或者下载到新的主题目录中并修改 Hexo 配置中的主题名）。
-
-### 选项 2：下载 [tag 指向的 release 版本][releases-url]
-
- 在少数情况下将有所帮助，但这并非推荐方式。\
- 你必须指定一个版本：使用 [tags 列表][tags-url]中的任意 tag 替换 `v6.0.0`。
-
- * 方式 1：使用 [curl 和 tar][curl-tar-url] 安装：
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball/v6.0.0 | tar -zxv -C themes/next --strip-components=1
- ```
- 和上述的 `curl、tar 和 wget` 方法相同，但只会下载**指定的 release 版本**。
-
- * 方式 2：使用 [git][git-url] 安装：
-
- ```sh
- $ git clone --branch v6.0.0 https://github.com/theme-next/hexo-theme-next themes/next
- ```
- 这一方式将为你下载**指定的 release 版本**（其中包含 `.git` 目录）。\
- 并且，你可以随时切换到任何已定义的版本号所对应的 tag 的版本。
-
-### 选项 3：下载[最新 master 分支][download-latest-url]
-
- 可能**不稳定**，但包含最新的特性。推荐进阶用户和开发者按此方式进行。
-
- * 方式 1：使用 [curl 和 tar][curl-tar-url] 安装：
-
- ```sh
- $ mkdir themes/next
- $ curl -L https://api.github.com/repos/theme-next/hexo-theme-next/tarball | tar -zxv -C themes/next --strip-components=1
- ```
- 和上述的 `curl、tar 和 wget` 方法相同，但只会下载**最新 master 分支版本**。\
- 在有些情况对开发者有所帮助。
-
- * 方式 2：使用 [git][git-url] 安装：
-
- ```sh
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next
- ```
-
- 这一方式将为你下载**完整仓库**（其中包含 `.git` 目录）。\
- 你可以随时[使用 git 更新至最新版本][update-with-git-url]并切换至任何有 tag 标记的 release 版本、最新的 master 分支版本、甚至其他分支。\
- 在绝大多数情况下对用户和开发者友好。
-
- 获取 tags 列表：
-
- ```sh
- $ cd themes/next
- $ git tag -l
- …
- v6.0.0
- v6.0.1
- v6.0.2
- ```
-
- 例如，假设你想要切换到 `v6.0.1` 这一 [tag 指向的 release 版本][tags-url]。输入如下指令：
-
- ```sh
- $ git checkout tags/v6.0.1
- Note: checking out 'tags/v6.0.1'.
- …
- HEAD is now at da9cdd2... Release v6.0.1
- ```
-
- 然后，假设你想要切换回 [master 分支][commits-url]，输入如下指令即可：
-
- ```sh
- $ git checkout master
- ```
-
-步骤 3 → 完成配置
-
-在 **hexo 根配置**文件 `_config.yml` 中设置你的主题：
-
-```yml
-theme: next
-```
-
-[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
-[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
-[releases-url]: https://github.com/theme-next/hexo-theme-next/releases
-[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
-[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
-
-[git-url]: http://lmgtfy.com/?q=linux+git+install
-[curl-tar-url]: http://lmgtfy.com/?q=linux+curl+tar+install
-[curl-tar-wget-url]: http://lmgtfy.com/?q=linux+curl+tar+wget+install
-
-[update-with-git-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/README.md#update
-[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/DATA-FILES.md
diff --git a/doc/themes/next/docs/zh-CN/LEANCLOUD-COUNTER-SECURITY.md b/doc/themes/next/docs/zh-CN/LEANCLOUD-COUNTER-SECURITY.md
deleted file mode 100644
index 39fee3462..000000000
--- a/doc/themes/next/docs/zh-CN/LEANCLOUD-COUNTER-SECURITY.md
+++ /dev/null
@@ -1,186 +0,0 @@
-在配置前，请升级NexT至**v6.0.6**以上。
-
-在配置过程中请注意**博客配置文件**和**主题配置文件**的区别。
-
----
-
-# 注册Leancloud并创建应用
-- 首先，前往Leancloud官网[leancloud.cn](leancloud.cn)进行注册，并登陆。
-- 然后点击图示`1`处，进入控制台：
-
- 
-
-- 接着，点击图示`1`处，创建应用：
-
- 
-
-- 在弹出窗口`1`处输入应用名称（可随意输入，可更改，为演示方便取名为test），并选择`2`处“开发版”，然后点击`3`处创建：
-
- 
-
-到这里应用创建完成。
-
-# 建立Counter类并在NexT中启用插件
-- 点击`1`处应用名称进入应用管理界面：
-
- 
-
-- 如图，点击侧边栏`1`处创建Class：
-
- 
-
-- 在弹出窗口`1`处填入`Counter`，勾选`2`处无限制，并点击`3`处创建Class：
-
- 
-
-- 此时类已创建完成。接下来点击图示`1`处进入设置，然后点击`2`处进入应用Key：
-
- 
-
-- 粘贴`App ID`和`App Key`到**NexT主题配置文件**`_config.yml`对应位置。此时配置文件应如下：
-```yml
-leancloud_visitors:
- enable: true
- security: true
- app_id: <>
- app_key: <>
-```
-
-- 设置Web安全域名确保域名调用安全。点击`1`处进入安全中心，然后在`2`处填写自己博客对应的域名（**注意协议、域名和端口号需严格一致**）：
-
- 
-
-到这里内容均与Doublemine的[为NexT主题添加文章阅读量统计功能](https://notes.wanghao.work/2015-10-21-%E4%B8%BANexT%E4%B8%BB%E9%A2%98%E6%B7%BB%E5%8A%A0%E6%96%87%E7%AB%A0%E9%98%85%E8%AF%BB%E9%87%8F%E7%BB%9F%E8%AE%A1%E5%8A%9F%E8%83%BD.html#%E9%85%8D%E7%BD%AELeanCloud)这篇文章相同，只不过截图为新版的Leancloud的界面。
-
-# 部署云引擎以保证访客数量不被随意篡改
-- 点击左侧`1`处云引擎，然后点击`2`处部署，再点击`3`处在线编辑：
-
- 
-
-- 点击`1`处创建函数：
-
- 
-
-- 在弹出窗口选择`1`处`Hook`类型，然后`2`处选择`beforeUpdate`，`3`处选择刚才建立的`Counter`类。在`4`中粘贴下方代码后，点`5`处保存。
- ```javascript
- var query = new AV.Query("Counter");
- if (request.object.updatedKeys.indexOf('time') !== -1) {
- return query.get(request.object.id).then(function (obj) {
- if (obj.get("time") > request.object.get("time")) {
- throw new AV.Cloud.Error('Invalid update!');
- }
- return request.object.save();
- });
- }
- ```
-
- 如图所示：
-
- 
-
-- 点击保存后应出现类似红框处函数。此时点击`1`处部署：
-
- 
-
-- 在弹出窗口点击`1`处部署：
-
- 
-
-- 等待出现红框处的成功部署信息后，点击`1`处关闭：
-
- 
-
-
-至此云引擎已成功部署，任何非法的访客数量更改请求都将失败。
-
-# 进一步设置权限
-- 打开**NexT主题配置文件**`_config.yml`，将leancloud_visitors下的security设置为true（如没有则新增）：
- ```yml
- leancloud_visitors:
- enable: true
- app_id: <>
- app_key: <>
- # Dependencies: https://github.com/theme-next/hexo-leancloud-counter-security
- security: true
- betterPerformance: false
- ```
-
- **对`betterPerformance`选项的说明：**
- 由于Leancloud免费版的云引擎存在请求线程数和运行时间限制以及休眠机制，很多时候访客数量加载会很慢。如果设置`betterPerformance`为`true`，则网页则会在提交请求之前直接显示访客人数为查询到的人数+1，以增加用户体验。
-
-- 打开cmd并切换至**博客根目录**，键入以下命令以安装`hexo-leancloud-counter-security`插件：
- ```
- npm install hexo-leancloud-counter-security --save
- ```
-
-- 打开**博客配置文件**`_config.yml`，新增以下配置：
- ```yml
- leancloud_counter_security:
- enable_sync: true
- app_id: <>
- app_key: <
- username:
- password:
- ```
-
-- 在相同目录键入以下命令：
- ```
- hexo lc-counter register <> <>
- ```
- 或
- ```
- hexo lc-counter r <> <>
- ```
-
- 将`<>`和`<>`替换为你自己的用户名和密码（不必与leancloud的账号相同）。此用户名和密码将在hexo部署时使用。
-
- - 打开**博客配置文件**`_config.yml`，将`<>`和`<>`替换为你刚刚设置的用户名和密码：
- ```yml
- leancloud_counter_security:
- enable_sync: true
- app_id: <>
- app_key: <
- username: <> #如留空则将在部署时询问
- password: <> #建议留空以保证安全性，如留空则将在部署时询问
- ```
-
-- 在**博客配置文件**`_config.yml`的`deploy`下添加项：
- ```yml
- deploy:
- # other deployer
- - type: leancloud_counter_security_sync
- ```
-
-- 返回Leancloud控制台的应用内。依次点击`1` `2`，检查_User表中是否出现一条记录（图示以用户名为admin为例）：
-
- 
-
-- 点击`1`处进入Counter表，依次点击`2` `3`，打开权限设置：
-
- 
-
-- 点击`1`add_fields后选择`2`指定用户， 并将下两栏留空：此处应与下条create设置相同（选择你所创建的用户）：
-
- 
-
-- 点击`1`create后选择`2`指定用户， 在`3`处键入用户名，点击`4`处后点击`5`处添加：
-
- 
-
- 完成此步操作后，界面应与图示类似：
-
- 
-
-- 点击`1`delete后选择`2`指定用户， 并将下两栏留空：
-
- 
-
-至此权限已设置完成，数据库记录只能在本地增删。
-
-每次运行`hexo d`部署的时候，插件都会扫描本地`source/_posts`下的文章并与数据库对比，然后在数据库创建没有录入数据库的文章记录。
-
-如果在**博客配置文件**中留空username或password，则在部署过程中程序会要求输入。
-
----
-
-原文链接：https://leaferx.online/2018/02/11/lc-security/
diff --git a/doc/themes/next/docs/zh-CN/MATH.md b/doc/themes/next/docs/zh-CN/MATH.md
deleted file mode 100644
index 760053a57..000000000
--- a/doc/themes/next/docs/zh-CN/MATH.md
+++ /dev/null
@@ -1,291 +0,0 @@
-数学公式
-
-NexT 内部提供数学公式渲染的引擎，这样你就不需要自己手动在模板中引入 JS 或者 CSS；
-只需要将 `next/_config.yml` 中 `math` 的 `enable` 选项改为 `true`，并选择对应的渲染引擎即可：
-
-
-```yml
-math:
- enable: true
- ...
- engine: mathjax
-```
-
-
-需要注意的是，仅仅将 `math` 的 `enable` 打开**并不能让你看到数学公式**，你还需要**使用对应的 Hexo 渲染器(Renderer)** 才能真正在博客页面中显示出数学公式。引擎对应使用的 Hexo 渲染器会在引擎相关的部分介绍。
-
-提供的渲染引擎
-
-目前，NexT 提供两种数学公式渲染引擎，分别为 [MathJax](https://www.mathjax.org/) 和 [Katex](https://khan.github.io/KaTeX/)，默认为 MathJax。
-
-### MathJax(默认)
-
-如果你选择使用 MathJax 进行数学公式渲染，你需要使用 [hexo-renderer-pandoc](https://github.com/wzpan/hexo-renderer-pandoc) 或者 [hexo-renderer-kramed](https://github.com/sun11/hexo-renderer-kramed) 这两个渲染器的其中一个。
-
-首先，卸载原有的渲染器 `hexo-renderer-marked`，并安装这两种渲染器的**其中一个**：
-
-```sh
-npm un hexo-renderer-marked --save
-npm i hexo-renderer-pandoc --save # 或者 hexo-renderer-kramed
-```
-
-
-然后在 `next/_config.yml` 中将 `math` 的 `enable` 打开，并选择 `mathjax` 作为渲染引擎。
-
-```yml
-math:
- enable: true
- ...
- engine: mathjax
- #engine: katex
-```
-
-执行 Hexo 生成，部署，或者启动服务器：
-
-```sh
-hexo clean && hexo g -d
-# 或者 hexo clean && hexo s
-```
-
-#### 使用 MathJax 给公式编号并引用公式
-
-在新版本的 NexT 主题中，我们加入了公式自动编号和引用功能。下面简要介绍一下如何使用这项功能。
-
-为了使用这项功能，一般来说，你必须把所使用的 LaTeX 公式放在 `equation` 环境里面，采用旧的方法（也就是说，仅仅把公式的每一边用两个 $ 符号包含起来）是无效的。如何引用公式？你只需要在书写公式的时候给公式一个 `\
-label{}` 标记（tag），然后在正文中，可以使用 `\ref{}` 或者 `\eqref{}` 命令来引用对应的公式。使用 `\eqref{}` 是推荐的方式，因为如果你使用 `\ref{}`，公式在文中的引用编号将没有圆括号包围。下面介绍几种常见的公式编号例子。
-
-对于简单的公式，使用下面的方式给公式一个标记，
-
-```latex
-$$\begin{equation}
-e=mc^2
-\end{equation}\label{eq1}$$
-```
-
-然后，在正文中，你可以轻松引用上述公式，一个简单的例子如下：
-
-```
-著名的质能方程 $\eqref{eq1}$ 由爱因斯坦提出 ...
-```
-
-对于多行公式，在 `equation` 环境中，你可以使用 `aligned` 环境把公式分成多行，
-
-```latex
-$$\begin{equation}
-\begin{aligned}
-a &= b + c \\
- &= d + e + f + g \\
- &= h + i
-\end{aligned}
-\end{equation}\label{eq2}$$
-```
-
-要对齐多个公式，我们需要使用 `align` 环境。align 环境中的每个公式都有自己的编号：
-
-```
-$$\begin{align}
-a &= b + c \label{eq3} \\
-x &= yz \label{eq4}\\
-l &= m - n \label{eq5}
-\end{align}$$
-```
-
-在 `align` 环境中，如果你不想给某个或某几个公式编号，那么在这些公式后面使用 [`\nonumber`](https://tex.stackexchange.com/questions/17528/show-equation-number-only-once-in-align-environment) 命令即可。例如：
-
-```latex
-$$\begin{align}
--4 + 5x &= 2+y \nonumber \\
- w+2 &= -1+w \\
- ab &= cb
-\end{align}$$
-```
-
-有时，你可能会希望采用更加奇特的方式来标记和引用你的公式，你可以通过使用 `\tag{}` 命令来实现，例如：
-
-```latex
-$$x+1\over\sqrt{1-x^2} \tag{i}\label{eq_tag}$$
-```
-
-如果你想要了解更多信息，请访问 [MathJax 关于公式编号的官方文档](http://docs.mathjax.org/en/latest/tex.html#automatic-equation-numbering)。同时，你也可以访问[这篇博客](https://jdhao.github.io/2018/01/25/hexo-mathjax-equation-number/) 来获取更多细节信息。
-
-### Katex
-
-Katex 渲染引擎相对于 MathJax 来说**大大提高了速度**，而且在关掉 JavaScript 时也能渲染数学公式。
-
-但是 Katex 所支持的东西没有 MathJax 全面，你可以从下面的相关链接中获取更多的信息。
-
-如果你选择使用 Katex 进行数学公式渲染，你需要使用 [hexo-renderer-markdown-it-plus](https://github.com/CHENXCHEN/hexo-renderer-markdown-it-plus) 或者 [hexo-renderer-markdown-it](https://github.com/hexojs/hexo-renderer-markdown-it) 这两种渲染器的其中一个。
-
-首先，卸载原有的渲染器 `hexo-renderer-marked`，并安装这两种渲染器的**其中一个**：
-
-```sh
-npm un hexo-renderer-marked --save
-npm i hexo-renderer-markdown-it-plus --save
-# 或者 hexo-renderer-markdown-it
-```
-
-
-然后在 `next/_config.yml` 中将 `math` 的 `enable` 打开，并选择 `katex` 作为渲染引擎。
-
-```yml
-math:
- enable: true
- ...
- #engine: mathjax
- engine: katex
-```
-
-执行 Hexo 生成，部署，或者启动服务器：
-
-```sh
-hexo clean && hexo g -d
-# 或者 hexo clean && hexo s
-```
-
-#### 如果你使用 hexo-renderer-markdown-it
-
-如果你使用 `hexo-renderer-markdown-it`，你还需要为其加上 `markdown-it-katex` 作为插件：
-
-```
-npm i markdown-it-katex --save
-```
-
-然后在 `hexo/_config.yml` 中将 `markdown-it-katex` 作为插件写入 `hexo-renderer-markdown-it` 的配置中：
-
-```yml
-markdown:
- render:
- html: true
- xhtmlOut: false
- breaks: true
- linkify: true
- typographer: true
- quotes: '“”‘’'
- plugins:
- - markdown-it-katex
-```
-
-#### 已知的问题
-
-1. 首先请查阅 Katex 的 [Common Issue](https://github.com/Khan/KaTeX#common-issues)
-2. 块级公式(例如 `$$...$$`)必须位于空行。\
- 即在开头的 `$$` 前和在结尾的 `$$` 后不能有除了空白字符以外的其他字符。([#32comment](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509))
-3. 不支持 Unicode。([#32comment](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509))
-4. 行内公式(例如 `$...$`)在开头的 `$` 后面和结尾的 `$` 前面**不能含有空格**。([#32comment](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-357489509))
-5. 如果你在文章的各级标题中(例如 `## 标题`)使用公式。\
- 那么文章目录中的这个标题会出现 3 次未渲染的公式代码([#32comment](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359018694))
-6. 如果你在文章 Title 中使用公式，那么公式将不会被渲染。([#32comment](https://github.com/theme-next/hexo-theme-next/pull/32#issuecomment-359142879))
-
-
-我们目前使用的 Katex 版本为 0.7.1，这里面可能有某些问题是因为 Katex 版本老旧导致的；
-
-但是，就像上面所说的，数学公式的渲染必须依靠渲染器来支持，目前的 Katex 相关的渲染器仅支持到 Katex 0.7.1；
-
-我们会持续关注相关渲染器的更新，如果有渲染器支持更高版本的 Katex，我们会及时更新我们的 Katex 版本。
-
-### 相关链接
-
-* [Katex 与 MathJax 渲染速度对比](https://www.intmath.com/cg5/katex-mathjax-comparison.php)
-* [Katex 支持的功能列表](https://khan.github.io/KaTeX/function-support.html)
-
-相关配置说明
-
-注意，在修改配置选项时，**不要更改配置的缩进**；
-
-目前，NexT 的所有配置都采用**2 空格的缩进**；
-
-如果配置的内容接在冒号后面，那么内容和冒号之间必须有一个空格(例如`enable: true`)
-
-```yml
-
-# Math Equations Render Support
-math:
- enable: false
-
- # Default(true) will load mathjax/katex script on demand
- # That is it only render those page who has 'mathjax: true' in Front Matter.
- # If you set it to false, it will load mathjax/katex srcipt EVERY PAGE.
- per_page: true
-
- engine: mathjax
- #engine: katex
-
- # hexo-rendering-pandoc (or hexo-renderer-kramed) needed to full MathJax support.
- mathjax:
- # Use 2.7.1 as default, jsdelivr as default CDN, works everywhere even in China
- cdn: //cdn.jsdelivr.net/npm/mathjax@2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML
- # For direct link to MathJax.js with CloudFlare CDN (cdnjs.cloudflare.com).
- #cdn: //cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-MML-AM_CHTML
-
- # hexo-renderer-markdown-it-plus (or hexo-renderer-markdown-it with markdown-it-katex plugin)
- # needed to full Katex support.
- katex:
- # Use 0.7.1 as default, jsdelivr as default CDN, works everywhere even in China
- cdn: //cdn.jsdelivr.net/npm/katex@0.7.1/dist/katex.min.css
- # CDNJS, provided by cloudflare, maybe the best CDN, but not works in China
- #cdn: //cdnjs.cloudflare.com/ajax/libs/KaTeX/0.7.1/katex.min.css
-```
-
-### enable
-
-`true` 或者 `false`，默认为 `false`。
-
-`true` 是打开数学公式渲染，`false` 则是关闭。
-
-### per_page
-
-`true` 或者 `false`，默认为 `true`。
-
-这个选项是控制是否在每篇文章都渲染数学公式；
-
-默认(`true`) 的行为是**只对 Front Matter 中含有 `mathjax: true` 的文章进行数学公式渲染**。
-
-如果 Front Matter 中不含有 `mathjax: true`，或者 `mathjax: false`，那么 NexT 将不会对这些文章进行数学公式渲染。
-
-例如：
-
-```md
-
----
-title: 'Will Render Math'
-mathjax: true
----
-....
-```
-
-```md
-
----
-title: 'Not Render Math'
-mathjax: false
----
-....
-```
-
-```md
-
----
-title: 'Not Render Math Either'
----
-....
-```
-
-当你将它设置为 `false` 时，它就会在每个页面都加载 MathJax 或者 Katex 来进行数学公式渲染。
-
-### cdn
-
-MathJax 和 Katex 都提供了 `cdn` 的配置，如果你不知道什么是 `cdn` ，**请不要修改这个配置**。
-
-首先，MathJax 和 Katex 都使用了 [jsDelivr](https://www.jsdelivr.com/) 作为默认 CDN；
-
-之所以选择 jsDelivr 是因为它在全球各地都有比较不错的速度，而且具有中国官方颁布的 ICP 证书，在中国也能比较好地访问。
-
-同时，我们也提供了其他的 CDN 备选方案，包括著名的 [CDNJS](https://cdnjs.com/)。
-
-对于 MathJax 来说，我们目前采用的版本为 2.7.1。
-
-对于 Katex，由于上面提到的版本问题，我们目前采用的版本为 0.7.1。
-
-如果你想尝试我们提供的备选方案以外的 CDN，请注意使用对应的版本。
-
-特别的，对于中国的博客主，或者您的博客访问大部分来源于中国，由于 CDNJS 在部分中国地区被墙，请不要使用 CDNJS 作为 CDN。
diff --git a/doc/themes/next/docs/zh-CN/README.md b/doc/themes/next/docs/zh-CN/README.md
deleted file mode 100644
index d25f43e27..000000000
--- a/doc/themes/next/docs/zh-CN/README.md
+++ /dev/null
@@ -1,156 +0,0 @@
-
-
-# e x T
«NexT» 是一款风格优雅的高质量 Hexo 主题，自点点滴滴中用爱雕琢而成。
-
-
-
-
-
-
-
-
-
-
-
-## 即时预览
-
-* :heart_decoration: Muse 主题: [LEAFERx](https://leaferx.online) | [Alex LEE](http://saili.science) | [Miaia](https://11.tt)
-* :six_pointed_star: Mist 主题: [uchuhimo](http://uchuhimo.me) | [xirong](http://www.ixirong.com)
-* :pisces: Pisces 主题: [Vi](http://notes.iissnan.com) | [Acris](https://acris.me) | [Jiaxi He](http://jiaxi.io)
-* :gemini: Gemini 主题: [Ivan.Nginx](https://almostover.ru) | [Raincal](https://raincal.com) | [Dandy](https://dandyxu.me)
-
-更多 «NexT» 的例子参见[这里](https://github.com/iissnan/hexo-theme-next/issues/119)。
-
-## 安装
-
-最简单的安装方式是直接克隆整个仓库：
-
- ```sh
- $ cd hexo
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next
- ```
-
-此外，如果你想要使用其他方式，你也可以参见[详细安装步骤][docs-installation-url]。
-
-## 插件
-
-在 NexT 配置中你现在可以找到已经被移至外部仓库的依赖项。你可以在[组织主页](https://github.com/theme-next)中找到它们。
-
-例如，假设你想要在你的站点中使用 `fancybox` 插件，请进入 NexT 配置文件，你会看到如下内容：
-
-```yml
-# Fancybox
-# Dependencies: https://github.com/theme-next/theme-next-fancybox
-fancybox: false
-```
-
-将 `fancybox` 配置项打开，进入它上面的 «Dependencies» 链接以查看它的安装步骤。
-
-### 例外
-
-如果你使用的插件脚本依赖 CDN，那么需要替换你的 CDN 链接：
-
-例如，假如你使用了 `fancybox` 插件并且配置了 CDN 加载链接，进入 Next 配置文件，你会看到如下内容：
-
-```yml
-vendors:
- # ...
- # Some contents...
- # ...
- fancybox: # Set or update fancybox cdn url.
- fancybox_css: # Set or update fancybox cdn url.
-```
-
-通过替换 CDN 链接来替换 [插件列表](https://github.com/theme-next) 项目来升级。
-
-## 更新
-
-你可以通过如下命令更新到最新的 master 分支：
-
-```sh
-$ cd themes/next
-$ git pull
-```
-
-如果你在此过程中收到了任何错误报告 (例如 **«Commit your changes or stash them before you can merge»**)，我们推荐你使用 [Hexo 数据文件][docs-data-files-url]特性。\
-然而你也可以通过提交（`Commit`）、贮藏（`Stash`）或忽视（`Discard`）本地更改以绕过这种更新错误。具体方法请参考[这里](https://stackoverflow.com/a/15745424/5861495)。
-
-**如果你想要从 v5.1.x 更新到 v6.0.x，阅读[这篇文档][docs-update-5-1-x-url]。**
-
-## 已知问题
-
-对于仍然遇到 **«[Error: Cannot find module 'hexo-util'](https://github.com/iissnan/hexo-theme-next/issues/1490)»** 这一错误的用户，请检查你的 NPM 版本。
-
-* `> 3`：仍然出现错误吗？请删除 `node_modules` 目录并通过 `npm install` 重新安装。
-* `< 3`：请通过 `npm install --save-dev hexo-util` 将 `hexo-util` 依赖手动添加至你的站点依赖包中。
-
-## 贡献你的代码
-
-我们欢迎你贡献出你的一份力量，你可以随时提交 issue 或 fork 本仓库。静候你的 pull request。
-
-## 反馈
-
-* 在 [Stack Overflow][stack-url] 上提问。
-* 在 [GitHub Issues][issues-bug-url] 报告Bug。
-* 在 [GitHub][issues-feat-url] 请求新的功能。
-* 为 [popular feature requests][feat-req-vote-url] 投票。
-* 加入我们的 [Gitter][gitter-url] / [Riot][riot-url] / [Telegram][t-chat-url] 聊天。
-* 关注我们的 [Telegram Channel][t-news-url] 以获取最新消息。
-
-## 第三方应用程序
-
-* :triangular_flag_on_post: HexoEditor
-
-## 鸣谢
-
-
-«NexT» 特别感谢这些支持我们核心基础设施的优质服务：
-
-
-
-
-
- GitHub 容许我们托管 Git 仓库，Netlify 容许我们分发文档。
-
-
-
-
- Crowdin 容许我们方便地翻译文档。
-
-
-
-
-
- Codacy 容许我们运行测试套件，BrowserStack 容许我们在真实的浏览器中进行测试。
-
-
-[browser-image]: https://img.shields.io/badge/browser-%20chrome%20%7C%20firefox%20%7C%20opera%20%7C%20safari%20%7C%20ie%20%3E%3D%209-lightgrey.svg
-[browser-url]: https://www.browserstack.com
-
-[stack-url]: https://stackoverflow.com/questions/tagged/theme-next
-[issues-bug-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Bug&template=bug-report.md
-[issues-feat-url]: https://github.com/theme-next/hexo-theme-next/issues/new?assignees=&labels=Feature+Request&template=feature-request.md
-[feat-req-vote-url]: https://github.com/theme-next/hexo-theme-next/issues?q=is%3Aopen+is%3Aissue+label%3A%22Feature+Request%22+sort%3Areactions-%2B1-desc
-
-[gitter-url]: https://gitter.im/theme-next
-[riot-url]: https://riot.im/app/#/room/#theme-next:matrix.org
-[t-chat-url]: https://t.me/theme_next
-[t-news-url]: https://t.me/theme_next_news
-
-
-
-
-
-[download-latest-url]: https://github.com/theme-next/hexo-theme-next/archive/master.zip
-[releases-latest-url]: https://github.com/theme-next/hexo-theme-next/releases/latest
-
-[tags-url]: https://github.com/theme-next/hexo-theme-next/tags
-[commits-url]: https://github.com/theme-next/hexo-theme-next/commits/master
-
-[docs-installation-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/INSTALLATION.md
-[docs-data-files-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/DATA-FILES.md
-[docs-update-5-1-x-url]: https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/UPDATE-FROM-5.1.X.md
diff --git a/doc/themes/next/docs/zh-CN/UPDATE-FROM-5.1.X.md b/doc/themes/next/docs/zh-CN/UPDATE-FROM-5.1.X.md
deleted file mode 100644
index ab097eac1..000000000
--- a/doc/themes/next/docs/zh-CN/UPDATE-FROM-5.1.X.md
+++ /dev/null
@@ -1,35 +0,0 @@
-从 NexT v5.1.x 更新
-
-在 5.1.x 版本和 6.0.x 版本之间没有很大的革命性改进。主版本号变更至 6 主要是因为：
-
-1. 主仓库已从 [iissnan 名下](https://github.com/iissnan/hexo-theme-next) 迁移至 [theme-next](https://github.com/theme-next) 组织。
-2. `next/source/lib` 目录下的绝大多数库被移出到了 [NexT 组织的外部仓库](https://github.com/theme-next)中。
-3. 第三方插件 [`hexo-wordcount`](https://github.com/willin/hexo-wordcount) 被 [`hexo-symbols-count-time`](https://github.com/theme-next/hexo-symbols-count-time) 所取代，因为 `hexo-symbols-count-time` 没有任何外部 nodejs 依赖、也没有会导致生成站点时的性能问题 [language filter](https://github.com/willin/hexo-wordcount/issues/7)。
-
-推荐通过如下步骤从 v5 升级到 v6：
-
-1. 并不修改原有的 `next` 目录，而只是复制部分 NexT 文件：
- 1. `config.yml` 或 `next.yml`（如果你使用了[数据文件](DATA-FILES.md)）。
- 2. 自定义的 CSS 配置，它们应在 `next/source/css/_custom/*` 和 `next/source/css/_variables/*` 中。
- 3. 自定义的排布配置，它们应在 `next/layout/_custom/*` 中。
- 4. 任何其它可能的附加自定义内容；为了定位它们，你可以通过某些工具在仓库间比较。
-2. 克隆新的 v6.x 仓库到任一异于 `next` 的目录（如 `next-reloaded`）：
- ```sh
- $ git clone https://github.com/theme-next/hexo-theme-next themes/next-reloaded
- ```
- 如此，你可以在不修改原有的 NexT v5.1.x 目录的同时使用 `next-reloaded` 目录中的新版本主题。
-3. 在 Hexo 的主配置文件中设置主题：
- ```yml
- ...
- theme: next-reloaded
- ...
- ```
- 如此，你的 `next-reloaded` 主题将在生成站点时被加载。如果你遇到了任何错误、或只是不喜欢这一新版本，你可以随时切换回旧的 v5.1.x 版本。
-
-4. 更新语言配置
-
- 从 v6.0.3版本起，`zh-Hans`改名为`zh-CN`：https://github.com/theme-next/hexo-theme-next/releases/tag/v6.0.3
-
- 升级到v6.0.3及以后版本的用户，需要显式修改`_config.xml`里的language配置，否则语言显示不正确。
-
-关于第三方库的启用，参见[这里](https://github.com/theme-next/hexo-theme-next/blob/master/docs/zh-CN/INSTALLATION.md#插件)。
From 4ef70ba91d5f4b5569b3ecd83c67461158b514df Mon Sep 17 00:00:00 2001
From: NaBian <836904362@qq.com>
Date: Sat, 3 Oct 2020 10:10:12 +0800
Subject: [PATCH 2/3] fixed #484
---
.../Themes/Styles/MessageBox.xaml | 29 ++-
.../Controls/Window/MessageBox.cs | 211 ++++++++++++++++--
.../Themes/Styles/MessageBox.xaml | 29 ++-
.../Tools/Interop/InteropMethods.cs | 3 +
.../Tools/Interop/InteropValues.cs | 3 +
5 files changed, 237 insertions(+), 38 deletions(-)
diff --git a/src/Net_40/HandyControl_Net_40/Themes/Styles/MessageBox.xaml b/src/Net_40/HandyControl_Net_40/Themes/Styles/MessageBox.xaml
index 6b39d81d6..c2d390336 100644
--- a/src/Net_40/HandyControl_Net_40/Themes/Styles/MessageBox.xaml
+++ b/src/Net_40/HandyControl_Net_40/Themes/Styles/MessageBox.xaml
@@ -1,16 +1,26 @@
+
+
+
+
+
+
+