Skip to content

Commit cd8d2fd

Browse files
authored
Merge pull request #1583 from liamcottle/docs/migrate
Refactor Documentation
2 parents 384e482 + 4af31e5 commit cd8d2fd

8 files changed

Lines changed: 315 additions & 430 deletions

File tree

docs/_stylesheets/extra.css

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,8 @@
99
.md-source__fact--version {
1010
display: none;
1111
}
12+
13+
/* underline links */
14+
.md-typeset a {
15+
text-decoration: underline;
16+
}

docs/cli_commands.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
1-
# MeshCore Repeater & Room Server CLI Commands
1+
# CLI Commands
2+
3+
This document provides an overview of CLI commands that can be sent to MeshCore Repeaters, Room Servers and Sensors.
24

35
## Navigation
46

Lines changed: 144 additions & 406 deletions
Large diffs are not rendered by default.

docs/docs.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Local Documentation
2+
3+
This document explains how to build and view the MeshCore documentation locally.
4+
5+
## Building and viewing Docs
6+
7+
```
8+
pip install mkdocs
9+
pip install mkdocs-material
10+
```
11+
12+
- `mkdocs serve` - Start the live-reloading docs server.
13+
- `mkdocs build` - Build the documentation site.

docs/faq.md

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,6 @@
1-
**MeshCore-FAQ**<!-- omit from toc -->
2-
A list of frequently-asked questions and answers for MeshCore
3-
4-
The current version of this MeshCore FAQ is at https://github.com/meshcore-dev/MeshCore/blob/main/docs/faq.md.
5-
This MeshCore FAQ is also mirrored at https://github.com/LitBomb/MeshCore-FAQ and might have newer updates if pull requests on Scott's MeshCore repo are not approved yet.
1+
# Frequently Asked Questions
62

7-
author: https://github.com/LitBomb<!-- omit from toc -->
8-
---
3+
A list of frequently-asked questions and answers for MeshCore
94

105
- [1. Introduction](#1-introduction)
116
- [1.1. Q: What is MeshCore?](#11-q-what-is-meshcore)
@@ -112,15 +107,15 @@ Anyone is able to build anything they like on top of MeshCore without paying any
112107

113108
### 1.2. Q: What do you need to start using MeshCore?
114109
**A:** Everything you need for MeshCore is available at:
115-
Main web site: [https://meshcore.co.uk/](https://meshcore.co.uk/)
116-
Firmware Flasher: https://flasher.meshcore.co.uk/
117-
Phone Client Applications: https://meshcore.co.uk/apps.html
118-
MeshCore Firmware GitHub: https://github.com/ripplebiz/MeshCore
119-
120-
NOTE: Andy Kirby has a very useful [intro video](https://www.youtube.com/watch?v=t1qne8uJBAc) for beginners.
121110

111+
- Main web site: [https://meshcore.co.uk](https://meshcore.co.uk)
112+
- Firmware Flasher: [https://flasher.meshcore.co.uk](https://flasher.meshcore.co.uk)
113+
- MeshCore Firmware on GitHub: [https://github.com/meshcore-dev/MeshCore](https://github.com/meshcore-dev/MeshCore)
114+
- MeshCore Companion App: [https://meshcore.nz](https://meshcore.nz)
115+
- MeshCore Map: [https://meshcore.co.uk/map.html](https://meshcore.co.uk/map.html)
116+
- Andy Kirby has a very useful [intro video](https://www.youtube.com/watch?v=t1qne8uJBAc) for beginners.
122117

123-
You need LoRa hardware devices to run MeshCore firmware as clients or server (repeater and room server).
118+
You need LoRa hardware devices to run MeshCore firmware as clients or server (repeater and room server).
124119

125120
#### 1.2.1. Hardware
126121
MeshCore is available on a variety of 433MHz, 868MHz and 915MHz LoRa devices. For example, Lilygo T-Deck, T-Pager, RAK Wireless WisBlock RAK4631 devices (e.g. 19003, 19007, 19026), Heltec V3, Xiao S3 WIO, Xiao C3, Heltec T114, Station G2, Nano G2 Ultra, Seeed Studio T1000-E. More devices are being added regularly.
@@ -535,7 +530,7 @@ MeshCore clients would need to reset path constantly and flood traffic across th
535530
This could change in the future if MeshCore develops a client firmware that repeats.
536531
[Source](https://discord.com/channels/826570251612323860/1330643963501351004/1354780032140054659)
537532

538-
### 5.12. Q: How do I add a node to the [MeshCore Map]([url](https://meshcore.co.uk/map.html))
533+
### 5.12. Q: How do I add a node to the [MeshCore Map](https://meshcore.co.uk/map.html)
539534
**A:**
540535

541536
To add a BLE Companion radio, connect to the BLE Companion radio from the MeshCore smartphone app. In the app, tap the `3 dot` menu icon at the top right corner, then tap `Internet Map`. Tap the `3 dot` menu icon again and choose `Add me to the Map`

docs/index.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
1-
# Welcome
1+
# Introduction
22

33
Welcome to the MeshCore documentation.
44

5-
## Building and viewing Docs
5+
Below are a few quick start guides.
66

7-
```
8-
pip install mkdocs
9-
pip install mkdocs-material
10-
```
7+
- [Frequently Asked Questions](./faq.md)
8+
- [CLI Commands](./cli_commands.md)
9+
- [Companion Protocol](./companion_protocol.md)
10+
- [Packet Structure](./packet_structure.md)
11+
- [QR Codes](./qr_codes.md)
1112

12-
* `mkdocs serve` - Start the live-reloading docs server.
13-
* `mkdocs build` - Build the documentation site.
13+
If you find a mistake in any of our documentation, or find something is missing, please feel free to open a pull request for us to review.
14+
15+
- [Documentation Source](https://github.com/meshcore-dev/MeshCore/tree/main/docs)

docs/qr_codes.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# QR Codes
2+
3+
This document provides an overview of QR Code formats that can be used for sharing MeshCore channels and contacts. The formats described below are supported by the MeshCore mobile app.
4+
5+
## Add Channel
6+
7+
**Example URL**:
8+
9+
```
10+
meshcore://channel/add?name=Public&secret=8b3387e9c5cdea6ac9e5edbaa115cd72
11+
```
12+
13+
**Parameters**:
14+
15+
- `name`: Channel name (URL-encoded if needed)
16+
- `secret`: 16-byte secret represented as 32 hex characters
17+
18+
## Add Contact
19+
20+
**Example URL**:
21+
22+
```
23+
meshcore://contact/add?name=Example+Contact&public_key=9cd8fcf22a47333b591d96a2b848b73f457b1bb1a3ea2453a885f9e5787765b1&type=1
24+
```
25+
26+
**Parameters**:
27+
28+
- `name`: Contact name (URL-encoded if needed)
29+
- `public_key`: 32-byte public key represented as 64 hex characters
30+
- `type`: numeric contact type
31+
- `1`: Companion
32+
- `2`: Repeater
33+
- `3`: Room Server
34+
- `4`: Sensor

docs/terminal_chat_cli.md

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
# Terminal Chat CLI
2+
3+
Below are the commands you can enter into the Terminal Chat clients:
4+
5+
```
6+
set freq {frequency}
7+
```
8+
Set the LoRa frequency. Example: set freq 915.8
9+
10+
```
11+
set tx {tx-power-dbm}
12+
```
13+
Sets LoRa transmit power in dBm.
14+
15+
```
16+
set name {name}
17+
```
18+
Sets your advertisement name.
19+
20+
```
21+
set lat {latitude}
22+
```
23+
Sets your advertisement map latitude. (decimal degrees)
24+
25+
```
26+
set lon {longitude}
27+
```
28+
Sets your advertisement map longitude. (decimal degrees)
29+
30+
```
31+
set af {air-time-factor}
32+
```
33+
Sets the transmit air-time-factor.
34+
35+
36+
```
37+
time {epoch-secs}
38+
```
39+
Set the device clock using UNIX epoch seconds. Example: time 1738242833
40+
41+
42+
```
43+
advert
44+
```
45+
Sends an advertisement packet
46+
47+
```
48+
clock
49+
```
50+
Displays current time per device's clock.
51+
52+
53+
```
54+
ver
55+
```
56+
Shows the device version and firmware build date.
57+
58+
```
59+
card
60+
```
61+
Displays *your* 'business card', for other to manually _import_
62+
63+
```
64+
import {card}
65+
```
66+
Imports the given card to your contacts.
67+
68+
```
69+
list {n}
70+
```
71+
List all contacts by most recent. (optional {n}, is the last n by advertisement date)
72+
73+
```
74+
to
75+
```
76+
Shows the name of current recipient contact. (for subsequent 'send' commands)
77+
78+
```
79+
to {name-prefix}
80+
```
81+
Sets the recipient to the _first_ matching contact (in 'list') by the name prefix. (ie. you don't have to type whole name)
82+
83+
```
84+
send {text}
85+
```
86+
Sends the text message (as DM) to current recipient.
87+
88+
```
89+
reset path
90+
```
91+
Resets the path to current recipient, for new path discovery.
92+
93+
```
94+
public {text}
95+
```
96+
Sends the text message to the built-in 'public' group channel

0 commit comments

Comments
 (0)