Issue Token: settings recs

content/tutorials/use-tokens/issue-a-fungible-token.md

@@ -29,7 +29,13 @@ This page provides examples that use [ripple-lib for JavaScript](get-started-wit
 {% set n = cycler(* range(1,99)) %}
 ### {{n.next()}}. Get Credentials
 
-To transact on the XRP Ledger, you need an address and secret key, and some XRP. For development purposes, you can get these using the following interface:
+To transact on the XRP Ledger, you need an address and secret key, and some XRP. You also need one or more recipients who are willing to hold the tokens you issue: unlike in some other blockchains, in the XRP Ledger you cannot force someone to hold a token they do not want.
+
+The best practice is to use ["cold" and "hot" addresses](issuing-and-operational-addresses.html). The cold address is the **issuer** of the token. The hot address is like a regular user's address that you control. It receives tokens from the cold address, which you can then transfer to other users. A hot address is not strictly necessary, since you could send tokens directly to users from the cold address, but it is useful for this tutorial since you need _someone_ to accept the tokens you issue. In production, you should take extra care of the cold address's cryptographic keys (for example, keeping them offline) because it is much harder to replace a cold address than a hot address, if its cryptographic keys are compromised.
+
+
+
+For purposes of this tutorial, you can get the keys for two addresses using the following interface.
 
 <!-- Special version of generate-step.md for getting sender AND receiver credentials -->
 {% if use_network is undefined or use_network == "Testnet" %}
@@ -74,3 +80,37 @@ main()
 For this tutorial, you can connect directly from your browser by pressing the following button:
 
 {% include '_snippets/interactive-tutorials/connect-step.md' %}
+
+
+### {{n.next()}}. Configure Issuer Settings
+
+First, configure the settings for your cold address (which will become the issuer of your token). Most settings can be reconfigured later, with the following exceptions: <!-- STYLE_OVERRIDE: will -->
+
+- [Default Ripple](rippling.html): **This setting is required** so that users can send your token to each other. It's best to enable it _before_ setting up any trust lines or issuing any tokens.
+- [Require Auth](authorized-trust-lines.html): (Optional) This setting limits your tokens to being held _only_ by accounts you've explicitly approved. You cannot enable this setting if you already have any trust lines or offers for _any_ token.
+
+Other settings you may want to, optionally, configure for your cold address (issuer):
+
+| Setting | Recommended Value | Summary |
+|---|---|---|
+| [Require Destination Tags](require-destination-tags.html) | Enabled or Disabled | Enable if you process withdrawals of your token to outside systems. (For example, your token is a stablecoin.) |
+| Disallow XRP | Enabled | Enable if this address isn't meant to process XRP payments. |
+| [Transfer Fee](transfer-fees.html) | 0–1% | Charge a percentage fee when users send your token to each other. |
+| [Tick Size](tick-size) | 5 | Limit the number of decimal places in exchange rates for your token in the [decentralized exchange](decentralized-exchange.html). Reduces churn of almost-equivalent offers and speeds up price discovery. |
+
+**Note:** Many issuing settings apply equally to all tokens issued by an address, regardless of the currency code. If you want to issue multiple types of tokens in the XRP Ledger with different settings, you should use a different address to issue each different token.
+
+```
+TODO: CODE SAMPLE
+```
+
+### {{n.next()}}. Configure Hot Address Settings
+
+
+### {{n.next()}}. Create Trust Line from Hot to Cold Address
+
+
+### {{n.next()}}. Send Token
+
+
+### {{n.next()}}. Confirm Token Balances