Changes
no edit summary
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.
===External Images and Attached Content===Two options for images and other attached content/media, use WordPress uploaded content managing feature, or upload the content to our host manually. jrochkind found the WordPress content managing feature to be more of a pain than it was worth, so is uploading content manually. To do that, sftp to c4ljeditor@login.ibilio.org. Ask jrochkind for the password for the c4ljeditor account. Change directory to:/public/vhost/c/c4lj/html/media in there you'll find an "issue1" subdir. Inside THERE (or other issue dir), 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 sort of url:http://journal.code4lib.org/media/issue1/lastname/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.
====Code====
====Images====
==Categories/Tags==
Every article in issue 1 should be put in a category "issue1". Etc.
[[Category:Code4Lib Journal]]
