%%INCLUDE:undeadly_doc_start.html%% OpenBSD Journal: (Unpublished) Submissions %%INCLUDE:header_pre_h1.html%%

(Unpublished) Submissions

%%INCLUDE:header_post_h1.html%%
%%ARTICLES%%

Editor Notes

All submissions show up on this page. Here, you can edit stories, preview and save changes. If you see a submission that is clearly inadequate, feel free to delete it to keep the queue small.

Before publishing a story, ensure all relevant fields are filled:

  • Supply a meaningful Subject.
  • Specify the relevant person in Contributed by.
  • Email is currently not shown, so may be left empty.
  • Optional Web page becomes the link from Contributed by.
  • Make up some witty Department.
  • Topic was used historically, but is now obsolete.
  • Front text is (the initial part of the) main body of the article. If the story was written by someone else, start the Front text with something along the lines of "His-or-her-name writes:", enclosing the quoted text in a <blockquote>/</blockquote>.
  • If the entire story is reasonably short, everything can go into Front text, otherwise break it at an appropriate place and put the overflow in More text. Open HTML entities (such as <blockquote>) must be closed in Front text and re-opened in More text.

Processing of the submission form is restrictive with regard to character set and the HTML constructs accepted. If UTF-8 is required, it is more convenient to submit a dummy article and then add the relevant material in the editing phase.

Use of the HTML validator (link) is strongly encouraged.

It is common for multiple Editors to work on a story.

Standard practice is to seek review by the original contributor (where relevant) and other Editors prior to publication.

There is no confirmation dialog for the Publish action (in contrast to deletion of submissions and articles). Articles may, however, be edited after publication, and this is sometimes useful to provide update(s).

HTML Notes

  • Use the validator link to check HTML.
  • Use <code>/</code> rather than <tt>/</tt>.
  • Use of semantic HTML is encouraged, particularly for the sake of those using screen readers. Relevant points include:
    • &hellip; ("…") is preferred over 3 full stops ("...").
    • For emphasis and strong emphasis, use <em>/</em> and <strong>/</strong> rather than <i>/</i> and <b>/</b>.
    • Abbreviations and acronyms should be marked up as <abbr>/</abbr>.
    • Ideally, dates and times should be represented as time elements.

CSS Notes

There are a few useful styles defined in the Undeadly stylesheet(s):

  • '<pre class="grnscrn">…</pre>' can be used for a "green screen" look.
  • '<span class="cmd">…</span>' gives bolder text, as typically used for commands within "<pre>/</pre>" or inline (e.g. '<code>$ <span class="cmd">doas /sbin/ifconfig wg0</span></code>' for "$ doas /sbin/ifconfig wg0").
  • 'class="ccc"' is for displaying as a centred block. This can be convenient for images ('<img class="ccc" …>').
  • 'class="lll"' is for a left float with 1em margin on the right (and 0 elsewhere). This can be convenient for images ('<img class="lll" …>').
  • 'class="rrr"' is for a right float with 1em margin on the left (and 0 elsewhere). This can be convenient for images ('<img class="rrr" …>').