Re: Guidance needed: Mercury template vs. Custom template
Michael Emmerich via opencms-dev <[email protected]> Wed, 30 Jul 2025 09:51:37 +0200
| Newsgroups | gmane.comp.cms.opencms.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============4904451272976505876==
Content-Type: multipart/alternative;
boundary="------------rT47PY9poUn3HUbOodJRHm0k"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------rT47PY9poUn3HUbOodJRHm0k
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hello Nivedita,
You're looking to set up a /main website/ for the headquarters and a
/subsite for each school/. If each school’s website follows a similar
layout, it’s best to create a *blueprint* (or base template) that can be
duplicated for each school.
There are two key areas you should focus on:
1.
The general concept of pages with *Mercury*
2.
The use of the *Sitemap Editor* to build the site structure
1. Understanding Mercury Page Concepts
You've already followed the dev-block instructions to set up your site,
which included creating a *header*, *footer*, and a base
*template-model*. This model defines the global layout shared by all
pages (i.e., consistent header and footer). Between these sections lies
the *content area*, where Mercury's page grid comes into play.
Mercury is built on *Bootstrap*, so it uses a *12-column grid* system.
This allows you to divide each page into rows and columns, where content
elements are placed.
Example Layout
Suppose you want a layout like this:
*
A full-width image slider at the top
*
Three teaser boxes side by side
*
A full-width text area at the bottom
Your row structure would look like:
*
*Row 1*: 1 column (12 columns wide)
*
*Row 2*: 3 columns (each 4 columns wide)
*
*Row 3*: 1 column (12 columns wide)
The numbers (12, 4-4-4, etc.) refer to how many of the 12 available grid
columns are used per container.
Adding Rows to a Page
After creating a new page via the Sitemap Editor (more on that below),
open it in the *Page Editor*, click *“Add Content” → “Template
Elements”*, and choose *“Layout Row”*.
You'll now see predefined layout options:
*
Single-column (12)
*
Two-column (e.g., 6-6, 8-4)
*
Three-column (4-4-4), etc.
Try out different options to see how they behave. You can add or remove
rows anytime. If you delete a row, all content inside it will also be
removed—so be sure to move any important elements to another row first.
Once your layout is in place, use *“Add Content” → “Content Elements”*
to drag and drop content blocks into the grid.
Optional: Predefine Grid Layouts
If you frequently use the same grid structure, you can define rows
/directly in the template-model/. That way, new pages created from this
template will already include the layout. You can even create multiple
template-models with different layouts.
Important: Editing the layout of a newly created page *does not affect*
the original template-model.
2. Creating the Site Structure with the Sitemap Editor
To build the site and navigation structure, always use the *Sitemap
Editor*, not the Explorer.
In OpenCms, the sitemap defines the structure and navigation of your
website. Here’s how to use it:
1.
Open the *Sitemap Editor*
2.
Click *“Add Pages”* in the toolbar
3.
Choose a *template-model*
4.
Drag the new page to your desired location and name it
The filename (URL) is automatically set based on the name you give.
You can reorder pages using the *"nine dots"* icon or nest one page
under another by dragging it onto the parent’s icon. This defines
hierarchical navigation (e.g., subpages).
Setting Up School Subsites
You could now use the sitemap editor to build the structure of your main
(headquarters) site. One page could be the entry for all your schools
subsites with a structure like this:
/schools/
/schools/school_1/
/schools/school_2/
/schools/school_3/
[...]
1.
Create a page called *"schools"*
2.
Under it, create a page *"school_1"*
3.
Open the "burger menu" of the *school_1* page (three lines icon),
and go to
*Advanced → Create Sub-Sitemap*
This turns *school_1* into its own *subsite* with a separate sitemap.
Clicking on it will open a *blank sitemap* for that school, where you
can create its individual pages.
Each subsite can have:
*
Its own template-models
*
Unique header/footer
*
Independent configuration
If none are defined, the parent’s templates and configurations are used.
Store Content Locally in Subsites
To ensure all content elements for a subsite are saved within it:
*
Open the subsite in the *Sitemap Editor*
*
Click the *burger menu* in the toolbar → *Advanced → Sitemap
Configuration*
*
Enable *"Local content elements"*
Final Tip
The best way to get familiar with Mercury and OpenCms is to experiment!
Create test pages, try different layouts, and explore the sitemap options.
Let me know if you need help with any specific step!
Kind regards,
Michael
Am 21.07.25 um 07:24 schrieb niveditasheoran via opencms-dev:
>
> Hi,
>
> I followed the step-by-step instructions provided in the link and
> successfully created a template of my own. As shown in the attached
> pictures, our firm used to manage a site with a headquarter and around
> 900–1000 sub-sites for individual schools.
>
> I am planning to develop something similar. Since the headquarters
> website is already in place, my idea is to start by building the
> homepage for one school and then replicate it for the others. These
> individual school sites will be linked from the headquarters site.
>
> However, I’m not sure where to begin—particularly when it comes to
> creating the homepage, which should include sections like a banner,
> About Us, statistics, Chairman's message, etc.
>
> Could someone please guide me through the process?
>
> Best regards,
>
> Nivedita
>
> On July 17, 2025 at 5:53 PM Michael Emmerich via opencms-dev
> <[email protected]> wrote:
>>
>> Nivedita,
>>
>> I would suggest to use the Mercury template for this task. Making
>> your own template from scratch without any OpenCms experience can be
>> a bit challenging, I would only do this if there very special design
>> requirements that cannot be made with Mercury.
>>
>> In the Mercury template you have different content types that should
>> provide everything that is needed for a school website.
>>
>> Some time ago, I made a beginners step-by-step instruction how to
>> start a complete new website with Mercury, you can fin it here:
>>
>> https://www.opencms.org/en/article/How-to-create-a-new-website-using-the-Mercury-template/
>>
>> A place to look is the general OpenCms documentation here:
>> https://documentation.opencms.org/opencms-documentation/
>>
>> You find an explanation of the OpenCms workplace and several more
>> technical infos for developers.
>>
>> There is a very detailed documentation of the Mercury template,
>> explaining all the content types, their options etc. It can be found
>> here: https://mercury-template.opencms.org/
>>
>> This one is only available in German, so you would need some online
>> translation of it, for example the build in translation of Chrome.
>>
>> Kind regards,
>>
>> Michael
>>
>> Am 17.07.25 um 13:04 schrieb niveditasheoran via opencms-dev:
>>> Hi,
>>>
>>> I’m totally new to OpenCMS and have been tasked with creating a
>>> website for a school. I’m exploring whether I should use the
>>> *Mercury template* or build a *custom template* from scratch.
>>>
>>> Could someone guide me on what would be the recommended approach for
>>> a school website?
>>> Also, are there any *step-by-step guides or documentation* available
>>> to help with either option — especially for beginners?
>>>
>>> Any suggestions or resources would be really appreciated.
>>>
>>> Thanks in advance!
>>>
>>> Nivedita Sheoran
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------------------------------------
>>>
>>> [ C-DAC is on Social-Media too. Kindly follow us at:
>>> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>>>
>>> This e-mail is for the sole use of the intended recipient(s) and may
>>> contain confidential and privileged information. If you are not the
>>> intended recipient, please contact the sender by reply e-mail and
>>> destroy
>>> all copies and the original message. Any unauthorized review, use,
>>> disclosure, dissemination, forwarding, printing or copying of this
>>> email
>>> is strictly prohibited and appropriate legal action will be taken.
>>> ------------------------------------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> This mail is sent to you from the opencms-dev mailing list
>>> To change your list options, or to unsubscribe from the list, please visit
>>> https://lists.opencms.org/mailman/listinfo/opencms-dev
>>>
>>>
>>>
>> --
>> Michael Emmerich
>>
>> -------------------
>>
>> Alkacon Software GmbH & Co. KG - The OpenCms Experts
>>
>> http://www.alkacon.com
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please
> visit
> https://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
>
>
>
>
> ------------------------------------------------------------------------------------------------------------
>
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> ------------------------------------------------------------------------------------------------------------
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> https://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
>
--
Michael Emmerich
Alkacon Software GmbH & Co. KG - The OpenCms Experts
http://www.alkacon.com
http://www.opencms.org
--------------rT47PY9poUn3HUbOodJRHm0k
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p data-start="134" data-end="153"><span data-start="134"
data-end="153">Hello Nivedita,</span></p>
<p data-start="155" data-end="396">You're looking to set up a <em
data-start="182" data-end="196">main website</em> for the
headquarters and a <em data-start="224" data-end="249">subsite
for each school</em>. If each school’s website follows a similar
layout, it’s best to create a <strong data-start="324"
data-end="337">blueprint</strong> (or base template) that can be
duplicated for each school.</p>
<p data-start="398" data-end="442">There are two key areas you
should focus on:</p>
<ol data-start="444" data-end="565">
<li data-start="444" data-end="500">
<p data-start="447" data-end="500">The general concept of pages
with <strong data-start="489" data-end="500">Mercury</strong></p>
</li>
<li data-start="501" data-end="565">
<p data-start="504" data-end="565">The use of the <strong
data-start="519" data-end="537">Sitemap Editor</strong> to
build the site structure</p>
</li>
</ol>
<h3 data-start="572" data-end="614">1. Understanding Mercury Page
Concepts</h3>
<p data-start="616" data-end="956">You've already followed the
dev-block instructions to set up your site, which included
creating a <strong data-start="714" data-end="724">header</strong>,
<strong data-start="726" data-end="736">footer</strong>, and a
base <strong data-start="749" data-end="767">template-model</strong>.
This model defines the global layout shared by all pages (i.e.,
consistent header and footer). Between these sections lies the <strong
data-start="896" data-end="912">content area</strong>, where
Mercury's page grid comes into play.</p>
<p data-start="958" data-end="1126">Mercury is built on <strong
data-start="978" data-end="991">Bootstrap</strong>, so it uses a
<strong data-start="1006" data-end="1024">12-column grid</strong>
system. This allows you to divide each page into rows and columns,
where content elements are placed.</p>
<h4 data-start="1128" data-end="1147">Example Layout</h4>
<p data-start="1148" data-end="1184">Suppose you want a layout like
this:</p>
<ul data-start="1185" data-end="1296">
<li data-start="1185" data-end="1223">
<p data-start="1187" data-end="1223">A full-width image slider
at the top</p>
</li>
<li data-start="1224" data-end="1257">
<p data-start="1226" data-end="1257">Three teaser boxes side by
side</p>
</li>
<li data-start="1258" data-end="1296">
<p data-start="1260" data-end="1296">A full-width text area at
the bottom</p>
</li>
</ul>
<p data-start="1298" data-end="1333">Your row structure would look
like:</p>
<ul data-start="1334" data-end="1458">
<li data-start="1334" data-end="1373">
<p data-start="1336" data-end="1373"><strong data-start="1336"
data-end="1345">Row 1</strong>: 1 column (12 columns wide)</p>
</li>
<li data-start="1374" data-end="1418">
<p data-start="1376" data-end="1418"><strong data-start="1376"
data-end="1385">Row 2</strong>: 3 columns (each 4 columns
wide)</p>
</li>
<li data-start="1419" data-end="1458">
<p data-start="1421" data-end="1458"><strong data-start="1421"
data-end="1430">Row 3</strong>: 1 column (12 columns wide)</p>
</li>
</ul>
<p data-start="1460" data-end="1564">The numbers (12, 4-4-4, etc.)
refer to how many of the 12 available grid columns are used per
container.</p>
<h3 data-start="1571" data-end="1596">Adding Rows to a Page</h3>
<p data-start="1598" data-end="1776">After creating a new page via
the Sitemap Editor (more on that below), open it in the <strong
data-start="1684" data-end="1699">Page Editor</strong>, click <strong
data-start="1707" data-end="1746">“Add Content” → “Template
Elements”</strong>, and choose <strong data-start="1759"
data-end="1775">“Layout Row”</strong>.</p>
<p data-start="1778" data-end="1819">You'll now see predefined
layout options:</p>
<ul data-start="1820" data-end="1899">
<li data-start="1820" data-end="1840">
<p data-start="1822" data-end="1840">Single-column (12)</p>
</li>
<li data-start="1841" data-end="1870">
<p data-start="1843" data-end="1870">Two-column (e.g., 6-6, 8-4)</p>
</li>
<li data-start="1871" data-end="1899">
<p data-start="1873" data-end="1899">Three-column (4-4-4), etc.</p>
</li>
</ul>
<p data-start="1901" data-end="2114">Try out different options to
see how they behave. You can add or remove rows anytime. If you
delete a row, all content inside it will also be removed—so be
sure to move any important elements to another row first.</p>
<p data-start="2116" data-end="2235">Once your layout is in place,
use <strong data-start="2150" data-end="2188">“Add Content” →
“Content Elements”</strong> to drag and drop content blocks into
the grid.</p>
<h4 data-start="2237" data-end="2274">Optional: Predefine Grid
Layouts</h4>
<p data-start="2275" data-end="2524">If you frequently use the same
grid structure, you can define rows <em data-start="2342"
data-end="2374">directly in the template-model</em>. That way,
new pages created from this template will already include the
layout. You can even create multiple template-models with
different layouts.</p>
<p data-start="2526" data-end="2628">Important: Editing the layout
of a newly created page <strong data-start="2580" data-end="2599">does
not affect</strong> the original template-model.</p>
<h3 data-start="2635" data-end="2693">2. Creating the Site Structure
with the Sitemap Editor</h3>
<p data-start="2695" data-end="2791">To build the site and
navigation structure, always use the <strong data-start="2754"
data-end="2772">Sitemap Editor</strong>, not the Explorer.</p>
<p data-start="2793" data-end="2892">In OpenCms, the sitemap defines
the structure and navigation of your website. Here’s how to use
it:</p>
<ol data-start="2894" data-end="3053">
<li data-start="2894" data-end="2924">
<p data-start="2897" data-end="2924">Open the <strong
data-start="2906" data-end="2924">Sitemap Editor</strong></p>
</li>
<li data-start="2925" data-end="2964">
<p data-start="2928" data-end="2964">Click <strong
data-start="2934" data-end="2949">“Add Pages”</strong> in
the toolbar</p>
</li>
<li data-start="2965" data-end="2995">
<p data-start="2968" data-end="2995">Choose a <strong
data-start="2977" data-end="2995">template-model</strong></p>
</li>
<li data-start="2996" data-end="3053">
<p data-start="2999" data-end="3053">Drag the new page to your
desired location and name it</p>
</li>
</ol>
<p data-start="3055" data-end="3122">The filename (URL) is
automatically set based on the name you give.</p>
<p data-start="3124" data-end="3301">You can reorder pages using the
<strong data-start="3156" data-end="3171">"nine dots"</strong>
icon or nest one page under another by dragging it onto the
parent’s icon. This defines hierarchical navigation (e.g.,
subpages).</p>
<h3 data-start="3308" data-end="3338">Setting Up School Subsites</h3>
<p>You could now use the sitemap editor to build the structure of
your main (headquarters) site. One page could be the entry for all
your schools subsites with a structure like this:</p>
<p>/schools/</p>
<p>/schools/school_1/</p>
<p>/schools/school_2/</p>
<p>/schools/school_3/</p>
<p>[...]</p>
<p><br>
</p>
<ol data-start="3453" data-end="3652">
<li data-start="3453" data-end="3490">
<p data-start="3456" data-end="3490">Create a page called <strong
data-start="3477" data-end="3490">"schools"</strong></p>
</li>
<li data-start="3491" data-end="3532">
<p data-start="3494" data-end="3532">Under it, create a page <strong
data-start="3518" data-end="3532">"school_1"</strong></p>
</li>
<li data-start="3533" data-end="3652">
<p data-start="3536" data-end="3652">Open the "burger menu" of
the <strong data-start="3566" data-end="3578">school_1</strong>
page (three lines icon), and go to<br data-start="3613"
data-end="3616">
<strong data-start="3619" data-end="3652">Advanced → Create
Sub-Sitemap</strong></p>
</li>
</ol>
<p data-start="3654" data-end="3832">This turns <strong
data-start="3665" data-end="3677">school_1</strong> into its own
<strong data-start="3691" data-end="3702">subsite</strong> with a
separate sitemap. Clicking on it will open a <strong
data-start="3755" data-end="3772">blank sitemap</strong> for
that school, where you can create its individual pages.</p>
<p data-start="3834" data-end="3856">Each subsite can have:</p>
<ul data-start="3857" data-end="3933">
<li data-start="3857" data-end="3882">
<p data-start="3859" data-end="3882">Its own template-models</p>
</li>
<li data-start="3883" data-end="3905">
<p data-start="3885" data-end="3905">Unique header/footer</p>
</li>
<li data-start="3906" data-end="3933">
<p data-start="3908" data-end="3933">Independent configuration</p>
</li>
</ul>
<p data-start="3935" data-end="4007">If none are defined, the
parent’s templates and configurations are used.</p>
<h4 data-start="4009" data-end="4047">Store Content Locally in
Subsites</h4>
<p data-start="4048" data-end="4113">To ensure all content elements
for a subsite are saved within it:</p>
<ul data-start="4114" data-end="4278">
<li data-start="4114" data-end="4158">
<p data-start="4116" data-end="4158">Open the subsite in the <strong
data-start="4140" data-end="4158">Sitemap Editor</strong></p>
</li>
<li data-start="4159" data-end="4240">
<p data-start="4161" data-end="4240">Click the <strong
data-start="4171" data-end="4186">burger menu</strong> in
the toolbar → <strong data-start="4204" data-end="4240">Advanced
→ Sitemap Configuration</strong></p>
</li>
<li data-start="4241" data-end="4278">
<p data-start="4243" data-end="4278">Enable <strong
data-start="4250" data-end="4278">"Local content elements"</strong></p>
</li>
</ul>
<h3 data-start="4285" data-end="4298">Final Tip</h3>
<p data-start="4300" data-end="4446">The best way to get familiar
with Mercury and OpenCms is to experiment! Create test pages, try
different layouts, and explore the sitemap options.</p>
<p data-start="4448" data-end="4500">Let me know if you need help
with any specific step!</p>
<p data-start="4502" data-end="4529">Kind regards,</p>
<p data-start="4502" data-end="4529">Michael</p>
<br>
<p><br>
</p>
<div class="moz-cite-prefix">Am 21.07.25 um 07:24 schrieb
niveditasheoran via opencms-dev:<br>
</div>
<blockquote type="cite"
cite="mid:160098304.2452.1753075461018.JavaMail.open-xchange@webmail.cdac.in">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div> <br>
<div id="m#msg-a:r4836045702067483676"
class="mail-message expanded">
<div id="m#msg-a:r4836045702067483676-header"
class="mail-message-header spacer"> </div>
<div id="m#msg-a:r4836045702067483676-content"
class="mail-message-content collapsible zoom-normal mail-show-images ">
<div class="clear">
<div dir="ltr">
<p>Hi,</p>
<p>I followed the step-by-step instructions provided in
the link and successfully created a template of my
own. As shown in the attached pictures, our firm used
to manage a site with a headquarter and around
900–1000 sub-sites for individual schools.</p>
<p>I am planning to develop something similar. Since the
headquarters website is already in place, my idea is
to start by building the homepage for one school and
then replicate it for the others. These individual
school sites will be linked from the headquarters
site.</p>
<p>However, I’m not sure where to begin—particularly
when it comes to creating the homepage, which should
include sections like a banner, About Us, statistics,
Chairman's message, etc.</p>
<p>Could someone please guide me through the process?</p>
<p>Best regards,</p>
<div> Nivedita </div>
</div>
</div>
</div>
<div id="m#msg-a:r4836045702067483676-footer"
class="mail-message-footer spacer collapsible"> </div>
</div>
</div>
<div> <br>
On July 17, 2025 at 5:53 PM Michael Emmerich via opencms-dev
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </div>
<div style="position: relative;">
<blockquote
style="margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;"
type="cite">
<p>Nivedita,</p>
<p>I would suggest to use the Mercury template for this task.
Making your own template from scratch without any OpenCms
experience can be a bit challenging, I would only do this if
there very special design requirements that cannot be made
with Mercury. </p>
<p>In the Mercury template you have different content types
that should provide everything that is needed for a school
website.</p>
<p>Some time ago, I made a beginners step-by-step instruction
how to start a complete new website with Mercury, you can
fin it here:</p>
<p><a
href="https://www.opencms.org/en/article/How-to-create-a-new-website-using-the-Mercury-template/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.opencms.org/en/article/How-to-create-a-new-website-using-the-Mercury-template/</a></p>
<p> </p>
<p>A place to look is the general OpenCms documentation here:
<a
href="https://documentation.opencms.org/opencms-documentation/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://documentation.opencms.org/opencms-documentation/</a></p>
<p>You find an explanation of the OpenCms workplace and
several more technical infos for developers.</p>
<p> </p>
<p>There is a very detailed documentation of the Mercury
template, explaining all the content types, their options
etc. It can be found here: <a
href="https://mercury-template.opencms.org/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://mercury-template.opencms.org/</a></p>
<p>This one is only available in German, so you would need
some online translation of it, for example the build in
translation of Chrome.</p>
<p> </p>
<p> </p>
<p>Kind regards,</p>
<p>Michael</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<div class="moz-cite-prefix"> Am 17.07.25 um 13:04 schrieb
niveditasheoran via opencms-dev: </div>
<blockquote type="cite">
<div id="m#msg-a:r-771192978873524482"
class="mail-message expanded">
<div id="m#msg-a:r-771192978873524482-header"
class="mail-message-header spacer"> <span
style="font-size: 9pt;">Hi,</span> </div>
<div id="m#msg-a:r-771192978873524482-content"
class="mail-message-content collapsible zoom-normal mail-show-images ">
<div class="clear">
<div dir="auto">
<div dir="auto">
<div>
<div dir="ltr">
<p>I’m totally new to OpenCMS and have been
tasked with creating a website for a school.
I’m exploring whether I should use the <strong>Mercury
template</strong> or build a <strong>custom
template</strong> from scratch.</p>
<p>Could someone guide me on what would be the
recommended approach for a school website?<br>
Also, are there any <strong>step-by-step
guides or documentation</strong> available
to help with either option — especially for
beginners?</p>
<p>Any suggestions or resources would be
really appreciated.</p>
<p>Thanks in advance!</p>
</div>
</div>
<div> Nivedita Sheoran </div>
</div>
</div>
</div>
</div>
<div id="m#msg-a:r-771192978873524482-footer"
class="mail-message-footer spacer collapsible"> </div>
</div>
<br>
<img src="https://pramani.cdac.in/signature.jpg" border="0"
moz-do-not-send="true"> <br>
<br>
------------------------------------------------------------------------------------------------------------
<br>
[ C-DAC is on Social-Media too. Kindly follow us at: <br>
Facebook: <a href="https://www.facebook.com/CDACINDIA"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.facebook.com/CDACINDIA</a>
& Twitter: @cdacindia ] <br>
<br>
This e-mail is for the sole use of the intended recipient(s)
and may <br>
contain confidential and privileged information. If you are
not the <br>
intended recipient, please contact the sender by reply
e-mail and destroy <br>
all copies and the original message. Any unauthorized
review, use, <br>
disclosure, dissemination, forwarding, printing or copying
of this email <br>
is strictly prohibited and appropriate legal action will be
taken. <br>
------------------------------------------------------------------------------------------------------------
<br>
<pre class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a href="https://lists.opencms.org/mailman/listinfo/opencms-dev"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.opencms.org/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature">--
Michael Emmerich
-------------------
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a href="http://www.alkacon.com" moz-do-not-send="true"
class="moz-txt-link-freetext">http://www.alkacon.com</a>
</pre>
</blockquote>
<br>
_______________________________________________ <br>
This mail is sent to you from the opencms-dev mailing list <br>
To change your list options, or to unsubscribe from the list,
please visit <br>
<a class="moz-txt-link-freetext" href="https://lists.opencms.org/mailman/listinfo/opencms-dev">https://lists.opencms.org/mailman/listinfo/opencms-dev</a> <br>
<br>
<br>
<br>
</div>
<br>
<img src="https://pramani.cdac.in/signature.jpg"
moz-do-not-send="true">
<br>
<br>
------------------------------------------------------------------------------------------------------------
<br>
[ C-DAC is on Social-Media too. Kindly follow us at:
<br>
Facebook: <a class="moz-txt-link-freetext" href="https://www.facebook.com/CDACINDIA">https://www.facebook.com/CDACINDIA</a> & Twitter:
@cdacindia ]
<br>
<br>
This e-mail is for the sole use of the intended recipient(s) and
may
<br>
contain confidential and privileged information. If you are not
the
<br>
intended recipient, please contact the sender by reply e-mail and
destroy
<br>
all copies and the original message. Any unauthorized review, use,
<br>
disclosure, dissemination, forwarding, printing or copying of this
email
<br>
is strictly prohibited and appropriate legal action will be taken.
<br>
------------------------------------------------------------------------------------------------------------
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="https://lists.opencms.org/mailman/listinfo/opencms-dev">https://lists.opencms.org/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Michael Emmerich
Alkacon Software GmbH & Co. KG - The OpenCms Experts
<a class="moz-txt-link-freetext" href="http://www.alkacon.com">http://www.alkacon.com</a>
<a class="moz-txt-link-freetext" href="http://www.opencms.org">http://www.opencms.org</a>
</pre>
</body>
</html>
--------------rT47PY9poUn3HUbOodJRHm0k--
--===============4904451272976505876==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhpcyBtYWls
IGlzIHNlbnQgdG8geW91IGZyb20gdGhlIG9wZW5jbXMtZGV2IG1haWxpbmcgbGlzdApUbyBjaGFu
Z2UgeW91ciBsaXN0IG9wdGlvbnMsIG9yIHRvIHVuc3Vic2NyaWJlIGZyb20gdGhlIGxpc3QsIHBs
ZWFzZSB2aXNpdApodHRwczovL2xpc3RzLm9wZW5jbXMub3JnL21haWxtYW4vbGlzdGluZm8vb3Bl
bmNtcy1kZXYKCgoK
--===============4904451272976505876==--