nzomkxia closed pull request #10: update dubbo docs address in readme
URL: https://github.com/apache/incubator-dubbo-docs/pull/10
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/README.md b/README.md
index 857323f..6334c9e 100644
--- a/README.md
+++ b/README.md
@@ -1,19 +1,17 @@
-# A collection of dubbo docs
+# A collection of Apache Dubbo (incubating) docs
 
-* [Dubbo user manual(English)](http://dubbo.io/books/dubbo-user-book-en/) or 
[Dubbo用户手册(中文)](http://dubbo.io/books/dubbo-user-book/) - Describe how to use 
Dubbo and all features of Dubbo concretely.
-* [Dubbo developer guide(English)](http://dubbo.io/books/dubbo-dev-book-en/) 
or [Dubbo开发手册(中文)](http://dubbo.io/books/dubbo-dev-book/) - Detailly introduce 
the design principal, extension mechanisms, code conventions, version control 
and building project, etc.
-* [Dubbo admin manual(English)](http://dubbo.io/books/dubbo-admin-book-en/) or 
[Dubbo管理手册(中文)](http://dubbo.io/books/dubbo-admin-book/) - Describe how to use 
Dubbo registry and admin-console.
+* [Dubbo user 
manual(English)](http://dubbo.apache.org/books/dubbo-user-book-en/) or 
[Dubbo用户手册(中文)](http://dubbo.apache.org/books/dubbo-user-book/) - Describe how 
to use Dubbo and all features of Dubbo concretely.
+* [Dubbo developer 
guide(English)](http://dubbo.apache.org/books/dubbo-dev-book-en/) or 
[Dubbo开发手册(中文)](http://dubbo.apache.org/books/dubbo-dev-book/) - Detailly 
introduce the design principal, extension mechanisms, code conventions, version 
control and building project, etc.
+* [Dubbo admin 
manual(English)](http://dubbo.apache.org/books/dubbo-admin-book-en/) or 
[Dubbo管理手册(中文)](http://dubbo.apache.org/books/dubbo-admin-book/) - Describe how 
to use Dubbo registry and admin-console.
 
 ## How to Visit (Publish Address):
 
-* The Chinese version is released under the `dubbo.io` domain, for example, 
you can visit User Mannual through http://dubbo.io/books/dubbo-user-book/.
-* The English version is published to `dubbo.io` as well, in addition, it is 
also published to `dubbo.gitbooks.io`. This way, you can visit the User Mannul 
through http://dubbo.io/books/dubbo-user-book-en/ or 
https://dubbo.gitbooks.io/user-book-en/.
+* The Chinese version is released under the `dubbo.apache.org` domain, for 
example, you can visit User Mannual through 
http://dubbo.apache.org/books/dubbo-user-book/.
+* The English version is published to `dubbo.apache.org` as well. This way, 
you can visit the User Mannul through 
http://dubbo.apache.org/books/dubbo-user-book-en/.
 
 ## How to Publish
 
 This repository only stores markdown sources, in order to be visited by users, 
it should be published everytime when there's an update. It will not be 
published automatically, so the committers need to publish mannually following 
rules below:
 
-* Publish to dubbo.io. You can find [the publish 
script](https://github.com/dubbo/dubbo.github.io/blob/master/script/deploy) 
stored in repo dubbo/dubbo.github.io(the official site), clone that repo and 
run the script, all resources will be published automatically to dubbo.io.
-* Publish to dubbo.gitbooks.io(only for english version). There's no publish 
script for this approach, what you need to do is merge the master branch to the 
corresponding branch. Because the gitbooks is watching the branches in this 
repo:gitbook-admin-en, gitbook-user-en, gitbook-dev-en, every change will be 
published automitically.
-
+* Publish to dubbo.apache.org. You can find [the publish 
script](https://github.com/apache/incubator-dubbo-website/blob/asf-site/script/deploy)
 stored in repo incubator-dubbo-website(the official site), clone that repo and 
run the script, all resources will be published automatically to 
dubbo.apache.org.
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to