You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@struts.apache.org by lu...@apache.org on 2017/03/31 07:31:06 UTC
struts-site git commit: Generates proper ToC and anchors
Repository: struts-site
Updated Branches:
refs/heads/master 391ce9c60 -> 0afeb55b4
Generates proper ToC and anchors
Project: http://git-wip-us.apache.org/repos/asf/struts-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/struts-site/commit/0afeb55b
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/0afeb55b
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/0afeb55b
Branch: refs/heads/master
Commit: 0afeb55b408e5dd83a09b4a778ae8106afd5a26d
Parents: 391ce9c
Author: Lukasz Lenart <lu...@gmail.com>
Authored: Fri Mar 31 09:30:48 2017 +0200
Committer: Lukasz Lenart <lu...@gmail.com>
Committed: Fri Mar 31 09:30:48 2017 +0200
----------------------------------------------------------------------
_config.yml | 11 +++++----
source/_layouts/default.html | 6 ++---
source/announce.md | 4 +++
source/birdseye.md | 4 +++
source/builds.md | 14 +++++++----
source/bylaws.md | 51 +++++++++++++++++++++------------------
source/coding-standards.md | 8 +++++-
source/css/custom.css | 2 +-
source/helping.md | 4 +++
source/kickstart.md | 4 +++
source/primer.md | 36 +++++++++++++++------------
source/releases.md | 10 +++++---
source/submitting-patches.md | 4 +++
source/volunteers.md | 4 +++
14 files changed, 104 insertions(+), 58 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/_config.yml
----------------------------------------------------------------------
diff --git a/_config.yml b/_config.yml
index a829062..22c18ca 100644
--- a/_config.yml
+++ b/_config.yml
@@ -5,11 +5,12 @@ source: source
destination: content
encoding: UTF-8
kramdown:
- auto_ids: true
- footnote_nr: 1
- entity_output: as_char
- toc_levels: 1..6
- smart_quotes: lsquo,rsquo,ldquo,rdquo
+ auto_id_stripping: true
+ auto_ids: true
+ footnote_nr: 1
+ entity_output: as_char
+ toc_levels: 1..6
+ smart_quotes: lsquo,rsquo,ldquo,rdquo
syntax_highlighter_opts:
wrap: div
tab_width: 4
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/_layouts/default.html
----------------------------------------------------------------------
diff --git a/source/_layouts/default.html b/source/_layouts/default.html
index ecd349e..d659bcf 100644
--- a/source/_layouts/default.html
+++ b/source/_layouts/default.html
@@ -33,12 +33,12 @@
<script>
$(function() {
return $("h2, h3, h4, h5, h6").each(function(i, el) {
- var $el, icon, id;
+ var $el, id;
$el = $(el);
id = $el.attr('id');
- icon = '<i class="fa fa-link"></i>';
if (id) {
- return $el.prepend($("<a />").addClass("header-link").attr("href", "#" + id).html(icon));
+ $el.removeAttr('id');
+ return $el.before($("<a />").addClass('anchor').attr('name', id));
}
});
});
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/announce.md
----------------------------------------------------------------------
diff --git a/source/announce.md b/source/announce.md
index 5d72517..c36c5e7 100644
--- a/source/announce.md
+++ b/source/announce.md
@@ -3,6 +3,10 @@ layout: default
title: Announcements
---
# Announcements
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
<p class="pull-right">
Skip to: <a href="announce-2016.html">Announcements - 2016</a>
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/birdseye.md
----------------------------------------------------------------------
diff --git a/source/birdseye.md b/source/birdseye.md
index 3885c63..f296c43 100644
--- a/source/birdseye.md
+++ b/source/birdseye.md
@@ -4,6 +4,10 @@ title: From a birds eye
---
# From a birds eye
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
## The Apache Struts web framework
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/builds.md
----------------------------------------------------------------------
diff --git a/source/builds.md b/source/builds.md
index 3d705e2..52e432b 100644
--- a/source/builds.md
+++ b/source/builds.md
@@ -4,6 +4,10 @@ title: Source Code
---
# Source Code
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
As a convenience to developers who are helping to create and maintain the Apache Struts framework,
public access to the live source code repository is available. This is our one-and-only development repository.
@@ -30,7 +34,7 @@ With the [Git client](http://git-scm.com/) installed, obtaining a working copy o
For more about using version control systems at Apache, see the ASF's
[Source Code Repositories](http://www.apache.org/dev/#version-control) page.
-# Building Apache Struts
+## Building Apache Struts
If you are building Apache Struts from source, we recommend that you install and use
[Apache Maven 3.](http://maven.apache.org) During the build process, Maven will automatically acquire
@@ -53,7 +57,7 @@ For more about using Maven to build Struts 2, see
For more about using Maven to build Struts 1, see our [Maven wiki page.](http://wiki.apache.org/struts/StrutsMaintenanceMaven)
-# NightlyBuilds
+## NightlyBuilds
As part of our continuous integration practice, we also make available each morning the
[latest stable development build.](https://builds.apache.org/view/S-Z/view/Struts/job/Struts2-JDK6/lastStableBuild/org.apache.struts$struts2-assembly/)
@@ -66,7 +70,7 @@ If you do **not** plan to contribute to the development of the framework, then y
NOTE: The Struts 2 nightly build is not fully operational. We suggest that contributors checkout
the [source code](#SourceCode) instead.
-# Test Builds
+## Test Builds
As we prepare for a new release, the project group may create interim *test builds*. When test builds are available,
we post them [here](http://people.apache.org/builds/struts/) in binary, source and library distributions.
@@ -78,7 +82,7 @@ made the "Best Available" release. If the group feels that a build requires more
as "Beta" release. When a test build is upgraded to "Beta" or "GA" by a vote of the project members,
we make the distribution available as a formal [release.](downloads.html)
-# Maven Snapshots
+## Maven Snapshots
When a distribution is first made available, it is rated as a development build or "snapshot". Later, the quality
of the distribution may be upgraded to "Beta" or "General Availability", based on feedback from the community,
@@ -94,7 +98,7 @@ specify the ASF Snapshot repository in the project's POM.
</repositories>
-# Licensing of Apache Struts Builds
+## Licensing of Apache Struts Builds
Apache Struts 2 source code and documentation is licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file included in any distribution for additional information
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/bylaws.md
----------------------------------------------------------------------
diff --git a/source/bylaws.md b/source/bylaws.md
index a073d4b..e585892 100644
--- a/source/bylaws.md
+++ b/source/bylaws.md
@@ -3,7 +3,13 @@ layout: default
title: Project Management Committee Charter
---
-# Apache Struts PMC Charter
+# Project Management Committee Charter
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
+
+## Apache Struts PMC Charter
Struts is a Project of the [Apache Software Foundation](http://apache.org/foundation) (ASF), formed by a resolution
of the [ASF Board of Directors](http://apache.org/foundation/board/). As an ASF Project, Struts is subject to the
@@ -13,54 +19,54 @@ The Project Charter incorporates by reference the current version
of [How the ASF works](http://apache.org/foundation/how-it-works.html, with the additional guidelines
and clarifications found herein.
-# Roles and Responsibilities
+## Roles and Responsibilities
The roles and responsibilities that people can assume in the project are based on merit.
Everybody can help no matter what their role. Those who have been long term or valuable contributors to
the project can earn the right to commit directly to the source repository and to cast binding votes during
the decision-making process.
-# Users.
+## Users
Users are the people who use the products of the Project. People in this role aren't contributing code,
but they are using the products, reporting bugs, making feature requests, and such. This is by far
the most important category of people as, without users, there is no reason for the Project.
When a user starts to contribute code or documentation patches, they become a Contributor.
-# Contributors.
+## Contributors
Contributors are the people who write code or documentation patches or contribute positively to the project
in other ways. When a volunteer's patch is applied, the contribution is recognized in the version control log.
-# Committers.
+## Committers
Contributors who give frequent and valuable contributions to a subproject of the Project can have their status
promoted to that of a "*Committer*" for that subproject. A Committer has write access to the source code repository.
Committer status is granted by the Project Management Committee by majority vote.
-# Project Management Committee (PMC).
+## Project Management Committee (PMC)
Committers and other volunteers who frequently participate with valuable contributions may have their status promoted
to that of a "*Project Management Committee Member*". The PMC is responsible for the day-to-day management
of the Project.
-# Management
+### Management
The Vice President is appointed by the ASF Board. The Vice President is assisted by the Project Management Committee
(PMC) and also serves as the PMC chair. The PMC may nominate new members. Nominees may then be approved
with a 3/4 majority vote of the PMC. Membership can be revoked by a unanimous vote of all the active PMC members
other than the member in question. The list of active PMC members can be found on our [Volunteers page](volunteers.html).
-# PMC Duties
+### PMC Duties
The PMC is responsible for the day-to-day management of the Struts Project. The PMC oversees all changes
made to the codebase. The PMC must ensure that all code under a Apache Struts repository is the lawful property
of the Foundation and may be distributed under the [Apache Software License](http://apache.org/licenses/).
All releases of a Struts subproject must be sanctioned by the Project Management Committee.
-# Subprojects
+### Subprojects
Subprojects are the Project's unit of release. Each subproject should represent an implementation of a Struts framework
or a related component. Each subproject should focus on creating, maintaining, and releasing a single software
@@ -75,13 +81,13 @@ identify the initial source from which the project is to be populated, identify
repositories, if any, which are to be created. Creation of a new subproject requires approval by a 3/4 majority
vote of the PMC.
-# Decision Making
+## Decision Making
All [Volunteers](http://apache.org/foundation/how-it-works.html#roles) (Users, Developers, Committers, PMC Members)
are encouraged to participate in the decision-making process, but binding decisions are made only
by the Project Management Committee.
-# Voting
+### Voting
Any subscriber to the list may [vote](http://apache.org/foundation/voting.html) on any issue or action item.
Votes from Developers and Committers are especially welcome. However, the only binding votes are those cast by a PMC
@@ -139,7 +145,7 @@ Voting represent consensus and votes are never final. Circumstances change, and
to a +1 after discussion, and likewise a +1 may be converted to a -1. By convention, Committers should allow a vote
to circulate for 72 hours before taking action.
-# Action Items
+## Action Items
All decisions revolve around "*Action Items*". Action Items consist of the following:
- Long Term Plans
@@ -149,28 +155,28 @@ All decisions revolve around "*Action Items*". Action Items consist of the follo
- Release Plan
- Release Grade
-## Long Term Plans
+### Long Term Plans
Long term plans are simply announcements that group members are working on particular issues related to the Project.
These items are not voted on, but Committers and PMC Members who do not agree with a particular plan, or think that
an alternative plan would be better, are obligated to inform the group of their feelings.
-## Short Term Plan
+### Short Term Plan
Short term plans are announcements that a volunteer is working on a particular set of documentation or code files
with the implication that other volunteers should avoid them or try to coordinate their changes.
-## Product Changes
+### Product Changes
All product changes to the repository are subject to lazy consensus.
-## Showstoppers
+### Showstoppers
Showstoppers are issues that require a fix be in place before the next public release. They are designated as "blockers"
in the issue tracker in order to focus special attention on these problems. An issue becomes a showstopper when it is
designated as such in the issue tracker by a PMC member and remains so by lazy consensus.
-## Release Plan
+### Release Plan
A release plan must be used to keep all volunteers aware of when a release is desired, whether it will be a major,
minor, or milestone release, who will be the release manager, when the repository will be tagged to create
@@ -178,23 +184,20 @@ the distribution, and other assorted information to keep volunteers from trippin
plan must be incorporated into the product documentation, or otherwise announced to the DEV list.
Lazy majority decides each issue in a release plan.
-
-## Release Grade
+### Release Grade
After a proposed release is built, it must be tested and classified before being released to the general public.
The proposed release may be assigned "Alpha", "Beta" or "General Availability" classifications by majority vote.
Once a release is classified by the PMC Members, it may be distributed to the general public on behalf of the Foundation.
Distributions may be reclassified or withdrawn by majority vote, but the release number may not be reused by another distribution.
-
-# Sandbox
+## Sandbox
Pursuant to the ["Rules for Revolutionaries"](http://incubator.apache.org/learn/rules-for-revolutionaries.html),
any committer may submit experimental material to the Sandbox area of the repository at his or her own discretion.
-Material must be moved from the sandbox to the main repository before it can be released.
-
-If a sandbox whiteboard becomes dormant for six or more months, it may be moved to the archive section of the repository.
+Material must be moved from the sandbox to the main repository before it can be released. If a sandbox whiteboard
+becomes dormant for six or more months, it may be moved to the archive section of the repository.
Experimental material that is outside the scope of the Struts project may also be submitted to the
[Apache Labs](http://labs.apache.org/)
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/coding-standards.md
----------------------------------------------------------------------
diff --git a/source/coding-standards.md b/source/coding-standards.md
index 0e4f9d2..45c8374 100644
--- a/source/coding-standards.md
+++ b/source/coding-standards.md
@@ -3,7 +3,13 @@ layout: default
title: Coding standards
---
-# In the first place
+# Coding standards
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
+
+## In the first place
Please remember that most of the time others will read your code. Focusing on that allow you to gain required perspective
about how code should look like. Defaults, margins, convention doesn't matter if what you write is hard to read.
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/css/custom.css
----------------------------------------------------------------------
diff --git a/source/css/custom.css b/source/css/custom.css
index 5b18053..f135a81 100644
--- a/source/css/custom.css
+++ b/source/css/custom.css
@@ -1,7 +1,7 @@
.header-link {
position: absolute;
right: -1em;
- top: 0.1em;
+ top: -2em;
opacity: 0;
font-size: 0.8em;
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/helping.md
----------------------------------------------------------------------
diff --git a/source/helping.md b/source/helping.md
index e1aa2f1..806a2eb 100644
--- a/source/helping.md
+++ b/source/helping.md
@@ -4,6 +4,10 @@ title: Helping
---
# How to Help FAQ
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
- ### What can my company do to help support Apache Struts?
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/kickstart.md
----------------------------------------------------------------------
diff --git a/source/kickstart.md b/source/kickstart.md
index 9d22b36..234146e 100644
--- a/source/kickstart.md
+++ b/source/kickstart.md
@@ -4,6 +4,10 @@ title: Kickstart FAQ
---
# Kickstart FAQ
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
## General
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/primer.md
----------------------------------------------------------------------
diff --git a/source/primer.md b/source/primer.md
index a3c735b..50bf4bd 100644
--- a/source/primer.md
+++ b/source/primer.md
@@ -4,11 +4,15 @@ title: Key Technologies Primer
---
# Key Technologies Primer
+{:.no_toc}
> *"The time has come," the Walrus said, "To talk of many things:
> Of shoes -- and ships -- and sealing-wax -- Of cabbages -- and kings --
> And why the sea is boiling hot -- And whether pigs have wings."*
+* Will be replaced with the ToC, excluding a header
+{:toc}
+
## Intention
If you would like to get started with Apache Struts you most likely want
@@ -55,7 +59,7 @@ may be able to follow along and visit the other references as needed. The core
technologies used by Struts are also used by most other Java web development products, so
the background information will be useful in any Java project.
-### <a class="anchor" name="http"></a>HTTP, HTML and User Agents
+### HTTP, HTML and User Agents {#http}
The World Wide Web was built over the Hypertext Transfer Protocol
[(HTTP)](http://www.ietf.org/rfc/rfc2616.txt?number=2616)
@@ -67,7 +71,7 @@ transport more the HTML, HTML from the browser to render the view.
If you would like to learn HTML, we recommend
[Getting started with HTML](http://www.w3.org/MarkUp/Guide/) by Dave Raggett.
-### <a class="anchor" name="cycle"></a>The HTTP Request/Response cycle
+### The HTTP Request/Response cycle {#cycle}
A very important part of HTTP for the web developer is the request/response cycle. To use HTTP
you have to make a request. A HTTP server, like a web server, is then obliged to respond. When you
@@ -79,7 +83,7 @@ If you are not familiar with the HTTP request/response you should learn about it
There is a lot of help available in the internet, like
[How does the Internet work?](http://docs.webplatform.org/wiki/tutorials/How_does_the_Internet_work)
-### <a class="anchor" name="java"></a>The Java Language and Application Frameworks
+### The Java Language and Application Frameworks
Struts is written in the
[Java programming language](http://www.oracle.com/us/technologies/java/overview/index.html).
@@ -88,7 +92,7 @@ object-orientated techniques. A good understanding of Java, and especially
object-orientated programming (OOP) and threading, will help
you get the most out of Struts.
-#### <a class="anchor" name="reflection"></a>Reflection and Introspection
+#### Reflection and Introspection {#reflection}
Reflection is the process of determining which member fields and methods are available on an object.
Introspection is a specialized form of reflection used by the JavaBean API.
@@ -102,7 +106,7 @@ between HTML forms and JavaBeans.
While it is not necessary to have a deep understanding of these concepts when you start with Apache
Struts, it will help you when your application grows and becomes more complex.
-#### <a class="anchor" name="resources"></a>Properties Files and ResourceBundles
+#### Properties Files and ResourceBundles {#resources}
Java applications, including web applications, are often
configured using [Properties](http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html)
@@ -120,14 +124,14 @@ Support for localizing an application was built into the framework from the grou
Again the Java Tutorials provide
[more information](http://docs.oracle.com/javase/tutorial/i18n/resbundle/concept.html).
-#### <a class="anchor" name="threads"></a>Threads
+#### Threads {#threads}
With Struts 1 you were required to know a lot about how to write code which
can run in a multi-threaded environment. With Struts 2 this is no longer necessary.
In an Struts 2 environment each action caused by a HTTP request
is a plain old Java object which is instanced for each request.
-### <a class="anchor" name="javascript"></a>JavaScript, AJAX, and SOAP
+### JavaScript, AJAX, and SOAP {#javascript}
WIth HTTP and HTML you can already provide static web pages. Today this is much
often not longer enough and your application users might expect a interactive user interface.
@@ -149,7 +153,7 @@ requests directly to a remote server, while still retaining a separation of conc
the business logic and the page markup. Depending on your applications need, it might be not necessary
for you to learn about SOAP.
-### <a class="anchor" name="containers"></a>Servlets, Filters, and Web Containers
+### Servlets, Filters, and Web Containers {#containers}
Since Java is an object-orientated language, the
[Java Servlet](http://docs.oracle.com/javaee/6/tutorial/doc/bnafd.html)
@@ -180,7 +184,7 @@ response. Filters are aggregated into a chain in which each filter
has a chance to process the request and response before and after
it is processed by subsequent filters (and the servlet that is ultimately called).
-### <a class="anchor" name="session"></a>Sessions
+### Sessions #{session}
One of the key characteristics of HTTP is that it is
*stateless*. In other words, there is nothing built in to
@@ -211,7 +215,7 @@ bypass this.
Struts 2 provides easy ways to create and access a session.
-### <a class="anchor" name="webapp"></a>Web Applications
+### Web Applications {#webapp}
Just as a HTTP server can be used to host several distinct
websites, a servlet container can be used to host more than one web
@@ -229,7 +233,7 @@ application and deploy it to your server. This might require knowledge of
build tools like [Maven](http://maven.apache.org) and addition reading
in the documentation of your server vendor.
-### <a class="anchor" name="security"></a>Security
+### Security {#security}
One detail that can be configured in the Web application deployment descriptor is container-managed security.
Declarative security can be used to protect requests for URIs that match given patterns.
@@ -243,7 +247,7 @@ Other projects, like [Apache Shiro](http://shiro.apache.org/) or
[Spring Security](http://www.springframework.org/spring-security/) might also help
you to secure your web application.
-### <a class="anchor" name="jsp"></a>JavaServer Pages, JSP Tag Libraries, and JavaServer Faces
+### JavaServer Pages, JSP Tag Libraries, and JavaServer Faces {#jsp}
If you write a classic web app, you might need a view component.
One of the first of its kind was [JSP](http://www.oracle.com/technetwork/java/javaee/jsp/index.html).
@@ -275,7 +279,7 @@ presentation technologies available to Struts:
- [Velocity](http://velocity.apache.org/)
- [XSLT](http://www.w3.org/TR/xslt)
-### <a class="anchor" name="xml"></a>Extensible Markup Language (XML)
+### Extensible Markup Language (XML) {#xml}
The features provided by the framework rely on a number of
objects that are sometimes deployed using a configuration file written in
@@ -288,7 +292,7 @@ it is no longer crucial to write long XML documents to create a Struts
application. If you would like to read more about it, please visit the page of the
[Convention plugin](http://struts.apache.org/release/2.1.x/docs/convention-plugin.html).
-### <a class="anchor" name="mvc"></a>Model View Controller (MVC)
+### Model View Controller (MVC) {#mvc}
Web applications based on JavaServer Pages sometimes
commingle database code, page design code, and control flow
@@ -340,7 +344,7 @@ For more about MVC, see
- [Smalltalk MVC framework](http://st-www.cs.uiuc.edu/users/smarch/st-docs/mvc.html).
- [Wikipedia - MVC](http://en.wikipedia.org/wiki/Model_view_controller)
-## <a class="anchor" name="logic_frameworks"></a>Business Logic Frameworks
+## Business Logic Frameworks {#logic-frameworks}
Most teams still roll their own business logic layer using
plain old JavaBeans (POJOs). Though, business layer frameworks are beginning to emerge,
@@ -351,7 +355,7 @@ and now include:
- [Commons Chain of Responsiblity](http://commons.apache.org/chain/)
- or you can rely on features of the bundled Struts XWork
-### <a class="anchor" name="data_frameworks"></a>Data Access Frameworks
+## Data Access Frameworks {#data-frameworks}
Most often, the business layer is seen to be distinct from
the data access layer. Some teams roll their own data access objects (DAOs),
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/releases.md
----------------------------------------------------------------------
diff --git a/source/releases.md b/source/releases.md
index f934d2f..80757ed 100644
--- a/source/releases.md
+++ b/source/releases.md
@@ -4,12 +4,16 @@ title: Release Guidelines
---
# Release Guidelines
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
This document describes the Apache Struts release process and our [coding conventions](#Coding),
which are applicable to all subprojects. Both stable and development releases are
[available for download.](downloads.html)
-# Release Process
+## Release Process
A [point release](http://commons.apache.org/releases/versioning.html) should be made before and after
any product change that is not a "fully-compatible change" (see link). This includes moving a dependency from
@@ -63,13 +67,13 @@ Additional remarks:
- If a serious flaw if found in a test build or release, it may be withdrawn by a majority vote of the PMC and
removed from ASF distribution channels.
-# Coding Conventions and Guidelines
+## Coding Conventions and Guidelines
Source code and documentation contributed to the Struts repositories should observe the:
- The ["Code Conventions for the Java Programming Language"](http://www.oracle.com/technetwork/java/codeconvtoc-136057.html),
as published by Oracle.
-# Clarifications
+## Clarifications
- First, "Observe the style of the original". Resist the temptation to make stylistic changes for their own
sake. But, if you must reformat code, commit style changes separately from code changes. Either change
the style, commit, and then change the code, or vice-versa.
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/submitting-patches.md
----------------------------------------------------------------------
diff --git a/source/submitting-patches.md b/source/submitting-patches.md
index 730c702..09510bd 100644
--- a/source/submitting-patches.md
+++ b/source/submitting-patches.md
@@ -4,6 +4,10 @@ title: Submitting patches
---
# Submitting patches
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
## Committers
http://git-wip-us.apache.org/repos/asf/struts-site/blob/0afeb55b/source/volunteers.md
----------------------------------------------------------------------
diff --git a/source/volunteers.md b/source/volunteers.md
index a30b4ee..734084c 100644
--- a/source/volunteers.md
+++ b/source/volunteers.md
@@ -4,6 +4,10 @@ title: Volunteers
---
# Volunteers
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
The project consists of a diverse group of volunteers who share common values regarding collaborative,
community-based open source development.