mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-13 11:56:33 +02:00
Readied all user guides for translation
This commit is contained in:
rehrar
parent
010458b5e8
commit
ab82e3cc9f
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Creating an Offline Backup of your Monero Account"
|
||||
title-pre-kick: "Creating an Offline Backup "
|
||||
title-kick: "of your Monero "
|
||||
title-post-kick: "Account"
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
## Operating Systems: Various versions of Linux and Windows 7, 8
|
||||
|
||||
### Wallet Software: Simplewallet
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Creating a Monero wallet"
|
||||
title-pre-kick: "Creating a Monero wallet "
|
||||
title-kick: "on Ubuntu "
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
### Operating Systems: Ubuntu
|
||||
|
||||
- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Easiest way to buy Monero"
|
||||
title-pre-kick: "Easiest way"
|
||||
title-kick: "to buy Monero"
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
## How to obtain Monero
|
||||
|
||||
This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "How to fix stuck funds"
|
||||
title-pre-kick: "Fix "
|
||||
title-kick: "Stuck funds"
|
||||
title-post-kick: ""
|
||||
kick-class: "kicks"
|
||||
icon: "icon_about"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
|
||||
|
||||
- Load your wallet in monero-wallet-cli.
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: Importing the Monero Blockchain from an outside source
|
||||
---
|
||||
|
||||
# Importing the Blockchain to Monero GUI wallet (Windows)
|
||||
|
||||
### Step 1
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
layout: custom
|
||||
title: "User Guides"
|
||||
---
|
||||
<div class="guides">
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
@ -14,11 +10,11 @@ title: "User Guides"
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[Monero Tools](monero_tools.html)
|
||||
[How to make an offline backup](Offline_Backup.html)
|
||||
[Importing the Monero blockchain](importing_blockchain.html)
|
||||
[How to run a node on VPS](vps_run_node.html)
|
||||
[Securely purchasing and storing Monero](securely_purchase.html)
|
||||
[Monero Tools]({{site.baseurl}}/resources/user-guides/monero_tools.html)
|
||||
[How to make an offline backup]({{site.baseurl}}/resources/user-guides/Offline_Backup.html)
|
||||
[Importing the Monero blockchain]({{site.baseurl}}/resources/user-guides/importing_blockchain.html)
|
||||
[How to run a node on VPS]({{site.baseurl}}/resources/user-guides/vps_run_node.html)
|
||||
[Securely purchasing and storing Monero]({{site.baseurl}}/resources/user-guides/securely_purchase.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@ -32,11 +28,11 @@ title: "User Guides"
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[Getting started with the CLI wallet](monero-wallet-cli.html)
|
||||
[How to make a view-only wallet](view_only.html)
|
||||
[How to prove payment](prove-payment.html)
|
||||
[Restoring wallet from keys](restore_from_keys.html)
|
||||
[How to connect to a remote node within GUI wallet](remote_node_gui.html)
|
||||
[Getting started with the CLI wallet]({{site.baseurl}}/resources/user-guides/monero-wallet-cli.html)
|
||||
[How to make a view-only wallet]({{site.baseurl}}/resources/user-guides/view_only.html)
|
||||
[How to prove payment]({{site.baseurl}}/resources/user-guides/prove-payment.html)
|
||||
[Restoring wallet from keys]({{site.baseurl}}/resources/user-guides/restore_from_keys.html)
|
||||
[How to connect to a remote node within GUI wallet]({{site.baseurl}}/resources/user-guides/remote_node_gui.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@ -55,8 +51,8 @@ title: "User Guides"
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[How to fix locked up funds](howto_fix_stuck_funds.html)
|
||||
[How to restore your account](restore_account.html)
|
||||
[How to fix locked up funds]({{site.baseurl}}/resources/user-guides/howto_fix_stuck_funds.html)
|
||||
[How to restore your account]({{site.baseurl}}/resources/user-guides/restore_account.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@ -70,9 +66,9 @@ title: "User Guides"
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[How to solo mine with the GUI](solo_mine_GUI.html)
|
||||
[How to mine on a pool with xmr-stak-cpu](mine-to-pool.html)
|
||||
[Mining with Docker and XMRig](mining_with_xmrig_and_docker.html)
|
||||
[How to solo mine with the GUI]({{site.baseurl}}/resources/user-guides/solo_mine_GUI.html)
|
||||
[How to mine on a pool with xmr-stak-cpu]({{site.baseurl}}/resources/user-guides/mine-to-pool.html)
|
||||
[Mining with Docker and XMRig]({{site.baseurl}}/resources/user-guides/mining_with_xmrig_and_docker.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@ -93,16 +89,16 @@ title: "User Guides"
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[General Web Edit Instructions (READ FIRST!)](website-general.html)
|
||||
[How to make a blog post](website-blog.html)
|
||||
[How to make a User Guide](website-user-guide.html)
|
||||
[How to make a Moneropedia entry](website-moneropedia.html)
|
||||
[How to make a FFS proposal](website-ffs.html)
|
||||
[How to update the Team page](website-team.html)
|
||||
[How to add update Events page](website-events.html)
|
||||
[How to update the Roadmap](website-roadmap.html)
|
||||
[How to add a new Merchant](website-merchants.html)
|
||||
[How to add a new question to the FAQ](website-faq.html)
|
||||
[General Web Edit Instructions (READ FIRST!)]({{site.baseurl}}/resources/user-guides/website-general.html)
|
||||
[How to make a blog post]({{site.baseurl}}/resources/user-guides/website-blog.html)
|
||||
[How to make a User Guide]({{site.baseurl}}/resources/user-guides/website-user-guide.html)
|
||||
[How to make a Moneropedia entry]({{site.baseurl}}/resources/user-guides/website-moneropedia.html)
|
||||
[How to make a FFS proposal]({{site.baseurl}}/resources/user-guides/website-ffs.html)
|
||||
[How to update the Team page]({{site.baseurl}}/resources/user-guides/website-team.html)
|
||||
[How to add update Events page]({{site.baseurl}}/resources/user-guides/website-events.html)
|
||||
[How to update the Roadmap]({{site.baseurl}}/resources/user-guides/website-roadmap.html)
|
||||
[How to add a new Merchant]({{site.baseurl}}/resources/user-guides/website-merchants.html)
|
||||
[How to add a new question to the FAQ]({{site.baseurl}}/resources/user-guides/website-faq.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to mine on a pool with xmr-stak-cpu
|
||||
---
|
||||
# Selecting a pool
|
||||
|
||||
There are many pools to choose from, a list is available at
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Mining with XMRig and Docker"
|
||||
title-pre-kick: "Mining XMR"
|
||||
title-kick: "With XMRig and DOcker"
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
|
||||
|
||||
@ -1,13 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Monero tools"
|
||||
title-pre-kick: "Monero tools "
|
||||
title-kick: "for the network "
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
# monero-wallet-cli
|
||||
|
||||
`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
|
||||
|
||||
@ -1,13 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Monero tools"
|
||||
title-pre-kick: "Monero tools "
|
||||
title-kick: "for the network "
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
# Monero tools
|
||||
|
||||
These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "How to prove payment"
|
||||
title-pre-kick: "Prove "
|
||||
title-kick: "payment"
|
||||
title-post-kick: ""
|
||||
kick-class: "kicks"
|
||||
icon: "icon_about"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
|
||||
|
||||
With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to use a remote node in the GUI wallet
|
||||
---
|
||||
|
||||
## Finding a node
|
||||
First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
|
||||
would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
|
||||
@ -12,4 +7,4 @@ After you enter your password for your wallet, you will see a pop up that will g
|
||||
sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the on to the left) you need to enter the address of the node that you want to
|
||||
connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
|
||||
### Your screen should look a bit like this
|
||||
<img src="/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
|
||||
<img src="{{site.baseurl}}/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Restoring your Monero Wallet"
|
||||
title-pre-kick: "Restoring your "
|
||||
title-kick: "Monero "
|
||||
title-post-kick: "Wallet"
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
## Operating Systems: Windows, Linux, Mac
|
||||
|
||||
### Account Software: monero-wallet-cli
|
||||
|
||||
@ -1,10 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Restoring a wallet from private keys"
|
||||
---
|
||||
|
||||
|
||||
|
||||
Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
|
||||
|
||||
You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
|
||||
|
||||
@ -1,9 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: Securely purchasing and storing Monero
|
||||
---
|
||||
|
||||
|
||||
## How to purchase Monero and securely store it.
|
||||
|
||||
This is a guide to purchase and securely store Monero as of June 2017.
|
||||
|
||||
@ -1,15 +1,4 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "How to solo mine with the GUI"
|
||||
title-pre-kick: "Solo mining with the GUI"
|
||||
title-kick: ""
|
||||
title-post-kick: ""
|
||||
kick-class: ""
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
|
||||
It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="{{site.baseurl}}/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
|
||||
|
||||
<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
|
||||
|
||||
|
||||
@ -1,14 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "View Only Wallets"
|
||||
title-pre-kick: "Creating a view only wallet "
|
||||
title-kick: ""
|
||||
title-post-kick: ""
|
||||
kick-class: ""
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
|
||||
A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
|
||||
|
||||
* Developers writing libraries to validate payments
|
||||
|
||||
@ -1,13 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: "Monero tools"
|
||||
title-pre-kick: "Monero tools "
|
||||
title-kick: "for the network "
|
||||
title-post-kick: ""
|
||||
kick-class: "purple-kicks"
|
||||
icon: "icon_userguides"
|
||||
attribution: "<!-- Icon is based on work by Freepik (http://www.freepik.com) and is licensed under Creative Commons BY 3.0 -->"
|
||||
---
|
||||
# monerod
|
||||
|
||||
`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to make a blog post
|
||||
---
|
||||
|
||||
### Quick Start
|
||||
* Make new .md file in _posts (named whatever, no spaces)
|
||||
* Front Matter (below)
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to add an event
|
||||
---
|
||||
|
||||
### 9.1 Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `events.yml`. You will notice a list separated by hyphenated `-event` tags.
|
||||
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to add a question to the FAQ
|
||||
---
|
||||
|
||||
### Copy/Paste Code
|
||||
Navigate to the `/get-started/faq` folder and open the `index.md` file. Inside you will see HTML code, but you will see it is very repetetive.
|
||||
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to make a FFS proposal
|
||||
---
|
||||
|
||||
### Quick Start
|
||||
|
||||
* Read [How the Forum Funding System works](#) and the [Forum Funding System Terms and Guidelines](#).
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: General Website Instructions
|
||||
---
|
||||
|
||||
### Introduction
|
||||
|
||||
This README here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new getmonero.org website. It'll definitely be a bit of a ride, so strap yourself in. Please note that translations are not available yet, but when they are added, this document will be updated with instructions on how to translate the content of getmonero.org. In the meantime, any help translating this document into another language is greatly appreciated.
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to add a new merchant
|
||||
---
|
||||
|
||||
### Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `merchants.yml`. You will notice a list separated by hyphenated `-category` tags.
|
||||
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to add a Moneropedia entry
|
||||
---
|
||||
|
||||
### Make a file
|
||||
Navigate to the /resources/moneropedia folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to update the Roadmap
|
||||
---
|
||||
|
||||
### Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `roadmap.yml`. You will notice a list separated by hyphenated `-year` tags.
|
||||
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to update the Team page
|
||||
---
|
||||
|
||||
If you are acting on behalf of another individual, please make sure you get their permission first before adding them onto the Team page.
|
||||
|
||||
### Change the .yml file
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
---
|
||||
layout: static_page
|
||||
title: How to make a User Guide
|
||||
---
|
||||
|
||||
### Quick Start
|
||||
|
||||
* Make file in /resources/user-guides with a .md ending and no spaces in filename.
|
||||
|
||||
@ -0,0 +1,48 @@
|
||||
## How to mine Monero (XMR) without a mining equipment?
|
||||
|
||||
If you don’t have a profitable mining equipment, nor time or
|
||||
money to invest into building it, you can still mine Monero with NiceHash.
|
||||
|
||||
NiceHash is a hashing power marketplace. Sellers of hashing
|
||||
power, i.e. miners, provide the hashing power for buyers (those who want to buy
|
||||
a service of mining a certain coin). Hence, NiceHash can provide you a massive
|
||||
hashing power in short amount of time. You won’t have to wait for years to see
|
||||
if you will make a profit or not and you can control which coin, at which pool,
|
||||
and for how long you want to mine.
|
||||
|
||||
### **Step 1:** Create new account at NiceHash
|
||||
|
||||
Visit [registration
|
||||
page](https://www.nicehash.com/?p=register) and register with your e-mail address.
|
||||
|
||||
### **Step 2:** Deposit some Bitcoins to your account
|
||||
|
||||
You will mine Monero, but you can buy hashing power at
|
||||
NiceHash only with Bitcoins. You can always withdraw unspent Bitcoins from your
|
||||
account back to any Bitcoin wallet.
|
||||
|
||||
Visit your [wallet
|
||||
page](https://www.nicehash.com/?p=wallet) and make a deposit. Note that the minimum price for placing an order
|
||||
equals 0.01 BTC.
|
||||
|
||||
### **Step 3:** Find a suitable pool for mining and add it to your pool list
|
||||
|
||||
Selection of the pool plays a big role in the final amount
|
||||
of mined cryptocurrency. Make sure the pool you have selected can handle
|
||||
massive hashing rate and loads of shares, especially from a single connection.
|
||||
You can find a list of Monero pools [here](https://bitcointalk.org/index.php?topic=583449.0).
|
||||
|
||||
Note that you will probably have to register an account at
|
||||
selected pool as well. The pool will provide you with all the information you need.
|
||||
You can save your favorite pools at [this page](https://www.nicehash.com/?p=managepools).
|
||||
|
||||
### **Step 4:** Create new order and start mining
|
||||
|
||||
When creating a [new order](https://www.nicehash.com/?p=orders&new), make sure you
|
||||
select CryptoNight algorithm for mining Monero. If you want to first learn more
|
||||
about placing an order with NiceHash, we recommend you to read this [frequently asked question](https://www.nicehash.com/?p=faq#faqb0).
|
||||
|
||||
If you want to bid on
|
||||
hashing power select Standard (bidding) order type and if you want a fixed
|
||||
order that cannot be outbid, select Fixed order type. The status of marketplace
|
||||
and approximate prices of mining can be checked at [live marketplace](https://www.nicehash.com/index.jsp?p=orders).
|
||||
36
_i18n/es/resources/user-guides/Offline_Backup.md
Normal file
36
_i18n/es/resources/user-guides/Offline_Backup.md
Normal file
@ -0,0 +1,36 @@
|
||||
## Operating Systems: Various versions of Linux and Windows 7, 8
|
||||
|
||||
### Wallet Software: Simplewallet
|
||||
|
||||
#### Resource for Creating Bootable Disks: [Linux](http://www.pendrivelinux.com/), [Windows](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
|
||||
|
||||
#### Resource for Monero Binaries: [Monero Binaries](https://getmonero.org/downloads/)
|
||||
|
||||
- Take any computer you have lying around, even your normal workstation. You may find it easier to use an older computer that has no wifi or bluetooth if you're particularly paranoid
|
||||
|
||||
- Create a Linux or Windows bootable disk, and make sure you have the Monero binaries on the same disk or on a second disk (for Linux make sure you have also downloaded copies of the dependencies you will need, libboost1.55 and miniupnpc for instance)
|
||||
|
||||
- Disconnect the network and/or Internet cables from your computer, physically remove the wifi card or switch the wifi/bluetooth off on a laptop if possible
|
||||
|
||||
- Boot into your bootable OS, install the dependencies if necessary
|
||||
|
||||
- Copy the Monero binaries to a RAM disk (/dev/shm in Linux, Windows bootable ISOs normally have a Z: drive or something)
|
||||
|
||||
- Don't run the Monero daemon. Instead, using the command line, use monero-wallet-cli to create a new Monero @account
|
||||
|
||||
- When prompted for a name, give it any name, it doesn't really matter
|
||||
|
||||
- When prompted for a password, type in like 50 - 100 random characters. Don't worry that you don't know the password, just make it LONG
|
||||
|
||||
- **CRITICAL STEP**: Write down (on paper) your 25 word @mnemonic-seed
|
||||
**WARNING**: If you forget to write down this information your funds may be lost forever
|
||||
|
||||
- Write down (on your phone, on paper, on another computer, wherever you want) your address and view key
|
||||
|
||||
- Switch off the computer, remove the battery if there is one, and leave it physically off for a few hours
|
||||
|
||||
The account you've created was created in RAM, and the digital files are now inaccessible. If some adversary manages to somehow obtain the data, they will lack the long password to open it. If you need to receive payments, you have your public address, and you have the view key if needed. If you need access to it, you have your 25 word @mnemonic-seed, and you can now write out several copies of it, including an offsite copy (e.g. a bank deposit box).
|
||||
|
||||
Credit: Riccardo Spagni
|
||||
|
||||
Related: [Offline Account Generator](http://moneroaddress.org/)
|
||||
60
_i18n/es/resources/user-guides/create_wallet.md
Normal file
60
_i18n/es/resources/user-guides/create_wallet.md
Normal file
@ -0,0 +1,60 @@
|
||||
### Operating Systems: Ubuntu
|
||||
|
||||
- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
|
||||
|
||||
|
||||
|
||||
|
||||
- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
|
||||
|
||||
|
||||
|
||||
|
||||
- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
|
||||
|
||||
|
||||
|
||||
|
||||
- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
|
||||
|
||||
|
||||
|
||||
- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
|
||||
|
||||
|
||||
|
||||
- Enter the name you want for your portfolio and follow the instructions from the terminal
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
*This is your private key. Write it down and keep it in a safe place!*
|
||||
|
||||
|
||||
|
||||
*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
|
||||
|
||||
|
||||
|
||||
*This is the address of your wallet*
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
|
||||
|
||||
Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
|
||||
|
||||
|
||||
64
_i18n/es/resources/user-guides/easiest_buy.md
Normal file
64
_i18n/es/resources/user-guides/easiest_buy.md
Normal file
@ -0,0 +1,64 @@
|
||||
## How to obtain Monero
|
||||
|
||||
This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
|
||||
|
||||
####Step 1: Buy Bitcoin
|
||||
|
||||
There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
|
||||
|
||||
####Step 2: Set up a mymonero.com account
|
||||
|
||||
MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
|
||||
|
||||
|
||||
|
||||
After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
|
||||
|
||||
### WRITE DOWN THIS KEY IMMEDIATELY!
|
||||
|
||||
|
||||
|
||||
Type in your private key in the box below, and click the button.
|
||||
|
||||
On the next page, you will see your address.
|
||||
|
||||
|
||||
|
||||
Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
|
||||
|
||||
#### Step 3: Buy Monero and transfer the Monero to your new address
|
||||
|
||||
Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
|
||||
|
||||
|
||||
|
||||
|
||||
Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
|
||||
|
||||
|
||||
|
||||
In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
|
||||
|
||||
|
||||
|
||||
Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
|
||||
Enter the amount of Bitcoin you would like to spend.
|
||||
|
||||
|
||||
|
||||
|
||||
You will get a text message verification code. Enter code and hit send.
|
||||
|
||||
|
||||
|
||||
You will see the shapeshift change to "awaiting exchange"
|
||||
|
||||
|
||||
|
||||
Then it will change to COMPLETE!
|
||||
|
||||
|
||||
|
||||
After a while you will see it in your Monero account
|
||||
|
||||
|
||||
30
_i18n/es/resources/user-guides/howto_fix_stuck_funds.md
Normal file
30
_i18n/es/resources/user-guides/howto_fix_stuck_funds.md
Normal file
@ -0,0 +1,30 @@
|
||||
Sometimes, your funds will become stuck - you will have some locked funds that never become unlocked. This is how you fix it.
|
||||
|
||||
- Load your wallet in monero-wallet-cli.
|
||||
|
||||
- Type
|
||||
|
||||
> seed
|
||||
|
||||
into the command prompt. Write down your 25 word seed, if you haven't already. This is the best way to make sure you don't loose access to your funds.
|
||||
|
||||
- Close monero-wallet-cli by typing
|
||||
|
||||
> exit
|
||||
|
||||
- Backup all of your wallet related files. These include:
|
||||
|
||||
> yourwalletname.bin
|
||||
> yourwalletname.bin.keys
|
||||
> yourwalletname.bin.address.txt
|
||||
|
||||
This can be done by copying the files to a new folder.
|
||||
|
||||
Sometimes, when creating your wallet, you might have named it something without the .bin part. In that case, the wallet file will be called yourwalletname without the .bin at the end.
|
||||
|
||||
- Delete yourwallet.bin
|
||||
|
||||
- Load monero-wallet-cli, type in the name of the wallet you just deleted
|
||||
|
||||
- Enter password. The wallet will now refresh and hopefully your locked funds will now become unlocked.
|
||||
|
||||
56
_i18n/es/resources/user-guides/importing_blockchain.md
Normal file
56
_i18n/es/resources/user-guides/importing_blockchain.md
Normal file
@ -0,0 +1,56 @@
|
||||
# Importing the Blockchain to Monero GUI wallet (Windows)
|
||||
|
||||
### Step 1
|
||||
|
||||
Download the Current bootstrap from https://downloads.getmonero.org/blockchain.raw; you can skip this step if you are importing the Blockchain from another source.
|
||||
|
||||
### Step 2
|
||||
|
||||
Find the path of your Monero wallet (the folder where you extracted your wallet). For example mine is:
|
||||
|
||||
`D:\monero-gui-0.10.3.1`
|
||||
|
||||
Your path may be different depending on where you decided to download your wallet and what version of the Monero wallet you have.
|
||||
|
||||
### Step 3
|
||||
|
||||
Find the path of your downloaded Blockchain for example mine was:
|
||||
|
||||
`C:\Users\KeeJef\Downloads\blockchain.raw`
|
||||
|
||||
Yours might be different depending on where you downloaded the Blockchain to.
|
||||
|
||||
### Step 4
|
||||
|
||||
Open a Command Prompt window. You can do this by pressing the Windows key + R, and then typing in the popup box `CMD`
|
||||
|
||||
### Step 5
|
||||
|
||||
Now you need to navigate using the CMD window to the path of your Monero wallet. You can do this by typing:
|
||||
|
||||
`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
|
||||
|
||||
It should look something like:
|
||||
|
||||
`cd D:\monero-gui-0.10.3.1`
|
||||
|
||||
If your Monero wallet is on another drive you can use `DriveLetter:` for example if your Monero wallet was on your D drive then before using the cd command you would do `D:`
|
||||
|
||||
### Step 6
|
||||
|
||||
Now type in your command prompt window:
|
||||
|
||||
`monero-blockchain-import --verify 1 --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
|
||||
|
||||
For example I would type :
|
||||
|
||||
`monero-blockchain-import --verify 1 --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
|
||||
|
||||
If you downloaded the Blockchain from a trusted, reputable source you may set `verify 0` this will reduce the amount of time to sync the Blockchain.
|
||||
|
||||
### Step 7
|
||||
|
||||
After the the Blockchain has finished syncing up you can open your Monero wallet normally. Your downloaded blockchain.raw can be deleted.
|
||||
|
||||
|
||||
Author: Kee Jefferys
|
||||
123
_i18n/es/resources/user-guides/index.md
Normal file
123
_i18n/es/resources/user-guides/index.md
Normal file
@ -0,0 +1,123 @@
|
||||
<div class="guides">
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
<div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>General</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[Monero Tools]({{site.baseurl}}/resources/user-guides/monero_tools.html)
|
||||
[How to make an offline backup]({{site.baseurl}}/resources/user-guides/Offline_Backup.html)
|
||||
[Importing the Monero blockchain]({{site.baseurl}}/resources/user-guides/importing_blockchain.html)
|
||||
[How to run a node on VPS]({{site.baseurl}}/resources/user-guides/vps_run_node.html)
|
||||
[Securely purchasing and storing Monero]({{site.baseurl}}/resources/user-guides/securely_purchase.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Wallets</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[Getting started with the CLI wallet]({{site.baseurl}}/resources/user-guides/monero-wallet-cli.html)
|
||||
[How to make a view-only wallet]({{site.baseurl}}/resources/user-guides/view_only.html)
|
||||
[How to prove payment]({{site.baseurl}}/resources/user-guides/prove-payment.html)
|
||||
[Restoring wallet from keys]({{site.baseurl}}/resources/user-guides/restore_from_keys.html)
|
||||
[How to connect to a remote node within GUI wallet]({{site.baseurl}}/resources/user-guides/remote_node_gui.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
<div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Recovery</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[How to fix locked up funds]({{site.baseurl}}/resources/user-guides/howto_fix_stuck_funds.html)
|
||||
[How to restore your account]({{site.baseurl}}/resources/user-guides/restore_account.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Mining</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[How to solo mine with the GUI]({{site.baseurl}}/resources/user-guides/solo_mine_GUI.html)
|
||||
[How to mine on a pool with xmr-stak-cpu]({{site.baseurl}}/resources/user-guides/mine-to-pool.html)
|
||||
[Mining with Docker and XMRig]({{site.baseurl}}/resources/user-guides/mining_with_xmrig_and_docker.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
</section>
|
||||
<section class="container">
|
||||
<div class="row">
|
||||
<div class="left half no-pad-sm col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Website</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
|
||||
[General Web Edit Instructions (READ FIRST!)]({{site.baseurl}}/resources/user-guides/website-general.html)
|
||||
[How to make a blog post]({{site.baseurl}}/resources/user-guides/website-blog.html)
|
||||
[How to make a User Guide]({{site.baseurl}}/resources/user-guides/website-user-guide.html)
|
||||
[How to make a Moneropedia entry]({{site.baseurl}}/resources/user-guides/website-moneropedia.html)
|
||||
[How to make a FFS proposal]({{site.baseurl}}/resources/user-guides/website-ffs.html)
|
||||
[How to update the Team page]({{site.baseurl}}/resources/user-guides/website-team.html)
|
||||
[How to add update Events page]({{site.baseurl}}/resources/user-guides/website-events.html)
|
||||
[How to update the Roadmap]({{site.baseurl}}/resources/user-guides/website-roadmap.html)
|
||||
[How to add a new Merchant]({{site.baseurl}}/resources/user-guides/website-merchants.html)
|
||||
[How to add a new question to the FAQ]({{site.baseurl}}/resources/user-guides/website-faq.html)
|
||||
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="right half col-lg-6 col-md-6 col-sm-12 col-xs-12">
|
||||
<div class="info-block">
|
||||
<div class="row center-xs">
|
||||
<div class="col">
|
||||
<h2>Miscellaneous</h2>
|
||||
</div>
|
||||
</div>
|
||||
<div class="row start-xs" markdown="1">
|
||||
Coming Soon
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
</section>
|
||||
</div>
|
||||
113
_i18n/es/resources/user-guides/mine-to-pool.md
Normal file
113
_i18n/es/resources/user-guides/mine-to-pool.md
Normal file
@ -0,0 +1,113 @@
|
||||
# Selecting a pool
|
||||
|
||||
There are many pools to choose from, a list is available at
|
||||
[moneropools.com](https://moneropools.com). Mining on a larger pool could mean
|
||||
more frequent payouts, but mining on a smaller pool helps to keep the network
|
||||
decentralized.
|
||||
|
||||
# Selecting a CPU miner
|
||||
|
||||
Just like pools, there are a lot of miners to choose from. The one that you
|
||||
should pick depends on the hardware you want to mine on. This guide will only
|
||||
use a CPU miner, and will be using
|
||||
[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). Alternatives include
|
||||
[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) and
|
||||
[sgminer-gm](https://github.com/genesismining/sgminer-gm). However, their
|
||||
configuration is slightly different and will not be covered in this guide.
|
||||
|
||||
## For Windows Systems
|
||||
|
||||
If you are using a Windows system, the developer of xmr-stak-cpu provides
|
||||
binaries to download on the
|
||||
[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
|
||||
|
||||
Download `xmr-stak-cpu-win64.zip` and extract it somewhere you'll be able to
|
||||
find it again.
|
||||
|
||||
## For Other Operating Systems
|
||||
|
||||
If you're not using Windows, you will have to compile xmr-stak-cpu for yourself,
|
||||
luckily this isn't as hard as it sounds. Before you can compile the miner, you
|
||||
will need to install some of its prerequisites.
|
||||
|
||||
For Debian-based distros:
|
||||
|
||||
sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
|
||||
|
||||
For Red Hat based distros:
|
||||
|
||||
sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
|
||||
|
||||
<!-- TODO: Add dependencies for other operating systems? -->
|
||||
|
||||
Following this, you just need to use cmake to generate the build files, run
|
||||
make and copy the config file:
|
||||
|
||||
mkdir build-$(gcc -dumpmachine)
|
||||
cd $_
|
||||
cmake ../
|
||||
make -j$(nproc)
|
||||
cp ../config.txt bin/
|
||||
cd bin
|
||||
|
||||
Don't celebrate just yet, as the miner needs to be configured. Running the miner
|
||||
now should give you a block of text to copy and paste:
|
||||
|
||||
|
||||
|
||||
Open `config.txt` and *replace* the two `"cpu_threads_conf"` lines with the text
|
||||
you just copied. It should look something like this afterwards:
|
||||
|
||||
|
||||
|
||||
Scroll down in the file until you see the lines containing `"pool_address"`.
|
||||
*Replace* the contents of the second set of quotes with the address and port of
|
||||
the pool you chose earlier. You can find this information on the pool's website.
|
||||
|
||||
Put your wallet address between the quotes on the wallet address. You may leave
|
||||
the password blank unless the pool specifies otherwise.
|
||||
|
||||
After this, your config should look something like this:
|
||||
|
||||
|
||||
|
||||
# Running the miner
|
||||
|
||||
**Save the config** file and run the miner!
|
||||
|
||||
|
||||
|
||||
Some pools allow you to monitor your hashrate by pasting your address into their
|
||||
website. You can also monitor your hashrate by pressing the `h` key.
|
||||
|
||||
# Tuning the miner
|
||||
|
||||
You might see nasty messages like this:
|
||||
|
||||
[2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
|
||||
|
||||
This means that you can get around a 20% hashrate boost by enabling large pages.
|
||||
|
||||
## Large pages on Linux
|
||||
|
||||
Firstly stop the miner (if it's running), run the following commands to enable
|
||||
large pages and then start the miner as root:
|
||||
|
||||
sudo sysctl -w vm.nr_hugepages=128
|
||||
sudo ./xmr-stak-cpu
|
||||
|
||||
## Large pages on Windows
|
||||
|
||||
Taken from `config.txt`:
|
||||
|
||||
>By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows
|
||||
You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
|
||||
1. On the Start menu, click Run. In the Open box, type gpedit.msc.
|
||||
2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
|
||||
3. Expand Security Settings, and then expand Local Policies.
|
||||
4. Select the User Rights Assignment folder.
|
||||
5. The policies will be displayed in the details pane.
|
||||
6. In the pane, double-click Lock pages in memory.
|
||||
7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
|
||||
8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
|
||||
9. Reboot for change to take effect.
|
||||
@ -0,0 +1,36 @@
|
||||
## Introduction
|
||||
|
||||
This guide is two fold, ease of use for mining on Linux distributions and some extra security around mining as most of these miners have not had security auditing.
|
||||
|
||||
At the end of this guide you will be able to sleep a little easier knowing that if the miner gets exploited it will not migrate to your OS.
|
||||
|
||||
### Why Docker
|
||||
|
||||
[Docker](https://www.docker.com/) is being used as it is the most well known and has the biggest chance to be already installed.
|
||||
|
||||
The container I an using is [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) as per the name it is built on the [Alpine Linux](https://www.alpinelinux.org/) image.
|
||||
|
||||
If you are interested in getting started with Docker, here are some really good starting references.
|
||||
* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
|
||||
* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
|
||||
* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
|
||||
|
||||
For distribution specific installation please refer to the [Docker Docs](https://docs.docker.com/engine/installation/) website.
|
||||
|
||||
### Why XMRig
|
||||
|
||||
[XMRig](https://github.com/xmrig/xmrig) is just a really solid miner to me. Nice output and statistics, no flashy web-ui's or dependencies. The XMRig container is only ~4MB what makes it extremely portable.
|
||||
|
||||
#### Step 1: Mining with XMRig
|
||||
|
||||
Run the following
|
||||
|
||||
```bash
|
||||
# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
|
||||
# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
|
||||
```
|
||||
|
||||
#### Step 2: There is no Step 2
|
||||
|
||||
You have already done everything you need to do. You are now mining in a docker container with XMRig `ctrl+c` to exit the miner or add `-d` just after `docker run` to background the miner.
|
||||
|
||||
145
_i18n/es/resources/user-guides/monero-wallet-cli.md
Normal file
145
_i18n/es/resources/user-guides/monero-wallet-cli.md
Normal file
@ -0,0 +1,145 @@
|
||||
# monero-wallet-cli
|
||||
|
||||
`monero-wallet-cli` is the wallet software that ships with the Monero tree. It is a console program,
|
||||
and manages an account. While a bitcoin wallet manages both an account and the blockchain,
|
||||
Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
|
||||
|
||||
This guide will show how to perform various operations from the `monero-wallet-cli` UI. The guide assumes you are using the most recent version of Monero and have already created an account according to the other guides.
|
||||
|
||||
|
||||
## Checking your balance
|
||||
|
||||
Since the blockchain handling and the wallet are separate programs, many uses of `monero-wallet-cli`
|
||||
need to work with the daemon. This includes looking for incoming transactions to your address.
|
||||
Once you are running both `monero-wallet-cli` and `monerod`, enter `balance`.
|
||||
|
||||
Example:
|
||||
|
||||
This will pull blocks from the daemon the wallet did not yet see, and update your balance
|
||||
to match. This process will normally be done in the background every minute or so. To see the
|
||||
balance without refreshing:
|
||||
|
||||
balance
|
||||
Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
|
||||
|
||||
In this example, `Balance` is your total balance. The `unlocked balance` is the amount currently available to spend. Newly received transactions require 10 confirmations on the blockchain before being unlocked. `unlocked dust` refers to very small amounts of unspent outputs that may have accumulated in your account.
|
||||
|
||||
## Sending monero
|
||||
|
||||
You will need the standard address you want to send to (a long string starting with '4'), and
|
||||
possibly a payment ID, if the receiving party requires one. In that latter case, that party
|
||||
may instead give you an integrated address, which is both of these packed into a single address.
|
||||
|
||||
### Sending to a standard address:
|
||||
|
||||
transfer ADDRESS AMOUNT PAYMENTID
|
||||
|
||||
Replace `ADDRESS` with the address you want to send to, `AMOUNT` with how many monero you want to send,
|
||||
and `PAYMENTID` with the payment ID you were given. Payment ID's are optional. If the receiving party doesn't need one, just
|
||||
omit it.
|
||||
|
||||
### Sending to an integrated address:
|
||||
|
||||
transfer ADDRESS AMOUNT
|
||||
|
||||
The payment ID is implicit in the integrated address in that case.
|
||||
|
||||
### Specify the number of outputs for a transaction:
|
||||
|
||||
transfer MIXIN ADDRESS AMOUNT
|
||||
|
||||
Replace `MIXIN` with the number of outputs you wish to use. **If not specified, the default is 4.** It's a good idea to use the default, but you can increase the number if you want to include more outputs. The higher the number, the larger the transaction, and higher fees are needed.
|
||||
|
||||
|
||||
## Receiving monero
|
||||
|
||||
If you have your own Monero address, you just need to give your standard address to someone.
|
||||
|
||||
You can find out your address with:
|
||||
|
||||
address
|
||||
|
||||
Since Monero is anonymous, you won't see the origin address the funds you receive came from. If you
|
||||
want to know, for instance to credit a particular customer, you'll have to tell the sender to use
|
||||
a payment ID, which is an arbitrary optional tag which gets attached to a transaction. To make life
|
||||
easier, you can generate an address that already includes a random payment ID:
|
||||
|
||||
integrated_address
|
||||
|
||||
This will generate a random payment ID, and give you the address that includes your own account
|
||||
and that payment ID. If you want to select a particular payment ID, you can do that too:
|
||||
|
||||
integrated_address 12346780abcdef00
|
||||
|
||||
Payments made to an integrated address generated from your account will go to your account,
|
||||
with that payment id attached, so you can tell payments apart.
|
||||
|
||||
|
||||
## Proving to a third party you paid someone
|
||||
|
||||
If you pay a merchant, and the merchant claims to not have received the funds, you may need
|
||||
to prove to a third party you did send the funds - or even to the merchant, if it is a honest
|
||||
mistake. Monero is private, so you can't just point to your transaction in the blockchain,
|
||||
as you can't tell who sent it, and who received it. However, by supplying the per-transaction
|
||||
private key to a party, that party can tell whether that transaction sent monero to that
|
||||
particular address. Note that storing these per-transaction keys is disabled by default, and
|
||||
you will have to enable it before sending, if you think you may need it:
|
||||
|
||||
set store-tx-info 1
|
||||
|
||||
You can retrieve the tx key from an earlier transaction:
|
||||
|
||||
get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
|
||||
|
||||
Pass in the transaction ID you want the key for. Remember that a payment might have been
|
||||
split in more than one transaction, so you may need several keys. You can then send that key,
|
||||
or these keys, to whoever you want to provide proof of your transaction, along with the
|
||||
transaction id and the address you sent to. Note that this third party, if knowing your
|
||||
own address, will be able to see how much change was returned to you as well.
|
||||
|
||||
If you are the third party (that is, someone wants to prove to you that they sent monero
|
||||
to an address), then you can check this way:
|
||||
|
||||
check_tx_key TXID TXKEY ADDRESS
|
||||
|
||||
Replace `TXID`, `TXKEY` and `ADDRESS` with the transaction ID, per-transaction key, and destination
|
||||
address which were supplied to you, respectively. monero-wallet-cli will check that transaction
|
||||
and let you know how much monero this transaction paid to the given address.
|
||||
|
||||
|
||||
## Getting a chance to confirm/cancel payments
|
||||
|
||||
If you want to get a last chance confirmation when sending a payment:
|
||||
|
||||
set always-confirm-transfers 1
|
||||
|
||||
|
||||
## How to find a payment to you
|
||||
|
||||
If you received a payment using a particular payment ID, you can look it up:
|
||||
|
||||
payments PAYMENTID
|
||||
|
||||
You can give more than one payment ID too.
|
||||
|
||||
More generally, you can review incoming and outgoing payments:
|
||||
|
||||
show_transfers
|
||||
|
||||
You can give an optional height to list only recent transactions, and request
|
||||
only incoming or outgoing transactions. For example,
|
||||
|
||||
show_transfers in 650000
|
||||
|
||||
will only incoming transfers after block 650000. You can also give a height
|
||||
range.
|
||||
|
||||
If you want to mine, you can do so from the wallet:
|
||||
|
||||
start_mining 2
|
||||
|
||||
This will start mining on the daemon usin two threads. Note that this is solo mining,
|
||||
and may take a while before you find a block. To stop mining:
|
||||
|
||||
stop_mining
|
||||
|
||||
17
_i18n/es/resources/user-guides/monero_tools.md
Normal file
17
_i18n/es/resources/user-guides/monero_tools.md
Normal file
@ -0,0 +1,17 @@
|
||||
# Monero tools
|
||||
|
||||
These tools can be used to gain information about the Monero network or your transaction data in the blockchain.
|
||||
|
||||
### [Check that a recipient has received your funds](http://xmrtests.llcoins.net/checktx.html)
|
||||
|
||||
### [Tools for monero address generation](https://xmr.llcoins.net/)
|
||||
|
||||
### [Monero node count](http://moneronodes.i2p.xyz/)
|
||||
|
||||
### [Monero node map](https://monerohash.com/nodes-distribution.html)
|
||||
|
||||
### [Monero offline wallet generator](http://moneroaddress.org/)
|
||||
|
||||
### [Monero network statistics](http://moneroblocks.info/stats)
|
||||
|
||||
### [Monero.how statistics](https://www.monero.how/)
|
||||
51
_i18n/es/resources/user-guides/prove-payment.md
Normal file
51
_i18n/es/resources/user-guides/prove-payment.md
Normal file
@ -0,0 +1,51 @@
|
||||
When you send money to a party who then disputes the payment was made, you need to be able to prove the payment was made.
|
||||
|
||||
With Bitcoin, this is typically done by looking up the transaction ID, where the origin and destination addresses are
|
||||
shown, along with the amount transacted.
|
||||
|
||||
Monero, however, is private: that information is not available publicly on the blockchain. The steps are therefore a bit
|
||||
more involved.
|
||||
|
||||
To prove to Charlie that she made a payment to Bob, Alice must supply Charlie three pieces of information:
|
||||
|
||||
- the transaction ID, as is done in Bitcoin
|
||||
- Bob's address, as is done with Bitcoin
|
||||
- the transaction's key, which is new with Monero and other CryptoNote currencies
|
||||
|
||||
When Alice made the transaction, a one time key was automatically generated just for this transaction. Alice can
|
||||
query it thus in monero-wallet-cli (new name for the old simplewallet):
|
||||
|
||||
> get_tx_key TXID
|
||||
|
||||
Alice would plug in her actual transaction ID instead of this TXID placeholder. All being well, the one time transaction key
|
||||
will be displayed.
|
||||
|
||||
Note that this will only work if monero-wallet-cli is set to save transaction keys. To double check:
|
||||
|
||||
> set
|
||||
|
||||
If it's set to 0, set it to 1:
|
||||
|
||||
> set store-tx-info 1
|
||||
|
||||
Alice can now send Charlie the transaction key along with transaction ID and Bob's address.
|
||||
|
||||
Note: if several transactions were made, this needs repeating for each such transaction.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Charlie now received those three pieces of information, and wants to check Alice is telling the truth: on an up to date
|
||||
blockchain, Charlie types in monero-wallet-cli:
|
||||
|
||||
> check_tx_key TXID TXKEY ADDRESS
|
||||
|
||||
The information supplied by Alice plugs neatly instead of the placeholders. monero-wallet-cli will use the transaction
|
||||
key to decode the transaction, and display how much this particular transaction sent to this address. Obviously,
|
||||
Charlie will want to double check with Bob the address is really his - same as with Bitcoin.
|
||||
|
||||
Alternatively, the transaction key can be obtained in the GUI in the History tab. Click on details for each individual transaction to get the key.
|
||||
|
||||
Note: if several transactions were made, this needs repeating for each such transaction.
|
||||
|
||||
|
||||
10
_i18n/es/resources/user-guides/remote_node_gui.md
Normal file
10
_i18n/es/resources/user-guides/remote_node_gui.md
Normal file
@ -0,0 +1,10 @@
|
||||
## Finding a node
|
||||
First things first, you need to find a node to connect to! [moneroworld.com](https://moneroworld.com/#nodes) has some great resources for finding nodes. One of the easiest methods
|
||||
would be to use a node run by moneroworld, but they have a tool for finding random nodes too.
|
||||
|
||||
## Connecting to the node from the GUI wallet
|
||||
After you enter your password for your wallet, you will see a pop up that will give you the option to "use custom settings". Click on it. You will then be
|
||||
sent to the "Settings" page in the GUI. At this point you should see two text boxes to the right of a label that says "Daemon address". In the first box (the on to the left) you need to enter the address of the node that you want to
|
||||
connect to. This address might look like `node.moneroworld.com` or it could look like any old ip address. The smaller box to the right is where you enter the node's port. The default port is `18081` but if you are using a random node the port that is used will vary. The port for node.moneroworld.com uses 18089.
|
||||
### Your screen should look a bit like this
|
||||
<img src="{{site.baseurl}}/resources/user-guides/png/remote_node/remote-node-screenshot.png" width="600">
|
||||
22
_i18n/es/resources/user-guides/restore_account.md
Normal file
22
_i18n/es/resources/user-guides/restore_account.md
Normal file
@ -0,0 +1,22 @@
|
||||
## Operating Systems: Windows, Linux, Mac
|
||||
|
||||
### Account Software: monero-wallet-cli
|
||||
|
||||
- Retrieve your 25 word @mnemonic-seed that you saved when creating your old Monero @wallet
|
||||
|
||||
- Open a command prompt and navigate to the drive and directory that contains monero-wallet-cli
|
||||
|
||||
- At the command prompt type: `monero-wallet-cli --restore-deterministic-wallet`
|
||||
|
||||
- Once you press enter you will be prompted for a wallet file name. Give your wallet a new name, any name will do
|
||||
|
||||
- Press enter again and you will be prompted for a password. Give your wallet a new and long password
|
||||
|
||||
- Press enter again you will be prompted to repeat the password
|
||||
|
||||
- Press enter again and you will be prompted for the 25 word electrum style mnemonic seed that you retrieved earlier
|
||||
|
||||
- You will then be prompted with "Restore from specific blockchain height (optional, default 0):" Default will start the restore process from the beginning of the Monero blockchain. If you don't know the specific blockchain height, just hit enter. (Specifying a specific blockchain height will start the restore process from that specific height. This will save a bit of time in scanning, if you know what starting blockchain height your initial funds were transacted for this specific account.)
|
||||
|
||||
After you have entered the 25 word mnemonic seed and have chosen your specific blockchain height, monero-wallet-cli will generate the same public address and view key as your old wallet and begin the refresh process automatically. (Please be patient as the refresh process may take a while.)
|
||||
|
||||
18
_i18n/es/resources/user-guides/restore_from_keys.md
Normal file
18
_i18n/es/resources/user-guides/restore_from_keys.md
Normal file
@ -0,0 +1,18 @@
|
||||
Restoring a wallet from private keys (via the command line) is pretty simple. If you have the necessary information, with this guide you can completely restore your wallet. Note: you do NOT have to have your password to restore from keys.
|
||||
|
||||
You need to have 3 pieces of data from your wallet, or your .keys file which holds this info and the password to decrypt it. The 3 wallet components that you need are:
|
||||
|
||||
1. **Address**
|
||||
2. **Secret Spendkey**
|
||||
3. **Secret Viewkey**
|
||||
|
||||
|
||||
Then run the wallet command:
|
||||
|
||||
`./monero-wallet-cli --generate-from-keys New_Wallet_Name.abc`
|
||||
|
||||
Next, you'll be asked for the Address, the spendkey, the viewkey, and finally the new password for the re-generated wallet.
|
||||
|
||||
Running this with the correct parameters will re-generate your wallet files for you and allow you to set a new password.
|
||||
|
||||
If you run into any trouble, running `./monero-wallet-cli --help` will show you the options available to you at wallet startup. Once you're inside your wallet, running the `help` command will list the help for the commands available to you within the wallet.
|
||||
81
_i18n/es/resources/user-guides/securely_purchase.md
Normal file
81
_i18n/es/resources/user-guides/securely_purchase.md
Normal file
@ -0,0 +1,81 @@
|
||||
## How to purchase Monero and securely store it.
|
||||
|
||||
This is a guide to purchase and securely store Monero as of June 2017.
|
||||
|
||||
#### Step 1: Buy Bitcoin
|
||||
|
||||
There are many ways to buy Bitcoin. Two semi-reliable companies at this time are Xapo <http://www.xapo.com/> and Coinbase <http://www.coinbase.com/>. The process will involve uploading your personal identification (State ID, Passport, etc.) and will take anywhere from 2 to 10 days (or longer). Verify their reputation on Reddit before making a large purchase. Xapo uses Wire Transfer and Coinbase uses Bank Transfer (ACH in the USA). Xapo should be faster than Coinbase. Coinbase also allows small "instant" buys via a debit card but adds a large fee for this option. Once you have purchased Bitcoin, you are ready to convert it to Monero!
|
||||
|
||||
#### Step 2: Download and create a Paper Wallet on a secure and air-gapped computer.
|
||||
|
||||
Download the paper wallet generator at: https://moneroaddress.org and copy it to a USB stick (Direct link: https://github.com/moneromooo-monero/monero-wallet-generator/archive/master.zip).
|
||||
|
||||
Unzip and open the paper wallet generator (monero-wallet-generator.html) into a web browser on an air-gapped computer that hasn't been used before, or has had a clean installation of the OS.
|
||||
|
||||
Your paper wallet will have four important items:
|
||||
|
||||
Monero Public Address
|
||||
The public address is used to receive funds to the wallet. You give this to anyone who will be sending funds to your wallet.
|
||||
|
||||
Monero Mnemonic Seed
|
||||
The mnemonic seed is a method of storing the entire wallet that is easily recognizable to humans. This is all you need to restore your wallet at a later date.
|
||||
|
||||
Monero Private Spend Key
|
||||
The private spend key is used to send funds from the wallet.
|
||||
|
||||
Monero Private View Key
|
||||
The private view key is to view transactions entering the wallet. Commonly this is used to setup a view-only only wallet which can see incoming transactions live on the blockchain as they are sent to a cold storage wallet.
|
||||
|
||||
At this point you have many options. You can print the wallet on paper, save it as a PDF or text on a USB stick, burn it to CD/DVD, etc. Most likely you will want at least two or three copies, stored securely in different locations. If storing digitally, encrypt everything with a strong password. If storing on paper, do not show the wallet to anyone else who can memorize your 25 word key, or take a picture of the wallet without your permission. Sending someone a picture of the wallet is the same as giving away all of your funds.
|
||||
|
||||
Whichever method you chose, be sure there's no copy of the Monero wallet left over on the device you used. You may need to securely delete the Monero wallet if you saved it to a disk, or make sure your printer does not save a copy in memory.
|
||||
|
||||
*If you lose access to your Monero paper wallet the Monero will not be available to you or anyone else, ever. You wont be able to recover them!
|
||||
|
||||
#### Side Note
|
||||
Option to encrypt an XMR mnemonic seed:
|
||||
https://xmr.llcoins.net/
|
||||
Download the html page and place it on your airgapped computer. Check the part "Encrypt/Decrypt Mnemonic Seed" and make sure you use "CN Add" with a decent password. Thanks manicminer5.
|
||||
|
||||
|
||||
|
||||
#### Step 3: Convert your Bitcoin to Monero and have it sent to your Monero Paper Wallet
|
||||
|
||||
Switch to your internet connected computer and go to www.shapeshift.io. Choose "Deposit Bitcoin" and "Receive Monero" (quick).
|
||||
|
||||
Press Continue.
|
||||
|
||||
Your Monero Address (the Monero Public Address on your Monero Paper Wallet)
|
||||
Paste the Monero Public address from your paper wallet where it says "Your Monero Address". But wait, since your Monero Public Address is on an airgapped computer (right?), you can't copy and paste anything... Copy it over by hand, or get a blank USB drive and copy only the Public Address to it.
|
||||
|
||||
Refund Address (Bitcoin Public Address you can receive funds at)
|
||||
Enter a Bitcoin address that you control where a refund can be sent in case there's a problem with the transaction. It's very important that you enter a Bitcoin Public Address you control or can receive funds at. At Xapo and Coinbase this is called a Receive Address and it may change periodically.
|
||||
|
||||
Payment ID
|
||||
Leave Payment ID blank if you are sending to your own Monero wallet or Monero paper wallet.
|
||||
|
||||
Agree to the Terms and hit the slider to make this a "Reusable Address".
|
||||
|
||||
Press "Start Transaction".
|
||||
|
||||
Deposit Address (Shapeshift.io's Public Bitcoin Address created only to receive your funds)
|
||||
In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy). You will send Bitcoin from Xapo/Coinbase to Shapeshift.io via this address.
|
||||
|
||||
Go to your Xapo or Circle account, and find a Transfer or Send button. Paste the Bitcoin Deposit address into the Destination field and enter the amount of bitcoin you would like to have converted to Monero. It must be within the Deposit Min and Deposit Max range specified by Shapeshift.io. Press Send and authorize the transaction, if required.
|
||||
|
||||
Once the send has been initiated by Xapo/Coinbase there will be a delay while the transaction enters the Bitcoin blockchain and awaits confirmation. This may be minutes or hours. You can check if the payment has been sent by looking up the Shapeshift.io Deposit address at blockchain.info. Your transaction to Shapeshift.io will show up there.
|
||||
|
||||
When your Bitcoin transaction has been confirmed, Shapeshift.io will then begin exchanging Bitcoin (BTC) for Monero (XMR) at one of the exchanges and when it's complete, send the Monero to the address of your Cold Storage Paper Wallet! This can take minutes to hours. If there's an issue, contact Shapeshift.io. They have good support.
|
||||
|
||||
When the Shapehift.io webpage says your transaction has been completed, you should now have Monero in your Paper Wallet!
|
||||
|
||||
|
||||
#### Notes and How to Verify Funds
|
||||
Because the Monero blockchain is private and untraceable, you won't be able to lookup your Monero Public Address and confirm that the funds have arrived like you might with Bitcoin. This is good for privacy, but bad for convenience.
|
||||
|
||||
To securely verify the funds have arrived at your wallet, you will need to setup a View Only wallet. This is where that view-key comes in. To create a view-only wallet see the entry: @view-only
|
||||
|
||||
To verify the funds are *still in* your wallet and have not been spent you need to create a Cold Wallet with your mnemonic key (all your funds) on an airgapped computer with an up-to-date copy of the Monero Blockchain. When finished you will have to securely erase the wallet or connect it to the internet and it becomes a Hot Wallet.
|
||||
|
||||
|
||||
|
||||
15
_i18n/es/resources/user-guides/solo_mine_GUI.md
Normal file
15
_i18n/es/resources/user-guides/solo_mine_GUI.md
Normal file
@ -0,0 +1,15 @@
|
||||
It is very easy to solo mine with the official GUI. If you have not done so already, go to the <a href="{{site.baseurl}}/downloads/">Monero downloads page</a> and download the official GUI for your operating system. Then, run the setup and be patient as Monero synchronizes with the network. You should see that it displays "Connected" in the lower left corner.
|
||||
|
||||
<img src="/resources/user-guides/png/solo_mine_GUI/01.PNG" style="width: 600px;"/>
|
||||
|
||||
Click on the "Advanced" tab. You should see that several other options appear. Now click on the "Mining" sub-tab.
|
||||
|
||||
<img src="/resources/user-guides/png/solo_mine_GUI/02.PNG" style="width: 600px;"/>
|
||||
|
||||
You should now have an option to start mining. You can optionally change the number of threads to mine with. For optimal efficiency, you should mine with your CPU's cache divided by 2. You will need to look up your CPU's specs on the manufacturer's website. If you are unsure, leave the number of threads at 1. Click the "Start mining" button.
|
||||
|
||||
<img src="/resources/user-guides/png/solo_mine_GUI/03.PNG" style="width: 600px;"/>
|
||||
|
||||
You are now mining with the network, as you can see on the bottom of the image. In this example, the computer is contributing 23 H/s to the Monero network. Mining helps keep the network secure, and you may get lucky and receive a reward for protecting the network.
|
||||
|
||||
To stop mining, simply click the "Stop mining" button.
|
||||
12
_i18n/es/resources/user-guides/view_only.md
Normal file
12
_i18n/es/resources/user-guides/view_only.md
Normal file
@ -0,0 +1,12 @@
|
||||
A view-only wallet can only see which incoming transactions belong to you. It can not spend any of your Monero, in fact it can't even see outgoing transactions from this wallet. This makes view-only wallets particularly interesting for
|
||||
|
||||
* Developers writing libraries to validate payments
|
||||
* End users validating incoming transactions to cold wallets
|
||||
|
||||
### Creating A View-Only Wallet
|
||||
|
||||
You can create a view-only wallet from any existing wallet.
|
||||
|
||||
Open an existing wallet or create a new one using `monero-wallet-cli`. In the wallet, type `address` and `viewkey` to display the wallet's address and secret viewkey. Type `exit` to close the wallet.
|
||||
|
||||
Next, create your view-only wallet by typing `monero-wallet-cli --generate-from-view-key wallet-name`. The last argument will be your new wallet's file name. You will be prompted for `Standard address` and `View key` by the wallet. Paste in your original wallet's address and secret view key. Next, enter and confirm a password for your new wallet and you're done.
|
||||
47
_i18n/es/resources/user-guides/vps_run_node.md
Normal file
47
_i18n/es/resources/user-guides/vps_run_node.md
Normal file
@ -0,0 +1,47 @@
|
||||
# monerod
|
||||
|
||||
`monerod` is the daemon software that ships with the Monero tree. It is a console program, and manages the blockchain. While a bitcoin wallet manages both an account and the blockchain, Monero separates these: `monerod` handles the blockchain, and `monero-wallet-cli` handles the account.
|
||||
|
||||
This guide assumes you have already set up your VPS account and are using SSH to tunnel into the server console.
|
||||
|
||||
## Linux, 64-bit (Ubuntu 16.04 LTS)
|
||||
|
||||
### Make sure that port 18080 is open
|
||||
`monerod` uses this port to communicate with other nodes on the Monero network.
|
||||
|
||||
Example if using `ufw`: `sudo ufw allow 18080`
|
||||
Example if using `iptables`: `sudo iptables -A INPUT -p tcp --dport 18080 -j ACCEPT`
|
||||
|
||||
### Download the current Monero Core binaries
|
||||
|
||||
wget https://downloads.getmonero.org/linux64
|
||||
|
||||
### Make a directory and extract the files.
|
||||
|
||||
mkdir monero
|
||||
tar -xjvf linux64 -C monero
|
||||
|
||||
### Launch the daemon
|
||||
|
||||
cd monero
|
||||
./monerod
|
||||
|
||||
### Options:
|
||||
|
||||
Show list of all options and settings:
|
||||
|
||||
./monerod --help
|
||||
|
||||
Launch the daemon as a background process:
|
||||
|
||||
./monerod --detach
|
||||
|
||||
Monitor the output of `monerod` if running as daemon:
|
||||
|
||||
tail -f ~/.bitmonero/bitmonero.log
|
||||
|
||||
Keep the VPS secure with autoupdate:
|
||||
|
||||
https://help.ubuntu.com/community/AutomaticSecurityUpdates
|
||||
|
||||
|
||||
29
_i18n/es/resources/user-guides/website-blog.md
Normal file
29
_i18n/es/resources/user-guides/website-blog.md
Normal file
@ -0,0 +1,29 @@
|
||||
### Quick Start
|
||||
* Make new .md file in _posts (named whatever, no spaces)
|
||||
* Front Matter (below)
|
||||
* Write Blog Post
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### Make a file
|
||||
Navigate to the _posts folder of the website and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### Front Matter
|
||||
```
|
||||
---
|
||||
layout: post
|
||||
title: CHANGE TO YOUR TITLE
|
||||
summary: A BRIEF ONE OR TWO SENTENCE SUMMARY
|
||||
tags: [CHOOSE, RELEVANT, TAGS, AND, SEPARATE, THEM, BY, COMMAS, KEEP, THE, BRACKETS]
|
||||
author: YOUR NAME OR HANDLE HERE
|
||||
---
|
||||
```
|
||||
|
||||
### Write
|
||||
After the front matter is finished you are free to write the remainder of your blog post in markdown.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test that your page appears in the 'News' section of the website, as well as the sidebars.
|
||||
|
||||
### Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
33
_i18n/es/resources/user-guides/website-events.md
Normal file
33
_i18n/es/resources/user-guides/website-events.md
Normal file
@ -0,0 +1,33 @@
|
||||
### 9.1 Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `events.yml`. You will notice a list separated by hyphenated `-event` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the area that you want to update and copy the code below:
|
||||
```
|
||||
- event:
|
||||
where:
|
||||
when:
|
||||
description:
|
||||
link:
|
||||
```
|
||||
and paste it IN THE CHRONOLOGICAL ORDER that it will be in. So if there is an event happening before yours, make sure it is higher up than yours. If there is an event happening AFTER yours, make sure it is after your event.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `event:` The name of the event goes here as well as the date. The recommended format is: `Event Name - January 1st, 2000`
|
||||
* `where:` Where the event will take place. Vanue name and address are recommended.
|
||||
* `when:` Date and time
|
||||
* `description:` Descriptoin of the happenings of your event
|
||||
* `link:` The website of your event (if applicable, this can be left blank and everything will be ok). This link must have http:// at the beginning if it is an external link.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### 9.2 Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `events.yml` file back in 9.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Events page `/community/events/` and check to see that the event is showing up in the correct place. Click their Event url link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### 9.3 Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
38
_i18n/es/resources/user-guides/website-faq.md
Normal file
38
_i18n/es/resources/user-guides/website-faq.md
Normal file
@ -0,0 +1,38 @@
|
||||
### Copy/Paste Code
|
||||
Navigate to the `/get-started/faq` folder and open the `index.md` file. Inside you will see HTML code, but you will see it is very repetetive.
|
||||
|
||||
Copy the code below:
|
||||
```
|
||||
<div class="tab">
|
||||
<input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
|
||||
<label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
|
||||
|
||||
<div class="tab-content" markdown="1">
|
||||
|
||||
CHANGE ANSWER
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
```
|
||||
And paste it at the very bottom of the file. Literally underneath everything else.
|
||||
|
||||
Now we're going to change just a couple of things. Find the section with:
|
||||
```
|
||||
<input id="tab-CHANGETHIS" type="checkbox" name="tabs" class="accordian">
|
||||
<label for="tab-CHANGETHIS" class="accordian">CHANGE QUESTION</label>
|
||||
```
|
||||
|
||||
and change the sections in between the quotes that say 'CHANGETHIS'. Leave the first part `tab-` alone. You can change it to anything really, as long as they are identical in the input and label, but it's good to see what number is on the last FAQ question (i.e. `tab-nine`) and make it the next number.
|
||||
|
||||
Now inside the label tag you're going to find where it says 'CHANGE QUESTION' and change it to the Question you want answered.
|
||||
|
||||
Lastly, find the words 'CHANGE ANSWER' and change it to the answer of your question.
|
||||
|
||||
**DO NOT MESS WITH THE INDENTATION HERE. The div that has `markdown=1` MUST be flush with the left side, the answer to the question must start flush with the left side, and the `</div>` MUST be flush with the left side. **
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build is successful, go to the FAQ page `/get-started/faq/` and check to see that your question is showing up and, when clicked, the answer drops down. If not, check to make sure that the `id="tab-CHANGETHIS"` in the input and the `for="CHANGETHIS"` in the label are identical to each other. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
67
_i18n/es/resources/user-guides/website-ffs.md
Normal file
67
_i18n/es/resources/user-guides/website-ffs.md
Normal file
@ -0,0 +1,67 @@
|
||||
### Quick Start
|
||||
|
||||
* Read [How the Forum Funding System works](#) and the [Forum Funding System Terms and Guidelines](#).
|
||||
* Make the .md file in the /forum-funding-system/proposals folder. Remember the name.
|
||||
* Choose your front matter layout based on whether your proposal is an Idea (`ffs-ideas`) or Open Task (`ffs-ot`) as specified in the above reading
|
||||
* Fill out the rest of the Front Matter below, leaving the `address` and `paymentid` sections empty
|
||||
* Edit the ffs.yml file. I strongly recommend you read this section.
|
||||
* Write the proposal
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### Make the proposal
|
||||
|
||||
Navigate to the /forum-funding-system/proposals folder and make a new file. Be sure the file name has no spaces and the ending is .md. It is very important that you remember the EXACT name of this file.
|
||||
|
||||
### Front Matter
|
||||
|
||||
```
|
||||
---
|
||||
layout: ffs-ideas OR ffs-ot
|
||||
title: NAME OF YOUR PROPOSAL
|
||||
summary: A BRIEF SUMMARY OF YOUR PROPOSAL
|
||||
author: YOUR NAME OR HANDLE
|
||||
address:
|
||||
paymentid:
|
||||
---
|
||||
```
|
||||
|
||||
The layout will depend on if you are simply presenting an idea that you do not plan to do yourself or if you are presenting an idea that you are capable and willing to do, the chosen layout will be `ffs-ideas` or `ffs-ot` respectively. You can get more information in the [How the Forum Funding System works](#) User Guide. Fill out the next three sections as normal (title, summary, author), but leave the last two (address, paymentid) blank. Again, DO NOT PUT ANYTHING HERE.
|
||||
|
||||
### Editing the .yml file
|
||||
|
||||
Navigate to the /_data folder and open the file titled `ffs.yml`. In this file you will find a long list of FFS proposals.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Identify the section you will be placing your proposal in. If you used `ffs-ideas` in the layout variable in the front matter then you will be putting your proposal in `stage: ideas`, and if you used `ffs-ot` in the layout, then you will be putting your proposal in the `stage: Open Tasks`. Copy the following code:
|
||||
|
||||
```
|
||||
- name:
|
||||
url: /forum-funding-system/proposals/
|
||||
summary:
|
||||
author:
|
||||
```
|
||||
|
||||
and paste it as the very top underneath the `proposals:`.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail. If in doubt, put the line with the hyphen (-name) all the way to the left and press space four time, and then put the remainder of the variables all the way to the left and press space six times.**
|
||||
|
||||
Fill in the information.
|
||||
* `name:` should be the same as the title chosen in 7.3
|
||||
* for `url:` you should append the EXACT name of the file as chosen in 7.2 to the current string but with `.html` at the end instead of `.md`. So it should look like `/forum-funding-system/proposals/YOUR-FILE-NAME.html`
|
||||
* `summary:` should be the same summary copy and pasted from the front matter in 7.3
|
||||
* `author:` should be your name or handle, again the same as the front matter in 7.3
|
||||
|
||||
Sorry for the repetition here, but it's how Jekyll is working to put things correctly.
|
||||
|
||||
### Write the proposal
|
||||
Go ahead and write your proposal now. Go back to your .md file in `/forum-funding-system/proposals`. Be sure to follow the [Forum Funding System Terms and Guidelines](#). Let me be the first to thank you for wanting to contribute your time and energy to better Monero.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `ffs.yml` file back in 7.4. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Forum Funding System section of the website and make sure that your proposal is showing up in the correct areas, and that when the linked is clicked it takes you to the correct page with your proposal. Use this time to read everything for accuracy and make any changes. If not, you will have to do multiple PRs to make edits and updates. It is this way by design so we can keep track of edits made by authors.
|
||||
|
||||
### Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
53
_i18n/es/resources/user-guides/website-general.md
Normal file
53
_i18n/es/resources/user-guides/website-general.md
Normal file
@ -0,0 +1,53 @@
|
||||
### Introduction
|
||||
|
||||
This README here to walk you through everything you need to know to make changes, edits, or even completely new pages for the new getmonero.org website. It'll definitely be a bit of a ride, so strap yourself in. Please note that translations are not available yet, but when they are added, this document will be updated with instructions on how to translate the content of getmonero.org. In the meantime, any help translating this document into another language is greatly appreciated.
|
||||
|
||||
Feel free to skip down to a relevant section if you already know what you need. So to go to the 'How to make a User Guide' section use your find function and type '5.0'.
|
||||
|
||||
If for any reason you have questions or need to contact us, you can find us on the IRC channel #monero. We'll do whatever we can to help you.
|
||||
|
||||
### What you'll need
|
||||
|
||||
* Jekyll: Getmonero.org is made using a simple, static website generator called [Jekyll](https://jekyllrb.com/). You will need it installed on your system to test any changes that you made. If you're using Windows, you will want to check out [this site](http://jekyll-windows.juthilo.com/) for instructions on how to get Jekyll working on your system. If you're using a Linux-based system you can just follow the instructions on the website to get up and going:
|
||||
* Install Ruby
|
||||
* Install Bundler: `gem install bundler`
|
||||
* Install Jekyll with all dependencies (run from the project directory): `bundle`
|
||||
|
||||
* GitHub: Pretty much everything in Monero is hosted on [GitHub](https://github.com) and uses Git as the primary version control system. If you're not familiar with how to use Git, you can check out [this tutorial](https://guides.github.com/activities/hello-world/) for a good overview. It will take you through pretty much everything you'll need to know to edit the website. If you haven't already, register for GitHub and fork the [Monero Website repository](https://github.com/monero-project/monero-site).
|
||||
|
||||
* Markdown experience: To write pages, you're going to need to know how to use Markdown. It's basically an in-between language that enables people who don't know HTML to just write, and it will be compiled into HTML for you. You can find a great Markdown cheat sheet with examples [here](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet). IF you need more help, Google and YouTube are great resources.
|
||||
|
||||
*Note: If you're confused, feel free to click other files in the same directory (folder) that you are in for the step that you are on to see some working examples. Compare them to the instructions and you should understand better.*
|
||||
|
||||
Once you have the above list of things, it's typically a good idea to build the website from your local computer to make sure it works before you make any changes. To do this, complete the following steps:
|
||||
|
||||
1. Navigate to your local `monero-site` repository.
|
||||
2. Serve the website: `jekyll serve`
|
||||
3. Open a browser and go to [http://127.0.0.1:4000](http://127.0.0.1:4000).
|
||||
4. If all went well, you should see the Monero website and you're ready to make changes.
|
||||
|
||||
### General change recommendations
|
||||
|
||||
The average Monero user that will want to contribute to the website should probably stick with making blog posts, user guides, Moneropedia entries, or a Forum Funding System proposal, all of which are covered in this document. If this is all you want to do, don't worry, it's actually not a daunting task at all. If you are not well versed in web development however, it is not recommended you try to do anything beyond that.
|
||||
|
||||
If you are a web developer and would like to make large macro-level changes, it would be best to get in contact with rehrar. The HTML/CSS framework is custom, though quite easy to use for a seasoned developer. Still, there are some pages that are more complicated than others and would require fair amounts of styling changes should the structure change significantly.
|
||||
|
||||
This website is completely open-source however and anything and everything is available for changing should the community deem it necessary.
|
||||
|
||||
Every section from here on out will talk about how to make a specific type of web page. It will start with a bullet point list of what to do for the advanced among you that just want a quick overview. For those who are still learning this list is followed by a detailed explanation, starting with example front matter. Any variable in the front matter written in all caps you are expected to change (make sure your changes are not all caps though). It will then lead you through the rest of the process until it's time to type your content.
|
||||
|
||||
A few random points of note:
|
||||
|
||||
- All external links must have http:// or https:// in front of them or they will not redirect properly.
|
||||
- If you want to add a new page to the navigation, you should note that there are two menus in `header.html`. One for mobile and one for desktop. Your page must be added in the appropriate place in BOTH navigations.
|
||||
- It is strongly strongly STRONGLY encouraged that you if you make a change, you - at the minimum - test it on your local machine before submitting a PR. Sometimes unexpected things may happen due to a change. If you change a page, check the whole page on multiple screen sizes and browsers to make sure there wasn't any collateral damage.
|
||||
|
||||
### Housekeeping
|
||||
|
||||
#### GitHub Issues
|
||||
We ask that if you open an issue on the site that you remain available for clarifying questions or corrections. We do our best to close issues that are resolved when we make changes to the site, but If your issue is resolved by a contributer and the issue is not closed we ask that you close it in a timely manner. A contributer (rehrar, SamsungGalaxyPlayer, or other community members, etc) may ask you to close an issue after it's confirmed fixed. Please review the changes to the site and close your issue if you can verify that it's fixed.
|
||||
|
||||
#### Pull Requests
|
||||
Contributers should use [issue keywords](https://help.github.com/articles/closing-issues-using-keywords/) to make it easier for maintainers to close issues when they merge. Include close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved, etc in the commit message or pull request description, so that the correct issue can be closed if your PR is merged. (Example: 'fixes #1234' could close Issue 1234 when merged.)
|
||||
|
||||
Pull requests allow others to make comments or review your changes to the site. We ask that you remain available to comment or make changes to your PR. Pull requests with pending changes for more than 30 days will be closed and need to be resubmitted in the future. Sometimes someone else's changes might make your changes conflict with the current site. If that happens you may need to rebase your PR. (If you're unsure about how to do so, you can reach out to other contributers on IRC (freenode #monero) and someone should be able to walk you through it.
|
||||
27
_i18n/es/resources/user-guides/website-merchants.md
Normal file
27
_i18n/es/resources/user-guides/website-merchants.md
Normal file
@ -0,0 +1,27 @@
|
||||
### Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `merchants.yml`. You will notice a list separated by hyphenated `-category` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the category that best describes your business/service and copy the code below:
|
||||
```
|
||||
- name:
|
||||
url:
|
||||
```
|
||||
and paste it in the correct category under the `merchants:` section.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `name:` The name of the the business/service.
|
||||
* `url:` The external url of the business/service. This link must have http:// (or https://) at the beginning if it is an external link.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `merchants.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Merchants page `/community/merchants/` and check to see that the business is showing up in the correct category and that the link is redirecting correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
23
_i18n/es/resources/user-guides/website-moneropedia.md
Normal file
23
_i18n/es/resources/user-guides/website-moneropedia.md
Normal file
@ -0,0 +1,23 @@
|
||||
### Make a file
|
||||
Navigate to the /resources/moneropedia folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### Front Matter
|
||||
```
|
||||
---
|
||||
layout: moneropedia
|
||||
entry: "PUT THE NAME OF THE TERM HERE IN QUOTE, THIS IS HOW IT WILL SHOW UP ON THE LANDING PAGE"
|
||||
terms: ["PUT", "TERMS", "HERE", "EXPLAINED", "BELOW"]
|
||||
summary: "PUT SUMMARY OF YOUR ENTRY HERE IN QUOTES"
|
||||
---
|
||||
```
|
||||
|
||||
There is one thing to highlight. The `terms:` section of the front matter can be filled with as many terms as you would like. This is how other Moneropedia entries will link to this page. You can link to other Moneropedia entries as well in your page by putting an ampersand before the term used, i.e. `@THE-TERM-USED`. This will make an automatic link in the Moneropedia entry to the referred term, replace the @term with the word used in that terms `entry:` area of the front matter, and on hover it will show the summary. How cool is that?
|
||||
|
||||
### Write
|
||||
Write your Moneropedia entry. Remember that you can link to other Moneropedia entries using `@term-used-in-entry` as described above. Just go to the .md file of the Moneropedia entry you want to link to and use any of the terms in the `terms:` field of the front matter. Be sure to write whichever one you choose EXACTLY as shown and preceded by an ampersand.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test check the link to your entry is appearing on the alphabetical list of Moneropedia entries and that it leads to your entry when clicked. Test your Moneropedia entry in the browser and contact rehrar if there are any bugs.
|
||||
|
||||
### Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
29
_i18n/es/resources/user-guides/website-roadmap.md
Normal file
29
_i18n/es/resources/user-guides/website-roadmap.md
Normal file
@ -0,0 +1,29 @@
|
||||
### Edit the .yml file
|
||||
Navigate to the `/_data/` folder and open `roadmap.yml`. You will notice a list separated by hyphenated `-year` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the year that you want to update and copy the code below:
|
||||
```
|
||||
- name:
|
||||
date:
|
||||
status:
|
||||
```
|
||||
and paste it in the correct years `accomplishments:` section IN THE CHRONOLOGICAL ORDER that it will be in. So if there is a accomplishment that happened/is happening before the one you are inputting, make sure it is higher up than yours. If there is an accomplishment that happened/is happening AFTER yours, make sure it is after yours. If you don't have exact dates, just do your best to estimate.
|
||||
|
||||
Fill in the data as follows:
|
||||
* `name:` The name of the accomplishment. Try to keep it short, a sentence or two at most.
|
||||
* `date:` When the accomplishment happened (past) or when it is expected to happen (future)
|
||||
* `status:` If the task is done, put `completed`, if the task is currently in the works put `ongoing`, and if work on the task has not yet started to your knowledge, but is expected to, put `upcoming`.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `roadmap.yml` file back in 10.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Events page `/resources/roadmap/` and check to see that the newly added accomplishment is showing up in the correct place in the correct year. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
25
_i18n/es/resources/user-guides/website-team.md
Normal file
25
_i18n/es/resources/user-guides/website-team.md
Normal file
@ -0,0 +1,25 @@
|
||||
If you are acting on behalf of another individual, please make sure you get their permission first before adding them onto the Team page.
|
||||
|
||||
### Change the .yml file
|
||||
Navigate to the `/_data/` folder and open `team.yml`. You will notice a long list separated by main `-area:` tags.
|
||||
|
||||
**DO NOT MESS WITH THE FORMATTING OR INDENTATION OF ANYTHING OR JEKYLL WILL NOT BUILD PROPERLY!**
|
||||
|
||||
Find the area that you want to update and copy the code below:
|
||||
```
|
||||
- name:
|
||||
url:
|
||||
```
|
||||
Put the name or handle of the person in the `name` section and in the `url:` section put the link to their GitHub URL (it must have https:// at the beginning). If they have no GitHub, then you may leave it blank, it won't mess anything up.
|
||||
|
||||
**Make sure the indentation is EXACTLY the same as the other proposals in the area. If it's not the jekyll build WILL fail.**
|
||||
|
||||
Save the file.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically. If the build fails and you receive an error, you may have messed up somewhere in the `team.yml` file back in 8.1. Go back to that section and check the indentation. Yes, it's stupid. Yes, it has to be perfect.
|
||||
|
||||
If the build is successful, go to the Team page `/community/team/` and check to see that the contributor is showing up in the correct place. Click their GitHub link (if applicable) and make sure it redirects correctly. Test the page and let rehrar know if there are any bugs.
|
||||
|
||||
### Submit a Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
39
_i18n/es/resources/user-guides/website-user-guide.md
Normal file
39
_i18n/es/resources/user-guides/website-user-guide.md
Normal file
@ -0,0 +1,39 @@
|
||||
### Quick Start
|
||||
|
||||
* Make file in /resources/user-guides with a .md ending and no spaces in filename.
|
||||
* Front Matter as in 5.3
|
||||
* Write User Guide
|
||||
* Add guide using markdown in the correct category in /resources/user-guides/index.md being careful not to mess with any indentation
|
||||
* Test/Build
|
||||
* Submit PR
|
||||
|
||||
### Make a file
|
||||
Navigate to the /resources/user-guides folder and make a new file. Be sure the file name has no spaces and the ending is .md
|
||||
|
||||
### Front Matter
|
||||
```
|
||||
---
|
||||
layout: static_page
|
||||
title: TITLE OF YOUR USER GUIDE
|
||||
---
|
||||
```
|
||||
|
||||
### Write
|
||||
Write your user guide. Be succinct but thorough. Remember, people will be using your guides when they need help. Make sure all the information is there. Feel free to use images or screenshots if necessary to help get your point across.
|
||||
|
||||
### Add Guide to the 'User Guide' landing page
|
||||
In the /resources/user-guides folder, find the file labeled index.md and open it.
|
||||
|
||||
DO NOT CHANGE ANYTHING IN THIS DOCUMENT BESIDES WHAT YOU ARE INSTRUCTED TO.
|
||||
|
||||
This file will look quite different because it's HTML. Don't panic. Simply Ctrl + F (i.e. the find feature) and search for the category that you want to put your User Guide in. You will see there are some sections that are not indented like the others. They are flush with the left side of the screen. **Do not change the indentation.** You can put markdown in these areas.
|
||||
|
||||
Once you've identified the non-indented area under the category you would like your User Guide to be under, you can use markdown to insert your link underneath the others. `[TITLE OF USER GUIDE](LINK-TO-USER-GUIDE.html)`. Please note that the file name in between the paranthases must be EXACTLY the same name as the file name you made in step 5.2, but with a `.html` at the end instead of `.md`.
|
||||
|
||||
In the event that you think your User Guide should be in a new Category that doesn't exist yet, contact rehrar to make one for you.
|
||||
|
||||
### Build/Test
|
||||
Build your website using `jekyll serve` if it's not rebuilding automatically and test that your link appears in the correct category and that it leads to your User Guide when clicked. Test your User Guide in the browser and contact rehrar if there are any bugs.
|
||||
|
||||
### Submit Pull Request
|
||||
You're all done. Submit a PR and wait for it to be reviewed and merged. Be sure to make any changes if requested.
|
||||
Loading…
Reference in New Issue
Block a user