mirror of
https://github.com/cwinfo/envayasms.git
synced 2025-07-06 15:04:04 +00:00
add titles and reorganize to avoid showing .html extension
This commit is contained in:
@ -1,4 +1,6 @@
|
||||
<h2>Comparison to Alternative Methods</h2>
|
||||
id: comparison
|
||||
title: Comparison to Alternative Methods
|
||||
---
|
||||
<p>
|
||||
SMS gateways can be created using several alternative methods, including hosted services (e.g. Twilio, Tropo, Clickatell),
|
||||
connecting GSM phones/modems to a computer (e.g. FrontlineSMS, RapidSMS, Kannel),
|
@ -1,7 +1,6 @@
|
||||
layout: default.twig
|
||||
id: faq
|
||||
title: Frequently Asked Questions
|
||||
---
|
||||
<h2>Frequently Asked Questions</h2>
|
||||
|
||||
<h4>
|
||||
What phones are compatible with EnvayaSMS?
|
||||
</h4>
|
||||
@ -56,11 +55,11 @@ EnvayaSMS is a complete rewrite that shares little code with KalSMS.
|
||||
<p>
|
||||
EnvayaSMS builds upon the idea of KalSMS by adding many new features that would be necessary for anyone deploying an SMS gateway in the field,
|
||||
such as sending more than 100 messages per hour, authenticating the phone to the server, and retrying forwarding messages after transient errors.
|
||||
For a complete list of changes, see the <a href='history.html'>History</a> page.
|
||||
For a complete list of changes, see the <a href='/history/'>History</a> page.
|
||||
</p>
|
||||
<p>
|
||||
EnvayaSMS's server API is incompatible with that of KalSMS. Anyone switching from KalSMS to EnvayaSMS must
|
||||
update their server to use the new API described on the <a href='serverapi.html'>API Reference</a> page.
|
||||
update their server to use the new API described on the <a href='/serverapi/'>API Reference</a> page.
|
||||
</p>
|
||||
<p>
|
||||
As of 2011, KalSMS is no longer actively developed, and new development will occur on the EnvayaSMS project.
|
@ -1,5 +1,6 @@
|
||||
<h2>History</h2>
|
||||
|
||||
id: history
|
||||
title: History
|
||||
---
|
||||
Version 2.0-beta (2011/09/22)
|
||||
|
||||
<ul>
|
@ -1,5 +1,7 @@
|
||||
<h2>How it Works</h2>
|
||||
|
||||
id: how
|
||||
layout: default.twig
|
||||
title: How it Works
|
||||
---
|
||||
<p>
|
||||
In the simplest configuration, EnvayaSMS only needs to be installed on one phone.
|
||||
Suppose that you have installed EnvayaSMS on an Android phone in Dar es Salaam,
|
@ -1,11 +1,11 @@
|
||||
id: home
|
||||
layout: default.twig
|
||||
---
|
||||
|
||||
<p>
|
||||
<div style='float:right;padding-left:10px;padding-bottom:10px'>
|
||||
<img src='media/screenshot-main.png' width='212' height='350' />
|
||||
<img src='/media/screenshot-main.png' width='212' height='350' />
|
||||
<br />
|
||||
<img src='media/screenshot-settings.png' width='212' height='350' />
|
||||
<img src='/media/screenshot-settings.png' width='212' height='350' />
|
||||
|
||||
</div>
|
||||
|
||||
@ -54,6 +54,6 @@ It works wherever the phone can receive SMS messages and access the Internet
|
||||
EnvayaSMS is compatible with many old or inexpensive Android phones, e.g. the LG GT540, currently $120 on Amazon.com.
|
||||
</p>
|
||||
|
||||
<a href='install.html' class='button'>
|
||||
<a href='/install/' class='button'>
|
||||
Install EnvayaSMS Now
|
||||
</a>
|
@ -1,7 +1,6 @@
|
||||
layout: default.twig
|
||||
id: install
|
||||
title: Installing EnvayaSMS
|
||||
---
|
||||
<h2>Installing EnvayaSMS</h2>
|
||||
|
||||
Before installing EnvayaSMS, ensure that you have the following prerequisites:
|
||||
|
||||
<ul>
|
||||
@ -21,12 +20,12 @@ Using an Android phone, open <a href='https://market.android.com/details?id=org.
|
||||
<a href="https://market.android.com/details?id=org.envaya.sms">Open Android Market</a>
|
||||
</div>
|
||||
<a href="https://market.android.com/details?id=org.envaya.sms">
|
||||
<img src='media/qr.png' width='175' height='175' />
|
||||
<img src='/media/qr.png' width='175' height='175' />
|
||||
</a>
|
||||
</div>
|
||||
|
||||
<div style='float:left;padding-top:10px'>
|
||||
<img src='media/screenshot-market.png' style='border:1px solid black' width='484' height='240' />
|
||||
<img src='/media/screenshot-market.png' style='border:1px solid black' width='484' height='240' />
|
||||
</div>
|
||||
|
||||
<div style='clear:both;padding-top:10px'>
|
||||
@ -43,14 +42,14 @@ It is assumed that your organization already has an HTTP server, or has the tech
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Follow the instructions in the <a href='serverapi.html'>API Reference</a> page to learn how to construct a
|
||||
Follow the instructions in the <a href='/serverapi/'>API Reference</a> page to learn how to construct a
|
||||
resource on your HTTP server that can communicate with EnvayaSMS.
|
||||
</p>
|
||||
|
||||
<h3>Phone Configuration</h3>
|
||||
|
||||
<div style='float:right;padding-left:10px;padding-bottom:10px'>
|
||||
<img src='media/screenshot-settings.png' width='211' height='347' />
|
||||
<img src='/media/screenshot-settings.png' width='211' height='347' />
|
||||
</div>
|
||||
|
||||
|
@ -1,7 +1,6 @@
|
||||
layout: default.twig
|
||||
id: serverapi
|
||||
title: Server API Reference
|
||||
---
|
||||
<h2>Server API Reference</h2>
|
||||
|
||||
<p>
|
||||
EnvayaSMS communicates with the server via HTTP POST requests that expect an XML response.
|
||||
</p>
|
Reference in New Issue
Block a user