hyperledger / hyperledger/fabric-docs-i18n

[ja_JP] Getting Started - Install

Open
#863 0 comments 0 reactions 0 assignees View on GitHub
jaJP-docs-ongoing
Dominant language
Makefile
Stars
96
Forks
180
PR merge metrics
No merged PRs in 30d

Description

Original HTML: https://hyperledger-fabric.readthedocs.io/en/release-2.5/getting_started.html
Original Source: https://github.com/hyperledger/fabric/blob/e1e8e2e52aa4fc543360d245fe6554a0eaf81183/docs/source/getting_started.rst

````diff
diff --git a/docs/source/getting_started.rst b/docs/source/getting_started.rst
index 087396c3d..7732f23f7 100644
--- a/docs/source/getting_started.rst
+++ b/docs/source/getting_started.rst
@@ -1,5 +1,5 @@
-Getting Started
-===============
+Getting Started - Install
+=========================

.. toctree::
:maxdepth: 1
@@ -7,58 +7,23 @@ Getting Started

prereqs
install
- test_network
+ sdk_chaincode

-Before we begin, if you haven't already done so, you may wish to check that
-you have all the :doc:`prereqs` installed on the platform(s)
-on which you'll be developing blockchain applications and/or operating
-Hyperledger Fabric.

-Once you have the prerequisites installed, you are ready to download and
-install HyperLedger Fabric. While we work on developing real installers for the
-Fabric binaries, we provide a script that will :doc:`install` to your system.
-The script also will download the Docker images to your local registry.
+The Fabric application stack has five layers:

-After you have downloaded the Fabric Samples and Docker images to your local
-machine, you can get started working with Fabric with the
-:doc:`test_network` tutorial.
+.. image:: ./getting_started_image2.png
+ :width: 300px
+ :align: right
+ :height: 200px
+ :alt: Fabric Application Stack

-Hyperledger Fabric smart contract (chaincode) APIs
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+* :doc:`Prerequisite software `: the base layer needed to run the software, for example, Docker.
+* :doc:`Fabric and Fabric samples `: the Fabric executables to run a Fabric network along with sample code.
+* :doc:`Contract APIs `: to develop smart contracts executed on a Fabric Network.
+* :doc:`Application APIs `: to develop your blockchain application.
+* The Application: your blockchain application will utilize the Application SDKs to call smart contracts running on a Fabric network.

-Hyperledger Fabric offers a number of APIs to support developing smart contracts (chaincode)
-in various programming languages. Smart contract APIs are available for Go, Node.js, and Java:
-
- * `Go contract-api `__.
- * `Node.js contract API `__ and `Node.js contract API documentation `__.
- * `Java contract API `__ and `Java contract API documentation `__.
-
-Hyperledger Fabric application SDKs
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Hyperledger Fabric offers a number of SDKs to support developing applications in various programming languages. SDKs are available for Node.js and Java:
-
- * `Node.js SDK `__ and `Node.js SDK documentation `__.
- * `Java SDK `__ and `Java SDK documentation `__.
-
- Prerequisites for developing with the SDKs can be found in the Node.js SDK `README `__ and Java SDK `README `__.
-
-In addition, there are two more application SDKs that have not yet been officially released
-(for Python and Go), but they are still available for downloading and testing:
-
- * `Python SDK `__.
- * `Go SDK `__.
-
-Currently, Node.js, Java and Go support the new application programming model delivered in Hyperledger Fabric v1.4.
-
-Hyperledger Fabric CA
-^^^^^^^^^^^^^^^^^^^^^
-
-Hyperledger Fabric provides an optional
-`certificate authority service `_
-that you may choose to use to generate the certificates and key material
-to configure and manage identity in your blockchain network. However, any CA
-that can generate ECDSA certificates may be used.

.. Licensed under Creative Commons Attribution 4.0 International License
https://creativecommons.org/licenses/by/4.0/

````

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the referenced upstream file docs/source/getting_started.rst and compare it with the linked rendered Getting Started page. Update the ja_JP documentation to reflect the shown title, navigation, application-stack content, and image; done means the localized page matches the supplied source changes.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.