140
edits
Changes
m
ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, it does syntax highlighting for you, e.g.:
<filename>.phps
→Bibliographies/Endnotes
/public/vhost/c/c4lj/html/media
in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this This sort of urlwill be used in the "<img src>" tag:http://journal.code4lib.org/media/issue1/smith/imagename.png
Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)
If code is attached as a file, follow the directions above for attached images, except:
* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)
ibiblio also has a PHPS extension, so if you an "s" on the end of .php files it will display the code rather than try to interpret the page:
<filename>.phps
Put all inline code in <code><pre></code> tags.
====Code Highlighting====
If the code is in a supported language, we can do syntax highlighting.
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:
Note: do not surround code with <tt><pre></tt> tags, as the <tt>[sourcecode]</tt> tag itself will generate the necessary HTML.
For more subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f
====Ampersand Issues====
==Bibliographies/Endnotes==
Items in a bibliography should be linked to the resource whenever possible. <!--We would like to provide COinS information with every appropriate citation that does not have a publically publicly accessible url.
It appears the COinS generator at http://generator.ocoins.info/ is no longer in service. An alternative is [https://www.zotero.org/download/ Zotero's stand alone citation software].
This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it. For an example see the [http://journal.code4lib.org/articles/7922 References section of a published article including coins].
-->
===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''
==Categories/Tags==
Posts will have "UncagetorizedUncategorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews
==WordPress Buttons==
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Submit URLS to Internet Archives for harvest ([https://gist.github.com/ruthtillman/fa7562989f299e4904c7fb0448d1fc83#file-waybacksubmit-py Wayback Submission Script] )
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.
