Okhatrimaza 2018com

Because the village had only a single satellite dish that gave a shaky 2 Mbps connection, the team decided to keep the site lightweight:

| Feature | Why It Was Chosen | Tools Used | |---------|------------------|------------| | Static HTML + CSS | No server‑side processing → less bandwidth | Visual Studio Code | | jQuery for simple interactivity | Familiar to Ayesha, easy to debug | jQuery 3.3 | | PayPal + local mobile‑money API | Global reach + local trust | PayPal Checkout, local API sandbox | | Responsive design | Many buyers would browse on phones | Bootstrap 4 | | Google Analytics (lite) | Track traffic without heavy scripts | GA4 (page‑view only) |

Ayesha taught the other four friends the basics of HTML, CSS, and git over a series of evenings by the tea stall’s flickering lantern. Within six weeks, the site was live, showcasing: okhatrimaza 2018com

On March 3, 2018, the website’s analytics recorded its first visitor from Toronto, Canada. The visitor, intrigued by the “Hand‑woven Himalayan Scarf – Midnight Blue,” added it to the cart, entered a credit card, and clicked Buy.

The payment gateway succeeded, but there was an unexpected hiccup: the village’s only internet‑enabled device (Ayesha’s old laptop) crashed after the transaction, and the team feared the order was lost. Because the village had only a single satellite

Lesson #1 – Redundancy is essential: They immediately set up a Google Form as a backup order receipt and added a WhatsApp Business number for customers to confirm orders.

Within an hour, a message popped up on the village’s community phone: “Order received – thank you! Your scarf will ship in 5–7 business days.” The customer in Toronto replied, “Can’t wait! Please send a photo once it’s ready.” On March 3, 2018 , the website’s analytics

The team shipped the scarf by courier, and a photo of the packaged product was sent back. The customer posted a glowing review on the site, and a small ripple began.

During a severe snowstorm in November 2018, the village lost electricity for three days. The team had already mirrored the website on a cheap Raspberry Pi running a local Wi‑Fi hotspot. Though orders could not be processed offline, they could still show the catalogue and take handwritten orders that were later entered once power returned.

Lesson #3 – Offline‑first thinking protects against infrastructure gaps.