When heading from Beirut to Sidon, one can’t help but notice the luxurious vegetation that surrounds the Awali River. The site of Eshmun lies within this lush valley of citrus groves, thus spreading its aromatic fragrances to roll back time and accompany the visitor in their discovery of this unique place.
A site rich with mythology and history, it is dedicated to the healing god Eshmun for whom the main sacred complex was initially erected. The location of the sanctuary is meaningful in itself, along the ancient Bostrenus (Nahr el-Awali river), near the Yidal source that served as part of the rituals.
Eshmun, according to legend, was a young hunter from Beirut with whom the goddess Astarte fell in love. The young man, in an attempt to escape from her advances, mutilated himself and dies. But the goddess, using her vital heat, brought him back to life with the attributes of a god. His death and resurrection gave this healing god the role of a fertility and vegetation god that dies and is reborn annually.
The cult of Eshmun is documented on many sites, such as Syria, Palestine, Egypt, Tunisia, Sardinia and other ancient cities around the Mediterranean Sea. The first written reference to Eshmun is the treaty signed in 754 B.C. between Mati’el, the king of Arpad in North Syria, and Assurnirani V, king of Assyria, where Eshmun is mentioned among the gods who warrant the treaty. Again, in 675-670 B.C., he is one of the god patrons of the treaty between the Assyrian king Esarhaddon and Ba’al I, king of Tyre. Would any of the kings break their promises:
“[…] May Melqart and Eshmun deliver your land to destruction, your people to be deported; from your land […] May they make food to disappear from your mouth and clothes from your body, oil for your ointment […]”
Eshmun was later associated with the Greek healing god Asclepius. He was depicted on coins minted by the city of Berytos (Beirut) holding the rod of Asclepius (a serpent-entangled rod, today’s medical symbol).

The main center of Eshmun’s cult seems to be the city of Sidon. Throughout the Persian Period, Sidon was a prosperous city; its monarchs were distinguished by their wealth and its elite by their culture and flourishing industries. It is then that Eshmunazar II, King of Sidon, and his mother Amoshtart started the temple construction.
The construction of the temple is attested by the 22-line Phoenician inscription, engraved on the lid of Eshmunazar’s sarcophagus (exhibited at the Louvre Museum, Department of Near Eastern Antiquities).
The inscription reads:
“[…] and it was we who built the temple for Eshmun, holy prince of the sacred spring YDLL, and enthroned him.”

The temple complex, dedicated to healing, was erected near the sacred spring. The main monument had a pyramidal shape, resembling a ziggurat (a terraced compound of receding levels built with massive stone), while an ingenious hydraulic tube system conveyed the curative water to the sacral basins, where citizens performed their ritual purifications or immersed for therapeutic sacraments.
During the reign of King Bodashtart (fifth century B.C.) renovation and development works were executed on the site. Inscriptions found on the foundations of the monumental podium indicate that the descendants of Eshmunazar carried out works all through their reign at the site:
“Bodashtart, king of the Sidonians, built this temple, aided by his son, the crown prince, Yatonmilk.”
Throne of Astarte, granite. In situ
The sanctuary evolved in dimension and in style, becoming a large sacral complex. The monumental podium was decorated with hunting scenes. The terrace atop of the podium was covered by a Greco-Persian style marble temple probably built by Ionic artisans.
Changes continued to be implemented on the site during the Hellenistic Period (third century B.C. – first century B.C.). It is then that Greeks associated Eshmun with the god Asclepius, thus trying to Hellenize the god. Large chapels were added near the podium. One of the chapels holds a throne carved in a single block of granite, attributed to the goddess Astarte. The throne, flanked with two lion sculptures, rests against one of the chapel’s walls embellished with relied sculptures of hunting scenes. During the Roman Period (first century B.C. – fourth century A.D.) a monumental staircase ornamented with mosaics was built near the sanctuary, and led to the top of the podium. A nymphaeum (monument dedicated to water nymphs) was added near the staircase, with a mosaic depicting the Maenads covering its floor.
The last period represented on the site is the Byzantine Period. A residential area and a basilica were built, whilst the temple declined and was abandoned as Christianity replaced paganism.
At the beginning of the 19th century, only two massive parallel walls made of massive stone masonry were visible, and the site was used as a stone-pit for reuse in nearby constructions.
Many artifacts were discovered during the excavations held on the site, among which were the Babies of Eshmun– marble sculptures of little children lying on their side and holding an animal. Those votive life-size statuaries seem to have been purposely broken when they were tossed into the sacred canal. Various interpretations are given by scholars for the purpose of the statuaries. Their vocation to secure divine protection for the boy is clarified through the Phoenician inscription inscribed on one of them, which reads:
“This statuette was given by Baalshillem, son of king Banaa, king of the Sidonians, to his lord Eshmun of the spring Ydlal. May he bless him.”
The royal child’s head is shaved, his torso is bare and his lower body is wrapped in a large cloth. And he holds with his right hand a dove, the symbol of love and peace.
Temple boy, marble. Beirut National Museum.
HOMEland Magazine
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to