Index: en_US.ISO8859-1/htdocs/news/status/report-sample.md
===================================================================
--- /dev/null
+++ en_US.ISO8859-1/htdocs/news/status/report-sample.md
@@ -0,0 +1,30 @@
+## Status Report Sample - This Will Become The Title ##
+
+Contact: John Smith, <email@example.org>
+
+Link:	 [Link description here](http://www.example.com/project/url)
+
+Paragraphs are separated with an empty line.  Use Markdown
+syntax, the same as you use on GitHub.  If you don't know
+Markdown, just write it as if it was plain text.
+
+Introduce your work.  Do not assume that the person reading
+the report knows about your project.
+
+Show the importance of your work.  Status reports are not
+just about telling everyone that things were done, they also
+need to explain why they were done.
+
+What has happened since the last report?  Let us know what
+is new in this area.
+
+Optionally include the information about the sponsor.
+
+If help is needed, make this explicit.  List tasks, with enough
+detail that people know if they are likely to be able to do them,
+and invite people to get in contact:
+
+  * First task
+  * Second task
+  * Third, if any
+
Index: en_US.ISO8859-1/htdocs/news/status/status.xml
===================================================================
--- en_US.ISO8859-1/htdocs/news/status/status.xml
+++ en_US.ISO8859-1/htdocs/news/status/status.xml
@@ -19,7 +19,8 @@
   <p>Submit your entries as Pull Requests from your fork of
     <a href="https://github.com/freebsd/freebsd-quarterly">FreeBSD
     Quarterly Status Reports GitHub repo</a> or submit them via e-mail to
-    <a href="mailto:quarterly@FreeBSD.org">quarterly@FreeBSD.org</a>.</p>
+    <a href="mailto:quarterly@FreeBSD.org">quarterly@FreeBSD.org</a>,
+    using the <a href="report-sample.md">Markdown template</a>.</p>
   <hr/>
 
   <p>One of the benefits of the FreeBSD development model is a focus on