Bob Mottram 7 年 前
コミット
59ef8ff65d
共有3 個のファイルを変更した127 個の追加76 個の削除を含む
  1. 1
    1
      doc/EN/mesh.org
  2. 16
    16
      website/EN/app_vpn.html
  3. 110
    59
      website/EN/mesh.html

+ 1
- 1
doc/EN/mesh.org ファイルの表示

@@ -268,7 +268,7 @@ To allow mobile devices to connect to the mesh you will need a second wifi adapt
268 268
 
269 269
 On a typical Android device go to *Settings* then *Security* and ensure that *Unknown sources* is enabled. Also within *Wifi* from the *Settings* screen select the mesh hotspot. The password is "/freedombone/". Open a non-Tor browser and navigate to the IP address showing in the hotspot name. You can then download and install mesh apps.
270 270
 
271
-#+ATTR_HTML: width="200px"
271
+#+ATTR_HTML: :width 300
272 272
 #+BEGIN_CENTER
273 273
 [[file:images/mesh_mobileapps.jpg]]
274 274
 #+END_CENTER

+ 16
- 16
website/EN/app_vpn.html ファイルの表示

@@ -3,7 +3,7 @@
3 3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5
 <head>
6
-<!-- 2017-09-27 Wed 17:58 -->
6
+<!-- 2017-10-05 Thu 14:51 -->
7 7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9 9
 <title>&lrm;</title>
@@ -266,9 +266,9 @@ Using a Tor browser is another way to get around censorship, but there might be
266 266
 On Freedombone the VPN is wrapped within a TLS layer of encryption, making it difficult for any deep packet inspection systems to know whether you are using a VPN or not. Since there is lots of TLS traffic on the internet your connection looks like any other TLS connection to a server, and this may help to avoid being censored. It's probably not possible for your local ISP to block TLS traffic without immediately generating a lot of irate customers, and stopping any kind of commercial activity.
267 267
 </p>
268 268
 
269
-<div id="outline-container-org778c839" class="outline-2">
270
-<h2 id="org778c839">Installation</h2>
271
-<div class="outline-text-2" id="text-org778c839">
269
+<div id="outline-container-orgb96ecdd" class="outline-2">
270
+<h2 id="orgb96ecdd">Installation</h2>
271
+<div class="outline-text-2" id="text-orgb96ecdd">
272 272
 <p>
273 273
 ssh into the system with:
274 274
 </p>
@@ -288,9 +288,9 @@ Only use ports 443 or 80 for VPN as an <i>absolute last resort</i>, since doing
288 288
 </div>
289 289
 </div>
290 290
 
291
-<div id="outline-container-org2cfcc49" class="outline-2">
292
-<h2 id="org2cfcc49">Usage</h2>
293
-<div class="outline-text-2" id="text-org2cfcc49">
291
+<div id="outline-container-orgc55576d" class="outline-2">
292
+<h2 id="orgc55576d">Usage</h2>
293
+<div class="outline-text-2" id="text-orgc55576d">
294 294
 <p>
295 295
 When the installation is complete you can download your VPN keys and configuration files onto your local machine.
296 296
 </p>
@@ -306,7 +306,7 @@ You will need to ensure that the <i>openvpn</i> and <i>stunnel</i> packages are
306 306
 </p>
307 307
 
308 308
 <div class="org-src-container">
309
-<pre class="src src-bash">sudp pacman -S openvpn stunnel4
309
+<pre class="src src-bash">sudo pacman -S openvpn stunnel4
310 310
 </pre>
311 311
 </div>
312 312
 
@@ -335,9 +335,9 @@ You should see a series of messages with "<i>Initialization Sequence Completed</
335 335
 </div>
336 336
 </div>
337 337
 
338
-<div id="outline-container-orgc7282cd" class="outline-2">
339
-<h2 id="orgc7282cd">Changing port number</h2>
340
-<div class="outline-text-2" id="text-orgc7282cd">
338
+<div id="outline-container-org8a983c5" class="outline-2">
339
+<h2 id="org8a983c5">Changing port number</h2>
340
+<div class="outline-text-2" id="text-org8a983c5">
341 341
 <p>
342 342
 Avoiding censorship can be a cat and mouse game, and so if the port you're using for VPN gets blocked then you may want to change it.
343 343
 </p>
@@ -348,16 +348,16 @@ Avoiding censorship can be a cat and mouse game, and so if the port you're using
348 348
 </div>
349 349
 
350 350
 <p>
351
-Select <b>Administrator controls</b> then <b>App Settings</b> then <b>vpn</b>. Choose <b>Change TLS port</b> and enter a new port value. You can then either manually change the port within your VPN configuration files, or download them again as described in the <a href="#org2cfcc49">Usage</a> section above.
351
+Select <b>Administrator controls</b> then <b>App Settings</b> then <b>vpn</b>. Choose <b>Change TLS port</b> and enter a new port value. You can then either manually change the port within your VPN configuration files, or download them again as described in the <a href="#orgc55576d">Usage</a> section above.
352 352
 </p>
353 353
 </div>
354 354
 </div>
355 355
 
356
-<div id="outline-container-orgbe4ddea" class="outline-2">
357
-<h2 id="orgbe4ddea">Generating new keys</h2>
358
-<div class="outline-text-2" id="text-orgbe4ddea">
356
+<div id="outline-container-orgc802140" class="outline-2">
357
+<h2 id="orgc802140">Generating new keys</h2>
358
+<div class="outline-text-2" id="text-orgc802140">
359 359
 <p>
360
-It's possible that your VPN keys might get lost or compromised on your local machine. If that happens you can generate new ones from the <b>Administrator controls</b> by going to <b>App Settings</b> then <b>vpn</b> then choosing <b>Regenerate keys for a user</b> and downloading the new keys as described in the <a href="#org2cfcc49">Usage</a> section above.
360
+It's possible that your VPN keys might get lost or compromised on your local machine. If that happens you can generate new ones from the <b>Administrator controls</b> by going to <b>App Settings</b> then <b>vpn</b> then choosing <b>Regenerate keys for a user</b> and downloading the new keys as described in the <a href="#orgc55576d">Usage</a> section above.
361 361
 </p>
362 362
 </div>
363 363
 </div>

+ 110
- 59
website/EN/mesh.html ファイルの表示

@@ -3,7 +3,7 @@
3 3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5
 <head>
6
-<!-- 2017-10-05 Thu 13:13 -->
6
+<!-- 2017-10-05 Thu 15:09 -->
7 7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9 9
 <title>&lrm;</title>
@@ -274,13 +274,13 @@ for the JavaScript code in this tag.
274 274
 </colgroup>
275 275
 <tbody>
276 276
 <tr>
277
-<td class="org-left"><a href="#orge7e03ce">What the system can do</a></td>
277
+<td class="org-left"><a href="#org5eda560">What the system can do</a></td>
278 278
 <td class="org-left">-</td>
279
-<td class="org-left"><a href="#orgc3dbd7e">Disk Images</a></td>
279
+<td class="org-left"><a href="#org63f9e7b">Disk Images</a></td>
280 280
 <td class="org-left">-</td>
281
-<td class="org-left"><a href="#orgf01fd55">Building Disk Images</a></td>
281
+<td class="org-left"><a href="#orgd4b86f7">Building Disk Images</a></td>
282 282
 <td class="org-left">-</td>
283
-<td class="org-left"><a href="#org1e57e4d">How to use it</a></td>
283
+<td class="org-left"><a href="#orge37188c">How to use it</a></td>
284 284
 </tr>
285 285
 </tbody>
286 286
 </table>
@@ -324,9 +324,9 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
324 324
 <li><b>Evolvable</b>: The network should be built with future development in mind. The platform should be flexible enough to support technologies, protocols and modes of usage that have not yet been developed.</li>
325 325
 </ul>
326 326
 
327
-<div id="outline-container-orge7e03ce" class="outline-2">
328
-<h2 id="orge7e03ce">What the system can do</h2>
329
-<div class="outline-text-2" id="text-orge7e03ce">
327
+<div id="outline-container-org5eda560" class="outline-2">
328
+<h2 id="org5eda560">What the system can do</h2>
329
+<div class="outline-text-2" id="text-org5eda560">
330 330
 <ul class="org-ul">
331 331
 <li>Discovery of other users on the network</li>
332 332
 <li>Text based chat, one-to-one and in groups</li>
@@ -350,13 +350,13 @@ This system should be quite scalable. Both qTox and IPFS are based upon distribu
350 350
 </div>
351 351
 </div>
352 352
 
353
-<div id="outline-container-orgc3dbd7e" class="outline-2">
354
-<h2 id="orgc3dbd7e">Disk Images</h2>
355
-<div class="outline-text-2" id="text-orgc3dbd7e">
353
+<div id="outline-container-org63f9e7b" class="outline-2">
354
+<h2 id="org63f9e7b">Disk Images</h2>
355
+<div class="outline-text-2" id="text-org63f9e7b">
356 356
 </div>
357
-<div id="outline-container-org48cf6b4" class="outline-3">
358
-<h3 id="org48cf6b4">Writing many images quickly</h3>
359
-<div class="outline-text-3" id="text-org48cf6b4">
357
+<div id="outline-container-org9b83703" class="outline-3">
358
+<h3 id="org9b83703">Writing many images quickly</h3>
359
+<div class="outline-text-3" id="text-org9b83703">
360 360
 <p>
361 361
 There may be situations where you need to write the same disk image to multiple drives at the same time in order to maximize rate of deployment. In the instructions given below the <b>dd</b> command is used for writing to the target drive, but to write to multiple drives you can use a tool such as <a href="https://wiki.gnome.org/Apps/MultiWriter">GNOME MultiWriter</a>.
362 362
 </p>
@@ -384,9 +384,9 @@ The MultiWriter tool is also available within mesh client images, so that you ca
384 384
 </p>
385 385
 </div>
386 386
 </div>
387
-<div id="outline-container-orga4d8a06" class="outline-3">
388
-<h3 id="orga4d8a06">Client images</h3>
389
-<div class="outline-text-3" id="text-orga4d8a06">
387
+<div id="outline-container-orgf6cd1c6" class="outline-3">
388
+<h3 id="orgf6cd1c6">Client images</h3>
389
+<div class="outline-text-3" id="text-orgf6cd1c6">
390 390
 <div class="org-center">
391 391
 
392 392
 <div class="figure">
@@ -435,16 +435,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
435 435
 </div>
436 436
 </div>
437 437
 
438
-<div id="outline-container-org990631a" class="outline-3">
439
-<h3 id="org990631a">Router images</h3>
440
-<div class="outline-text-3" id="text-org990631a">
438
+<div id="outline-container-org7170054" class="outline-3">
439
+<h3 id="org7170054">Router images</h3>
440
+<div class="outline-text-3" id="text-org7170054">
441 441
 <p>
442 442
 Routers are intended to build network coverage for an area using small and low cost hardware. You can bolt them to walls or leave them on window ledges. They don't have any user interface and their only job is to haul network traffic across the mesh and to enable peers to find each other via running bootstrap nodes for Tox and IPFS. Copy the image to a microSD card and insert it into the router, plug in an Atheros wifi dongle and power on. That should be all you need to do.
443 443
 </p>
444 444
 </div>
445
-<div id="outline-container-orgf4481d1" class="outline-4">
446
-<h4 id="orgf4481d1">Beaglebone Black</h4>
447
-<div class="outline-text-4" id="text-orgf4481d1">
445
+<div id="outline-container-orgd098fe1" class="outline-4">
446
+<h4 id="orgd098fe1">Beaglebone Black</h4>
447
+<div class="outline-text-4" id="text-orgd098fe1">
448 448
 <div class="org-center">
449 449
 
450 450
 <div class="figure">
@@ -481,9 +481,9 @@ There is still a software freedom issue with the Beaglebone Black, but it doesn'
481 481
 </div>
482 482
 </div>
483 483
 
484
-<div id="outline-container-orgf01fd55" class="outline-2">
485
-<h2 id="orgf01fd55">Building Disk Images</h2>
486
-<div class="outline-text-2" id="text-orgf01fd55">
484
+<div id="outline-container-orgd4b86f7" class="outline-2">
485
+<h2 id="orgd4b86f7">Building Disk Images</h2>
486
+<div class="outline-text-2" id="text-orgd4b86f7">
487 487
 <p>
488 488
 It's better not to trust images downloaded from random places on the interwebs. Chances are that unless you are in the web of trust of the above GPG signatures then they don't mean very much to you. If you actually want something trustworthy then build the images from scratch. It will take some time. Here's how to do it.
489 489
 </p>
@@ -571,9 +571,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
571 571
 </div>
572 572
 </div>
573 573
 
574
-<div id="outline-container-org410f58b" class="outline-2">
575
-<h2 id="org410f58b">Customisation</h2>
576
-<div class="outline-text-2" id="text-org410f58b">
574
+<div id="outline-container-org3b00cc8" class="outline-2">
575
+<h2 id="org3b00cc8">Customisation</h2>
576
+<div class="outline-text-2" id="text-org3b00cc8">
577 577
 <p>
578 578
 If you want to make your own specially branded version, such as for a particular event, then to change the default desktop backgrounds edit the images within <b>img/backgrounds</b> and to change the available avatars and desktop icons edit the images within <b>img/avatars</b>. Re-create disk images using the instructions shown previously.
579 579
 </p>
@@ -583,9 +583,9 @@ If you need particular <i>dconf</i> commands to alter desktop appearance or beha
583 583
 </p>
584 584
 </div>
585 585
 </div>
586
-<div id="outline-container-org1e57e4d" class="outline-2">
587
-<h2 id="org1e57e4d">How to use it</h2>
588
-<div class="outline-text-2" id="text-org1e57e4d">
586
+<div id="outline-container-orge37188c" class="outline-2">
587
+<h2 id="orge37188c">How to use it</h2>
588
+<div class="outline-text-2" id="text-orge37188c">
589 589
 <p>
590 590
 When you first boot from the USB drive the system will create some encryption keys, assign a unique network address to the system and then reboot itself. When that's done you should see a prompt asking for a username. This username just makes it easy for others to initially find you on the mesh and will appear in the list of users.
591 591
 </p>
@@ -595,9 +595,9 @@ After a minute or two if you are within wifi range and there is at least one oth
595 595
 </p>
596 596
 </div>
597 597
 
598
-<div id="outline-container-org11d6908" class="outline-3">
599
-<h3 id="org11d6908">Boot trouble</h3>
600
-<div class="outline-text-3" id="text-org11d6908">
598
+<div id="outline-container-org2a93988" class="outline-3">
599
+<h3 id="org2a93988">Boot trouble</h3>
600
+<div class="outline-text-3" id="text-org2a93988">
601 601
 <p>
602 602
 If the system doesn't boot and reports an error which includes <b>/dev/mapper/loop0p1</b> then reboot with <b>Ctrl-Alt-Del</b> and when you see the grub menu press <b>e</b> and manually change <b>/dev/mapper/loop0p1</b> to <b>/dev/sdb1</b>, then press <b>Ctrl-x</b>. If that doesn't work then reboot and try <b>/dev/sdc1</b> instead.
603 603
 </p>
@@ -607,9 +607,9 @@ After the system has booted successfully the problem should resolve itself on su
607 607
 </p>
608 608
 </div>
609 609
 </div>
610
-<div id="outline-container-org17e82b1" class="outline-3">
611
-<h3 id="org17e82b1">Set the Date</h3>
612
-<div class="outline-text-3" id="text-org17e82b1">
610
+<div id="outline-container-org3abb4d9" class="outline-3">
611
+<h3 id="org3abb4d9">Set the Date</h3>
612
+<div class="outline-text-3" id="text-org3abb4d9">
613 613
 <p>
614 614
 On the ordinary internet the date and time of your system would be set automatically via NTP. But this is not the internet and so you will need to manually ensure that your date and time settings are correct. You might need to periodically do this if your clock drifts. It's not essential that the time on your system be highly accurate, but if it drifts too far or goes back to epoch then things could become a little confusing in regard to the order of blog posts.
615 615
 </p>
@@ -619,9 +619,9 @@ On the ordinary internet the date and time of your system would be set automatic
619 619
 </p>
620 620
 </div>
621 621
 </div>
622
-<div id="outline-container-org55b78da" class="outline-3">
623
-<h3 id="org55b78da">Check network status</h3>
624
-<div class="outline-text-3" id="text-org55b78da">
622
+<div id="outline-container-org2b820e7" class="outline-3">
623
+<h3 id="org2b820e7">Check network status</h3>
624
+<div class="outline-text-3" id="text-org2b820e7">
625 625
 <p>
626 626
 Unlike with ordinary wifi, on the mesh you don't get a signal strength icon and so it's not simple to see if you have a good connection.
627 627
 </p>
@@ -644,9 +644,9 @@ When you are finished close the window and then select the <i>Network Restart</i
644 644
 </p>
645 645
 </div>
646 646
 </div>
647
-<div id="outline-container-orgc3d9324" class="outline-3">
648
-<h3 id="orgc3d9324">Connecting to the internet</h3>
649
-<div class="outline-text-3" id="text-orgc3d9324">
647
+<div id="outline-container-org3bf2ff9" class="outline-3">
648
+<h3 id="org3bf2ff9">Connecting to the internet</h3>
649
+<div class="outline-text-3" id="text-org3bf2ff9">
650 650
 <p>
651 651
 If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable, then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. <a href="https://en.wikipedia.org/wiki/Freifunk">Freifunk</a> works in a similar way.
652 652
 </p>
@@ -654,11 +654,62 @@ If you need to be able to access the internet from the mesh then connect one of
654 654
 <p>
655 655
 After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
656 656
 </p>
657
+
658
+<p>
659
+If for legal reasons you need to connect to the internet via a VPN then openvpn is preinstalled and you can run the command:
660
+</p>
661
+
662
+<div class="org-src-container">
663
+<pre class="src src-bash">sudo openvpn myclient.ovpn
664
+</pre>
665
+</div>
666
+
667
+<p>
668
+Where <i>myclient.ovpn</i> comes from your VPN provider and with the password "<i>freedombone</i>".
669
+</p>
670
+</div>
671
+</div>
672
+<div id="outline-container-org624d04c" class="outline-3">
673
+<h3 id="org624d04c">Connecting two meshes over the internet via a VPN tunnel</h3>
674
+<div class="outline-text-3" id="text-org624d04c">
675
+<p>
676
+Maybe the internet exists, but you don't care about getting any content from it and just want to use it as a way to connect mesh networks from different geographical locations together. VPN configuration, pem and stunnel files exist within the home directory. Edit the configuration with:
677
+</p>
678
+
679
+<div class="org-src-container">
680
+<pre class="src src-bash">nano ~/client.ovpn
681
+</pre>
682
+</div>
683
+
684
+<p>
685
+Edit the IP address or domain for the mesh that you wish to connect to within the <i>route</i> command:
686
+</p>
687
+
688
+<div class="org-src-container">
689
+<pre class="src src-bash">route [mesh IP or domain] 255.255.255.255 net_gateway
690
+</pre>
691
+</div>
692
+
693
+<p>
694
+Then you can connect to the other mesh with:
695
+</p>
696
+
697
+<div class="org-src-container">
698
+<pre class="src src-bash"><span class="org-builtin">cd</span> /home/fbone
699
+sudo stunnel stunnel-client.conf
700
+sudo openvpn client.ovpn
701
+</pre>
657 702
 </div>
703
+
704
+<p>
705
+Using the password "<i>freedombone</i>". From a deep packet inspection point of view the traffic going over the internet will just look like any other TLS connection to a server.
706
+</p>
658 707
 </div>
659
-<div id="outline-container-orgdceba0f" class="outline-3">
660
-<h3 id="orgdceba0f">Mobile devices (phones, etc)</h3>
661
-<div class="outline-text-3" id="text-orgdceba0f">
708
+</div>
709
+
710
+<div id="outline-container-orgd9e5261" class="outline-3">
711
+<h3 id="orgd9e5261">Mobile devices (phones, etc)</h3>
712
+<div class="outline-text-3" id="text-orgd9e5261">
662 713
 <p>
663 714
 To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "<i>mesh-192.168.1.83</i>").
664 715
 </p>
@@ -680,9 +731,9 @@ On some android devices you may need to move the downloaded APK file from the <b
680 731
 </p>
681 732
 </div>
682 733
 </div>
683
-<div id="outline-container-org6f1f090" class="outline-3">
684
-<h3 id="org6f1f090">Chat System</h3>
685
-<div class="outline-text-3" id="text-org6f1f090">
734
+<div id="outline-container-org20eff98" class="outline-3">
735
+<h3 id="org20eff98">Chat System</h3>
736
+<div class="outline-text-3" id="text-org20eff98">
686 737
 <p>
687 738
 Ensure that you're within wifi range of at least one other mesh peer (could be a router or client) and then you should see that the <i>Chat</i> and <i>Other Users</i> icons appear. Select the users icon and you should see a list of users on the mesh. Select the <i>Chat</i> icon and once you are connected you should see the status light turn green. If after a few minutes you don't get the green status light then try closing and re-opening the Tox chat application. Select the plus button to add a friend and then copy and paste in a Tox ID from the users list.
688 739
 </p>
@@ -741,9 +792,9 @@ At present video doesn't work reliably, but text and voice chat do work well.
741 792
 </div>
742 793
 </div>
743 794
 
744
-<div id="outline-container-org8ac8f7d" class="outline-3">
745
-<h3 id="org8ac8f7d">Social Network</h3>
746
-<div class="outline-text-3" id="text-org8ac8f7d">
795
+<div id="outline-container-orgfcc0537" class="outline-3">
796
+<h3 id="orgfcc0537">Social Network</h3>
797
+<div class="outline-text-3" id="text-orgfcc0537">
747 798
 <p>
748 799
 Patchwork is available as a social networking system for the mesh. Like all social network systems it has a stream of posts and you can follow or unfollow other users. You can also send private messages to other users with end-to-end encryption.
749 800
 </p>
@@ -778,9 +829,9 @@ The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be
778 829
 </div>
779 830
 </div>
780 831
 
781
-<div id="outline-container-org25fbdb4" class="outline-3">
782
-<h3 id="org25fbdb4">Sharing Files</h3>
783
-<div class="outline-text-3" id="text-org25fbdb4">
832
+<div id="outline-container-orgc02ecf3" class="outline-3">
833
+<h3 id="orgc02ecf3">Sharing Files</h3>
834
+<div class="outline-text-3" id="text-orgc02ecf3">
784 835
 <p>
785 836
 You can make files publicly available on the network simply by dragging and dropping them into the <i>Public</i> folder on the desktop. To view the files belonging to another user select the desktop icon called <i>Visit a site</i> and enter the username or Tox ID of the other user.
786 837
 </p>
@@ -795,9 +846,9 @@ You can make files publicly available on the network simply by dragging and drop
795 846
 </div>
796 847
 </div>
797 848
 
798
-<div id="outline-container-org00ad2c3" class="outline-3">
799
-<h3 id="org00ad2c3">Blogging</h3>
800
-<div class="outline-text-3" id="text-org00ad2c3">
849
+<div id="outline-container-orgbcb6881" class="outline-3">
850
+<h3 id="orgbcb6881">Blogging</h3>
851
+<div class="outline-text-3" id="text-orgbcb6881">
801 852
 <p>
802 853
 To create a blog post select the <i>Blog</i> icon on the desktop and then use the up and down cursor keys, space bar and enter key to add a new entry. Edit the title of the entry and add your text. You can also include photos if you wish - just copy them to the <b>CreateBlog/content/images</b> directory and then link to them as shown.
803 854
 </p>