Modified: struts/site/trunk/content/xdoc/index.xml
URL: 
http://svn.apache.org/viewvc/struts/site/trunk/content/xdoc/index.xml?rev=1521447&r1=1521446&r2=1521447&view=diff
==============================================================================
--- struts/site/trunk/content/xdoc/index.xml (original)
+++ struts/site/trunk/content/xdoc/index.xml Tue Sep 10 12:00:15 2013
@@ -18,9 +18,8 @@ limitations under the License.
 // ======================================================================== 78
 -->
 <document>
-
     <properties>
-        <title>Welcome</title>
+        <title>Welcome to the Apache Struts project</title>
     </properties>
 
     <head>
@@ -28,27 +27,41 @@ limitations under the License.
     </head>
 
     <body>
-
         <div class="hero-unit">
-            <h1>Apache Struts 2.3.15.1 GA</h1>
+            <h1>Apache Struts</h1>
             <p>
-                Released on 16 July 2013.
-                The <a 
href="http://struts.apache.org/release/2.3.x/docs/version-notes-23151.html";>version
 notes</a>
-                are available online. Scroll down for more about <a 
href="#Welcome">Apache Struts</a>,
-                the <a href="#Project">Apache Struts project</a>, and <a 
href="#Newbies">Struts for Newbies</a>
+                The Apache Struts web framework is a free open-source solution 
for creating
+                elegant and modern Java web applications. While the 
predecessor Struts 1
+                used a lot of XML in old times, Struts 2 applications can be 
configured
+                by "Convention". Struts 2 applications support the MVC 
pattern, allow a
+                REST-like approach and enables you to create full-featured 
AJAX applications.
             </p>
-            <a href="http://struts.apache.org/download.cgi#struts23151"; 
class="btn btn-primary">Download</a>
-            <a href="primer.html" class="btn btn-info">Read more</a>
-                
-            <h1>Apache Struts 1 End-Of-Life (EOL)</h1>
-            <p>
-                The Apache Struts Project Team would like to inform you that 
the Struts 1.x web framework
-                has reached its end of life and is no longer officially 
supported.
-            </p>
-            <a href="struts1eol-announcement.html" class="btn btn-info">Read 
more</a>
-            <a href="struts1eol-press.html" class="btn btn-info">Press 
release</a>
+            <a href="http://struts.apache.org/download.cgi#struts23151"; 
class="btn btn-primary btn-large">Download</a>
+            <a href="primer.html" class="btn btn-info btn-large">Technology 
Primer</a>
         </div>
 
+        <table class="showcase">
+            <tr>
+                <td width="33%">
+                    <h2>Struts 2.3.15.1 GA</h2>
+                    Apache Struts 2.3.15.1 GA has been released on 16 July 
2013.
+                    <a 
href="http://struts.apache.org/release/2.3.x/docs/version-notes-23151.html";>Version
 notes</a>
+                </td>
+                <td width="33%">
+                    <h2>Want to help?</h2>
+                    We welcome your help! If you want to more about how to 
build
+                    and patch the Struts 2 codebase, please read the <a 
href="#">Developer Docs</a>
+                </td>
+                <td width="33%">
+                    <h2>Apache Struts 1</h2>
+                    <strong>End-Of-Life (EOL)</strong><br/>
+                    The Struts 1.x web framework has reached its end of life 
and is no longer officially supported.
+                    <a href="struts1eol-announcement.html">Read the 
announcment</a> or the official <a href="struts1eol-press.html">Press 
release</a>
+                </td>
+            </tr>
+
+        </table>
+
         <div class="row">
             <div class="pull-left">
                <div>Official IRC channel: <a 
href="irc://irc.freenode.net/struts">#struts</a></div>
@@ -64,183 +77,5 @@ limitations under the License.
                 <a href="https://twitter.com/TheApacheStruts"; 
class="twitter-follow-button" data-show-count="false">Follow 
@TheApacheStruts</a>
             </div>
         </div>
-        
-        <div class="row">
-            <div class="span12">
-                <h2>The Apache Struts web framework</h2>
-                <a name="Welcome"/>
-                <p>
-                    The Apache Struts web framework is a free open-source 
solution for creating
-                    Java web applications.
-                </p>
-                
-                <p>
-                    Web applications differ from conventional websites in that
-                    web applications can create a dynamic response.
-                    Many websites deliver only static pages.
-                    A web application can interact with databases and
-                    business logic engines to customize a response.
-                </p>
-                
-                <p>
-                    Web applications based on JavaServer Pages sometimes
-                    commingle database code, page design code, and control
-                    flow code.
-                    In practice, we find that unless these concerns are
-                    separated,
-                    larger applications become difficult to maintain.
-                </p>
-                
-                <p>
-                    One way to separate concerns in a software application is 
to
-                    use a Model-View-Controller (MVC) architecture.
-                    The <em>Model</em> represents the business or database 
code,
-                    the <em>View</em> represents the page design code,
-                    and the <em>Controller</em> represents the navigational 
code.
-                    The Struts framework is designed to help developers create
-                    web applications that utilize a MVC architecture.
-                </p>
-                
-                <p>
-                    The framework provides three key components:
-                </p>
-                
-                <ul>
-                    <li>
-                        A "request" handler provided by the application 
developer
-                        that is mapped to a standard URI.
-                    </li>
-                    <li>
-                        A "response" handler that transfers control to another 
resource
-                        which completes the response.
-                    </li>
-                    <li>
-                        A tag library that helps developers create interactive
-                        form-based applications with server pages.
-                    </li>
-                </ul>
-                
-                <p>
-                    The framework's architecture and tags are buzzword 
compliant.
-                    Struts works well with conventional REST applications
-                    and with nouveau technologies like SOAP and AJAX.
-                </p>
-                
-                <hr/>
-        
-                <a name="Project"/>        
-                <h2>The Apache Struts Project</h2>
-                <p>
-                    The Apache Struts Project is the open source community
-                    that creates and maintains the Apache Struts framework.
-                    The project consists of a diverse group of volunteers who
-                    share common values regarding collaborative, 
community-based
-                    open source development.
-                    The Apache Struts Project is proud to share these values 
with
-                    our parent organization: The Apache Software Foundation.
-                </p>
-                
-                <p>
-                    The project is called "Struts" because the framework is 
meant to
-                    furnish the "invisible underpinnings" that support 
professional
-                    application development.
-                    Struts provides the glue that joins the various elements
-                    of the standard Java platform into a coherent whole.
-                    Our goal is to leverage existing standards by producing the
-                    missing pieces we need to create enterprise-grade 
applications
-                    that are easy to maintain over time.
-                </p>
-                
-                <p>
-                    The Apache Struts Project offers two major versions of the
-                    Struts framework.
-                    Struts 1 is recognized as
-                    <em>the</em> most popular web application framework for 
Java.
-                    The 1.x framework is mature, well-documented, and widely
-                    supported.
-                    Struts 1 is the best choice for teams who value proven
-                    solutions to common problems.
-                </p>
-                
-                <p>
-                    Struts 2 was originally known as
-                    <a href="http://www.opensymphony.com/webwork";>WebWork 
2</a>.
-                    After working independently for several years,
-                    the WebWork and Struts communities
-                    <a href="announce-2005.html#a20051214.3">joined forces</a>
-                    to create Struts 2.
-                    The 2.x framework is the best choice for teams who value
-                    elegant solutions to difficult problems.
-                </p>
-                
-                <hr/>
-
-                <a name="Newbies"/>
-                <h2>Struts for Newbies</h2>
-                <p>
-                    If you are new to development with Struts,
-                    here are some pointers on how to get started.
-                </p>
-                
-                <p>
-                    The framework "stands on the shoulders of giants".
-                    To use Struts well, it's important to have a good grasp of 
the
-                    fundamentals.
-                    Start by reviewing the
-                    <a href="http://struts.apache.org/primer.html";>Key 
Technologies primer</a>,
-                    and studying any unfamiliar topics.
-                </p>
-                
-                <p>
-                    Next, branch to either the
-                    <a href="http://struts.apache.org/2.x/index.html";>Struts 
2</a> or
-                    <a href="http://struts.apache.org/1.x/index.html";>Struts 
1</a>
-                    documentation
-                </p>
-                
-                <p>
-                    The Struts 2 documentation is maintained as a wiki, but 
don't let that
-                    stop you from scrolling through. We have organized the 
wiki so that
-                    it can be read like a book, cover to cover. Just keep 
following the
-                    Next links.
-                </p>
-                
-                <p>
-                    <a href="http://www.infoq.com/minibooks/starting-struts2";>
-                        <img 
src="http://www.infoq.com/resource/minibooks/starting-struts2/en/cover/StartingStruts2online250x355.JPG";
 alt="Starting Struts 2" hspace="16" align="left" style="height: 160px;"/></a>
-                    Better yet, turn first to the
-                    <a href="http://www.infoq.com/minibooks/starting-struts2";>
-                        Starting with Struts2</a> book.
-                    At 122 pages, it's a small book that doesn't try to 
replicate the
-                    online Struts 2 Documentation. Instead, the book is a 
perfect complement
-                    to the Struts 2 website. The "minibook" is available both 
as a free PDF
-                    and in conventional printed form.
-                </p>
-                
-                <p>
-                    For Struts 1, the most up-to-date book would be
-                    <a href="http://www.jamesholmes.com/StrutsTCR/";>Struts: 
The Complete Reference</a>.
-                    For newbies, <a 
href="http://www.dummies.com/store/product/Jakarta-Struts-For-Dummies.productCd-0764559575.html";>Struts
 for Dummies</a>
-                    is another good choice.
-                </p>
-                
-                <p>
-                    And don't hesitate to
-                    <a href="http://struts.apache.org/helping.html";>get 
involved</a>.
-                    The best way to help with any open source project is to 
improve the
-                    documentation!
-                    There are mountains of Struts know-how posted to the
-                    <a href="http://struts.apache.org/mail.html";>user mailing 
list</a>
-                    that could be sholved into the documentation.
-                    (How do you think this section started?)
-                </p>
-                
-                <p>
-                    <div class="right">
-                        <b>Next:</b> <a href="downloads.html" class="btn 
btn-primary">Download</a>
-                    </div>
-                </p>
-            </div>
-        </div>       
     </body>
 </document>

Modified: struts/site/trunk/content/xdoc/mail.xml
URL: 
http://svn.apache.org/viewvc/struts/site/trunk/content/xdoc/mail.xml?rev=1521447&r1=1521446&r2=1521447&view=diff
==============================================================================
--- struts/site/trunk/content/xdoc/mail.xml (original)
+++ struts/site/trunk/content/xdoc/mail.xml Tue Sep 10 12:00:15 2013
@@ -23,194 +23,158 @@ limitations under the License.
     </properties>
 
     <body>
-
         <section name="Mailing Lists">
-
             <p>
                 A mailing list is an electronic discussion forum that anyone
-                can
-                subscribe to. When someone sends an email message to the
-                mailing list,
-                a copy of that message is broadcast to everyone who is
-                subscribed to
-                that mailing list. Mailing lists are the primary means of
-                communication
-                for people working within the Apache Struts Project.
+                can subscribe to. When someone sends an email message to the
+                mailing list, a copy of that message is broadcast to everyone 
who is
+                subscribed to that mailing list. Mailing lists are the primary 
means of
+                communication for people working within the Apache Struts 
Project.
             </p>
 
-            <subsection name="Guidelines">
+            <p class="alert alert-block alert-error">
+                <strong>HEADS UP!</strong><br/>
+
+                A message sent to a public mailing list
+                cannot be unpublished. Although we might be able to modify our 
own
+                mail archives, the message is mirrored to a lot of other 
archiving
+                systems which we do not have under control. Therefore
+                almost 100% of all delete requests are denied. Please make
+                sure you <strong>do not send any potential sensitive 
information to the mailing list</strong>,
+                including passwords, server names, ips and so on.
+            </p>
+
+            <subsection name="Subscribing">
 
+                <table>
+                    <tr>
+                        <th>Name</th>
+                        <th>Subscribe</th>
+                        <th>Unsubscribe</th>
+                        <th>Description</th>
+                    </tr>
+
+                    <tr>
+                        <td>Struts-Announcements</td>
+                        <td><a 
href="mailto:announcements-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>announcements-subscr...@struts.apache.org</a></td>
+                        <td><a 
href="mailto:announcements-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>announcements-unsubscr...@struts.apache.org</a></td>
+                        <td>Major Announcements, low-volume, read only</td>
+                    </tr>
+
+                    <tr>
+                        <td>Struts-User</td>
+                        <td><a 
href="mailto:user-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>user-subscr...@struts.apache.org</a></td>
+                        <td> <a 
href="mailto:user-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>user-unsubscr...@struts.apache.org</a></td>
+                        <td>Contact to other Struts-users and ask questions on 
installation or features</td>
+                    </tr>
+
+                    <tr>
+                        <td>Users Digest</td>
+                        <td><a 
href="mailto:user-digest-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>user-digest-subscr...@struts.apache.org</a></td>
+                        <td><a 
href="mailto:user-digest-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>user-digest-unsubscr...@struts.apache.org</a></td>
+                        <td>Get a daily digest of the Struts Users list</td>
+                    </tr>
+                </table>
+
+                <a name="Archives"/>
+                <p>
+                    You can read the <a 
href="http://mail-archives.apache.org/mod_mbox/struts-user/";>ASF Mail </a>
+                    or the <a 
href="http://markmail.org/list/org.apache.struts.users/";>Mark Mail</a> Archives 
if you
+                    are looking for older discussions. There are many other 
archives out there as well.
+                </p>
+
+                <p class="alert alert-success">
+                    If you want to <strong>discuss patches or contribute to 
Struts</strong> you should
+                    subscribe to the <a href="dev/dev-mail.html">developers 
list</a>.
+                </p>
+            </subsection>
+
+            <subsection name="Guidelines">
                 <p>
                     Mailing lists provide a simple and effective communication
-                    mechanism.
-                    With potentially thousands of subscribers, there is a
-                    common set of
-                    etiquette guidelines that you should observe. Please keep
+                    mechanism. With potentially thousands of subscribers, 
there is a
+                    common set of etiquette guidelines that you should 
observe. Please keep
                     on reading.
                 </p>
 
-                <p>
+                <p class="alert alert-box alert-error">
                     <strong>
                         Join the lists that are appropriate for your
                         discussion.
                     </strong>
                     <br/>
                     Please make sure that you are joining the list that is
-                    appropriate for the
-                    topic or product that you would like to discuss. For
-                    example,
-                    please do not join the Struts mailing list and ask
-                    questions about Tomcat.
-                    Instead, you should join the Tomcat User list and ask your
-                    questions
-                    there.
-                </p>
-                <p>
-                    <strong>
-                        <a name="respect">Respect the mailing list type</a>
-                    </strong>
-                </p>
-
-                <ul>
-                    <li>
-                        The "User" list is where you can send questions and
-                        comments about
-                        configuration, setup, usage and other "user" types of
-                        questions.
-                    </li>
-                    <li>
-                        The "Developer" (or "Dev") list is where you can send
-                        questions and
-                        comments about the actual software source code and
-                        general
-                        "development" types of questions.
-                        Questions about the "future" of Struts are
-                        best addressed to the dev list.
-                    </li>
-                </ul>
-
-                <p>Some questions may seem appropriate for posting on both the
-                    "user" and
-                    the "developer" lists.
-                    In this case, pick one and only one.
-                    Do not cross post, unless a Committer asks that the
-                    thread be moved to the other list.
+                    appropriate for the topic or product that you would like 
to discuss. For
+                    example, please do not join the Struts mailing list and ask
+                    questions about Tomcat. Instead, you should join the 
Tomcat User list and ask your
+                    questions there.
                 </p>
 
-                <p>Asking a configuration question on the developers list is
-                    discouraged because the time of our developers is as
-                    precious as yours.
-                    By contacting the developers directly instead of the user
-                    base you are abusing resources.
-                    In fact, it is unlikely that you will get a quicker answer,
-                    if any answer at all
-                </p>
+                <h3><a name="respect">Respect the mailing list type</a></h3>
 
                 <p>
-                    Conversely, a question about the future of Struts
-                    or the operation of the Struts project is best posted to 
the
-                    dev list.
+                    The "User" list is where you can send questions and 
comments about
+                    configuration, setup, usage and other "user" types of 
questions.
                     The focus of the user list should be one "how" to do
                     something with the framework we have today.
                     The focus of the dev list is how we want to do something
                     with a future version of the framework.
                 </p>
+
                 <p>
-                    If you would like to discuss a topic outside the usual 
scope of our mailing lists,
-                    please create a
-                    <a href="http://quicktopic.com/";>
-                        <strong>QuickTopic</strong>
-                    </a>
-                    and invite others to join the conversation.
+                    The "Developer" (or "Dev") list is where you can send 
questions and
+                    comments about the actual software source code and general
+                    "development" types of questions. Questions about the 
"future" of Struts are
+                    best addressed to the dev list.
                 </p>
 
                 <p>
-                    <strong>
-                        <a name="post">Do not cross post messages.</a>
-                    </strong>
-                    <br/>
+                    Some questions may seem appropriate for posting on both the
+                    "user" and the "developer" lists. In this case, pick one 
and only one.
+                    Do not cross post, unless a Committer asks that the
+                    thread be moved to the other list.
+                </p>
+
+                <h3><a name="post">Do not cross post messages.</a></h3>
+                <p>
                     In other words, pick a mailing list and send your messages
-                    to that mailing
-                    list only. Do not send your messages to multiple mailing
-                    lists. The reason is
-                    that people may be subscribed to one list and not to the
-                    other. Therefore,
-                    some people will only see part of the conversation.
+                    to that mailing list only. Do not send your messages to 
multiple mailing
+                    lists. The reason is that people may be subscribed to one 
list and not to the
+                    other. Therefore, some people will only see part of the 
conversation.
                 </p>
 
+                <h3><a name="reply-to">Watch where you are sending 
email.</a></h3>
                 <p>
-                    <strong>
-                        <a name="reply-to">Watch where you are sending 
email.</a>
-                    </strong>
                     The majority of our mailing lists have set the Reply-To to
-                    go back to the
-                    list. That means that when you Reply to a message, it will
-                    go to the list
-                    and not to the original author directly. The reason is
-                    because it helps
-                    facilitate discussion on the list for everyone to benefit
-                    from. Be careful
-                    of this as sometimes you may intend to reply to a message
-                    directly to someone
-                    instead of the entire list.
-                    The appropriate contents of the Reply-To header is an
-                    age-old debate that
-                    should not be brought up on the mailing lists. You can
-                    examine opposing points of view
-                    <a href="http://www.unicom.com/pw/reply-to-harmful.html";>
-                        condemning</a>
-                    our convention and
-                    <a 
href="http://marc.merlins.org/netrants/reply-to-useful.html";>
-                        condoning</a>
-                    it. Bringing this up for debate on a mailing list will add
-                    nothing
-                    new and is considered off-topic.
+                    go back to the list. That means that when you Reply to a 
message, it will
+                    go to the list and not to the original author directly. 
The reason is
+                    because it helps facilitate discussion on the list for 
everyone to benefit
+                    from. Be careful of this as sometimes you may intend to 
reply to a message
+                    directly to someone instead of the entire list.
                 </p>
 
+                <h3><a name="plain">Do not send HTML emails to the 
list.</a></h3>
                 <p>
-                    <strong>
-                        <a name="plain">Do your best to ensure that you are 
not sending HTML
-                            or "Stylelized" email to the list.</a>
-                    </strong>
-                    <br/>
                     If you are using Outlook or Outlook Express or Eudora,
-                    chances are that
-                    you are sending HTML email by default. There is usually a
-                    setting that
-                    will allow you to send "Plain Text" email. If you are
-                    using Microsoft
-                    products to send email, there are several bugs in the
-                    software that
-                    prevent you from turning off the sending of HTML email.
+                    chances are that you are sending HTML email by default. 
There is usually a
+                    setting that will allow you to send "Plain Text" email.
                 </p>
 
+                <h3><a name="short">Keep your email short and to the 
point.</a></h3>
                 <p>
-                    <strong>
-                        <a name="short">Keep your email short and to the 
point.</a>
-                    </strong>
-                    <br/>
                     If your email is more than about a page of text, chances
-                    are that it
-                    won't get read by very many people. It is much better to
-                    try to pack a
-                    lot of informative information (see above about asking
-                    smart questions)
-                    into as small of an email as possible. If you are replying
-                    to a previous
-                    email, it is a good idea to only quote the parts that you
-                    are replying
-                    to and to remove the unnecessary bits. This makes it
-                    easier for people
-                    to follow a thread as well as making the email archives
-                    easier to search
-                    and read.
+                    are that it won't get read by very many people. It is much 
better to
+                    try to pack a lot of informative information (see above 
about asking
+                    smart questions) into as small of an email as possible. If 
you are replying
+                    to a previous email, it is a good idea to only quote the 
parts that you
+                    are replying to and to remove the unnecessary bits. This 
makes it
+                    easier for people to follow a thread as well as making the 
email archives
+                    easier to search and read.
                 </p>
 
-                <p>
-                    <strong>
-                        <a name="trolls">Don't feed the trolls.</a>
-                    </strong>
-                </p>
+
+                <h3><a name="trolls">Don't feed the trolls.</a></h3>
+
                 <blockquote>
                     <p>
                         "In Internet terminology, a troll is a person who 
posts rude or offensive messages on the
@@ -236,164 +200,21 @@ limitations under the License.
                     but troll spam is a hard for software to spot.
                     The best defense is to withhold from the troll what he or 
she wants most: A response.
                 </p>
+
+                <h3><a name="smart">Ask smart questions.</a></h3>
                 <p>
-                    <strong>
-                        <a name="smart">Ask smart questions.</a>
-                    </strong>
-                    <br/>
                     Every volunteer project obtains its strength from the
-                    people involved
-                    in it. You are welcome to join any of our mailing lists.
-                    You can
-                    choose to lurk, or actively participate; it's up to you.
-                    The level of
-                    community responsiveness to specific questions is
-                    generally directly
-                    proportional to the amount of effort you spend formulating
-                    your
-                    question. Eric Raymond and Rick Moen have even written an
+                    people involved in it. You are welcome to join any of our 
mailing lists.
+                    You can choose to lurk, or actively participate; it's up 
to you.
+                    The level of community responsiveness to specific 
questions is
+                    generally directly proportional to the amount of effort 
you spend formulating
+                    your question. Eric Raymond and Rick Moen have even 
written an
                     essay entitled
-                    <a
-                            
href="http://www.catb.org/~esr/faqs/smart-questions.html";>
-                        <strong>"Asking
-                            Smart Questions"</strong>
-                    </a>
+                    <a 
href="http://www.catb.org/~esr/faqs/smart-questions.html";>&quot;Asking Smart 
Questions&quot;</a>
                     precisely on this topic. Please read the essay, follow its 
advice,
-                    and then post your smart questions to the appropriate list
-                    (not to Eric and Rick!).
+                    and then post your smart questions to the appropriate list.
                 </p>
             </subsection>
-
-            <a name="Archives"/>
-            <subsection name="Archives">
-                <p>Archives Carrying Struts User List</p>
-                <ul>
-                    <li>
-                        <a 
href="http://mail-archives.apache.org/mod_mbox/struts-user/";>
-                          ASF Mail Archives</a>
-                    </li>
-                    <li>
-                        <a 
href="http://markmail.org/list/org.apache.struts.users/";>
-                            Mark Mail</a>
-                    </li>
-                    <li>
-                        <a 
href="http://www.mail-archive.com/user%40struts.apache.org/";>
-                            Mail-Archive</a>
-                    </li>
-                    <li>
-                        <a 
href="http://news.gmane.org/gmane.comp.jakarta.struts.user/";>
-                            Gmane</a>
-                    </li>
-                    <li>
-                        <a 
href="http://marc.theaimsgroup.com/?l=struts-user&amp;r=1&amp;w=2";>
-                            Mailing list ARChives</a>
-                    </li>
-                    <li>
-                        <a 
href="http://www.nabble.com/Struts---User-f206.html";>
-                            Nabble</a>
-                    </li>
-                </ul>
-            </subsection>
-
-            <subsection name="Subscribing">
-                <p>
-                    Now that you've read the guidelines (you
-                    <em>have</em>
-                    read the rest of the page, haven't you?), please subscribe
-                    to whichever Struts lists are of interest.
-                </p>
-
-                <ul>
-
-                    <li>
-                        <strong>STRUTS-ANNOUNCEMENTS Mailing List</strong>
-                        - Subscribe to this list
-                        to receiving only major announcements regarding
-                        Struts. This is a low-volume,
-                        read-only list.
-                        <br/>
-                        [
-                        <a 
href="mailto:announcements-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>
-                            Subscribe</a>
-                        ]
-                        <br/>
-                        [
-                        <a 
href="mailto:announcements-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>
-                            Unsubscribe</a>
-                        ]
-                    </li>
-
-                    <li>
-                        <strong>STRUTS-USER Mailing List</strong>
-                        - Subscribe to this list
-                        to communicate with other developers that are using
-                        Struts for their own applications, including questions
-                        about the
-                        installation of Struts, and the usage of particular
-                        Struts features.
-                        <br/>
-                        [
-                        <a 
href="mailto:user-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>
-                            Subscribe</a>
-                        ]
-                        <br/>
-                        [
-                        <a 
href="mailto:user-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>
-                            Unsubscribe</a>
-                        ]
-                    </li>
-                    <li>
-                        <strong>STRUTS-USER Digest</strong>
-                        - Subscribe to this list to receive
-                        a daily digest of the Struts USER list.
-                        <br/>
-                        [
-                        <a 
href="mailto:user-digest-subscr...@struts.apache.org?subject=subscribe&amp;body=subscribe";>
-                            Subscribe</a>
-                        ]
-                        <br/>
-                        [
-                        <a 
href="mailto:user-digest-unsubscr...@struts.apache.org?subject=unsubscribe&amp;body=unsubscribe";>
-                            Unsubscribe</a>
-                        ]
-                        <br/>
-                        If you subscribe to the Digest, you can also post to
-                        the User list.
-                        (Just don't quote the entire Digest mailing in a
-                        reply!)
-                    </li>
-                </ul>
-
-                <p>
-                    <em>To subscribe to the Dev list,
-                    please visit the <a href="dev/dev-mail.html">
-                    product development</a> area.</em>
-                </p>
-
-                <p>
-                    Please note that the Struts User list enjoys a "casual
-                    friday" policy.
-                    More off-topic messages are tolerated on Fridays so long
-                    as the
-                    message is prefixed with the token [FRIDAY].
-                    If you'd rather not be troubled by these postings, please
-                    set your
-                    mail filter accordingly.
-                    Posting [FRIDAY] articles on any other weekday is
-                    <strong>strongly
-                        discouraged.</strong>
-                    We thank you for your cooperation.
-                </p>
-
-            </subsection>
         </section>
-
-        <section>
-            <p class="right">
-                <strong>Next:</strong>
-                <a href="helping.html">How to Help FAQ</a>
-            </p>
-        </section>
-
     </body>
 </document>


Reply via email to