Changes

Code4Lib Journal WordPress Input Guidelines

1 byte removed, 20:17, 10 April 2019
no edit summary
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>&lt;pre&gt;</code> tags.
For more subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f
 
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
====Ampersand Issues====
140
edits