Changes

Jump to: navigation, search

Code4Lib Style Guide

936 bytes removed, 20:32, 4 August 2018
Add link to CSE style guide
 
== A Note About This Guide ==
 
This is a brief style guide for authors. For information about styles and conventions used in marking up articles for WordPress, see: [http://wiki.code4lib.org/Code4Lib_Journal_WordPress_Input_Guidelines Code4Lib Journal WordPress Input Guidelines].
== Start of Article ==
== Headings ==
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>.
== End of Document ==
=== Footnotes & Footnote References === A Notes section (if needed) immediately follows the last of the article's narrative text. Notes are indicated in the text either by note number in square brackets [1] or by author and year [Smith, 2007]. 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 InformationDiscussion: ====
[httphttps://owlwriting.english.purduewisc.edu/owlHandbook/resource/560/10/ APA Style Example DocCSE_NameYear.html Council of Science Editors (PurdueCSE)citation format]has been voted in as the official recommended style (see: [[Citation_discussion]])
[http://www.library.cornell.edu/resrch/citmanage/mla MLA Style Example (Cornell)]=== Endnote & Endnote References ===
[http://libraryA Bibliography and Notes section (if needed) immediately follows the last of the article's narrative text.osu.edu/help/research-strategies/how-do-i-cite-references/cse-citation-guide CSE Style Example References are indicated by author and year (Ohio StateSmith, 2007). 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 Endnotes]].
==== Voting on Recommended Style: ===={| border="1" cellpadding="5" class="sortable" |- CSE reference style="text-align: left;"is the Journal's recommended style for bibliographies. An author may choose to use a different bibliographic reference style, but should follow that style accurately and consistently.
!Name !! Recommend Authors can refer to this guide for using the [[CSE Reference Style? (Y/N) !! Which Style? (Vote even if N)|-| Tim McGeary || Y || CSE]]
Where notes refer to articles, books, etc., that are not available by direct link, insert a [[COinS (layman's description) |-| Your Name || Vote || Style |}COINS]] element after the note.
=== About the Author ===
364
edits

Navigation menu