web/www/contribute/index.php
2018-12-29 16:02:00 -06:00

85 lines
4.1 KiB
PHP
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?
require_once('Core.php');
?><?= Template::Header(['title' => 'Get Involved', 'highlight' => 'contribute', 'description' => 'Details on how to contribute your time and talent to the volunteer-driven Standard Ebooks project.']) ?>
<main>
<article>
<h1>Get Involved</h1>
<section id="intro">
<h2>Help create ebooks that are a pleasure to read</h2>
<p>Standard Ebooks is a volunteer driven project, and theres room for people of all skill levels to contribute.</p>
<p>At the most basic level, anyone can <a href="https://groups.google.com/forum/#!forum/standardebooks">contribute feedback via our mailing list</a>. Day-to-day readers can <a href="/contribute/report-errors">tell us about errors they spot in our ebooks</a>. People with an eye for typography and a talent for editing can proofread whole ebooks. Technically inclined readers can produce ebooks themselves, or <a href="https://github.com/standardebooks">contribute via Github</a>.</p>
</section>
<section id="everyone">
<h2>Everyone</h2>
<ul>
<li>
<p><a href="https://groups.google.com/forum/#!forum/standardebooks">Join the Standard Ebooks mailing list.</a></p>
<p>The mailing list is the best way to contact the Standard Ebooks project about any question, suggestion, concern, or contribution you might have. Were just an email away!</p>
</li>
<li>
<p><a href="/contribute/report-errors">Report a typo, formatting error, or typography error in any Standard Ebook.</a></p>
</li>
<li>
<p>Help us catalog fine art paintings from scans of old art books. We have links to complete book scans that you can browse, and we need your help to catalog the art in each book for use as cover art in future ebooks.</p>
<p>No technical experience is necessary. <a href="https://groups.google.com/forum/#!forum/standardebooks">Contact the mailing list if you want to help.</a></p>
</li>
</ul>
</section>
<section id="editors-and-readers">
<h2>Editors and readers of existing ebooks</h2>
<ul>
<li>
<p><a href="/contribute/report-errors">Report a typo, formatting error, or typography error in any Standard Ebook.</a></p>
</li>
<li>
<p><a href="/contribute/tips-for-editors-and-proofreaders">Tips for editors and proofreaders.</a></p>
</li>
<li>
<p><a href="/contribute/typography">The Standard Ebooks Typography Manual.</a></p>
</li>
</ul>
</section>
<section id="technical-contributors">
<h2>Technical contributors and producers of new ebooks</h2>
<ul>
<li>
<p><a href="/contribute/accepted-ebooks">Ebooks we do and dont accept.</a></p>
</li>
<li>
<p><a href="/contribute/wanted-ebooks">Our Wanted Ebooks list, including suggestions for first-time productions.</a></p>
</li>
<li>
<p><a href="/contribute/producers">The process of producing an ebook for Standard Ebooks.</a></p>
</li>
<li>
<p><a href="/contribute/producing-an-ebook-step-by-step">A technical step-by-step guide to producing a new ebook, from start to finish.</a></p>
</li>
<li>
<p><a href="/contribute/typography">The Standard Ebooks Typography Manual.</a></p>
</li>
<li>
<p><a href="/contribute/semantics">The Standard Ebooks XHTML Structure and Semantics Manual.</a></p>
</li>
<li>
<p><a href="/contribute/metadata">The Standard Ebooks Metadata Manual.</a></p>
</li>
<li>
<p><a href="/contribute/art">The Standard Ebooks Art Manual for cover art and titlepages.</a></p>
</li>
<li>
<p><a href="/contribute/a-basic-standard-ebooks-source-folder">Descriptions of the files in a fresh Standard Ebooks source folder.</a></p>
</li>
<li>
<p><a href="/contribute/toolset">Guidelines for contributing to the Standard Ebooks toolset.</a></p>
</li>
<li>
<p><a href="https://github.com/standardebooks">All Standard Ebooks ebook source files on Github.</a></p>
</li>
<li>
<p><a href="https://github.com/standardebooks/tools">The Standard Ebooks toolset on Github.</a></p>
</li>
</ul>
</section>
</article>
</main>
<?= Template::Footer() ?>