Changes

Use H2 for main Major section headings, H3 for sub-sections, H4 if you need a lower level. H2 are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. H3 and H4 Subheadings are in "Sentence case" -- only the first word is capitalized. == Figures & Tables == Figures and tables are centered, placed inside a P or DIV with class of "caption". For example: <pre>&lt;p class = "caption"&gt;&lt;img src = "...."&gt;&lt;strong&gt;Caption for Figure&lt;/strong&gt;&lt;p&gt; &lt;div class = "caption"&gt;&lt;table&gt;&lt;tr&gt;...&lt;/tr&gt;&lt;/table&gt;&lt;/div&gt;</pre> Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text. Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text. == Code == Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin: <pre>&lt;pre&gt;[sourcecode language='php']RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed[/sourcecode]&lt;/pre&gt;</pre> Supported formats include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>.

=== Footnotes & Footnote References Recommended Reference Style Discussion: ===

A Notes section [https://writing.wisc.edu/Handbook/DocCSE_NameYear.html Council of Science Editors (if neededCSE) immediately follows the last of the article's narrative text. Notes are indicated citation format] has been voted in as the text either by note number in square brackets official recommended style (see: [1] or by author and year [Smith, 2007Citation_discussion]]. Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) | COINS]] element after the note.

==== Recommended Reference Style Discussion: =Endnote & Endnote References ===

Tim McGeary proposes that A Bibliography and Notes section (if needed) immediately follows the Editorial Committee chose a recommended style for all authorslast of the article's narrative text. Authors that do not choose recommended style need to follow another documented style References are indicated by author and communicate that to their assigned editoryear (Smith, 2007). Using a documented style will provide a clear editorial guidelines Notes are indicated in the text by note number in square brackets [1]. More details can be found in the [[Code4Lib_Journal_WordPress_Input_Guidelines#Endnotes_style_and_HTML_coding|Input Guidelines for consistency, and ensure proper citations and references of literature and resourcesEndnotes]].

jrochkindCSE reference style is the Journal's proposal: recommended style for bibliographies. Citations should be clear and unambiguous, and reasonably consistent within an article. Authors are welcome but not required An author may choose to use a formal different bibliographic reference style. Editors will ensure readability, clarity, but should follow that style accurately and reasonable consistency of citations, but will not check citations for compliance with stylebooksconsistently.

==== Voting on Recommended Authors can refer to this guide for using the [[CSE Reference Style: ===={| border="1" cellpadding="5" class="sortable" |- style="text-align: left;"]]

EditorsWhere notes refer to articles, please vote at books, etc., that are not available by direct link, insert a [[Citation_discussionCOinS (layman's description) | COINS]]element after the note.