The D journal

Short Cuts...

Click on one of the links below for more information...

The D journal

Call For Papers:
Write for The D Journal

The D Journal is a new online magazine for software developers, aiming to increase awareness and understanding of the D language, Walter Bright's evolution of C/C++ (see http://digitalmars.com/d/).

The magazine will be published every second month - at http://thedjournal.com - probably starting April or May 2004.

We are looking for a variety of contributions, and would prefer them to conform to the following styles:

Top


Articles...

Articles take a relatively detailed look at a subject, and examine it depth. Articles should be written assuming that the audience is comprised of experienced software engineers but who know may not be expert in D itself.

In addition, for the relatively inexperienced, the article should contain references to explanatory material or, even better, contain sidebars - separate sections within the article in which a concept is elucidated. By not forming part of the flow of the article, experienced readers can get to the crux of the article, whilst inexperienced readers can find the background information needed for a fuller understanding of the article in the sidebars.

Articles can be on any topic related to D, but should preferably include technical content, accompanied by working source code.

You may optionally wish to include a PDF or HTML document representing the article (main text, sidebars, figures, tables & illustrations) as a whole, in order to better help us follow your original intent.

Top


Opinion Pieces...

Opinion Pieces structurally the same as articles, but here we're interested in (well argued) points over programming and programming language practise, philosophy and idiom.

We welcome controversial views, just don't be libellous!

Top


Tips...

Tips describe a less deep look at a subject area, or should examine a small topic in depth. Tips should be written assuming that the audience is comprised of experienced software engineers but who may not be expert in D itself.

Tips should contain references to any necessary explanatory subject matter not contained with the tip.

Tips can be on any topic related to D, but should preferably be more technical and "day-to-day practical". They may be accompanied by source code (which should be working).

You may optionally wish to include a PDF or HTML document representing the Tip (main text, sidebars, figures, tables & illustrations) as a whole, in order to better help us follow your original intent.

Top


Notes...

Notes are succinct simple snippets of wisdom. Most notes should be written aimed at inexperienced developers or those new to D.

Top


Document Requirements...

This is a summary of the specific document requirements.

Word Count:
Articles and Opinion Pieces: 2000-4000 words.
Tips: 400-800 words.
Notes: one sentence- one paragraph.
Format:
plain text files only. Separate paragraphs by blank line. Separate file for each sidebar (as required).
Code Figures:
plain text files only. No tabs (convert all tabs to spaces before submitting). Tabspacing should be set at 2 characters. A separate file is required for each figure listed in the text of the article, opinion piece or tech tip (name the files Figure1.d, Figure2.d etc.). For notes, code should be included in the main text file. Code may be edited for brevity, but will not be unnecessarily reformatted. The code should not contain lines which exceed 60 characters in width.
Code Archive:
This is the full code of which some/all appears as Code Figures. There are no constraints whatsoever on this code, except that it compiles and has the functionality described in the article. The code will be compiled and executed by the technical editor(s) prior to the article being accepted. You are advised to place copyright notices in the code. (Notes need not be accompanied by a code archive.)
Tables:
Plain text file (no tabs) formatted correctly. Note that we will not accept Excel spreadsheets, but you are welcome to accompany your article with a PDF or HTML document in order that we may better follow your original intent. (Notes should only contain tables if absolutely necessary.)
Illustrations:
We currently do not have facilities for rendering illustrations beyond simple image formats, so can only accept illustrations in JPEG, GIF, PNG or other common (and browser-compatible) image formats. (Notes should not use Illustrations.)
Biog:
the author is required to provide a valid email address, such that feedback and other correspondence can be facilitated. We would prefer the author provide full name and a brief biography (experience, interests, qualifications), but this is not required.

Top


Submission Details...

If you have an Article, Opinion-Piece, Tip or Note idea, please send it in to submissions@thedjournal.com. Please submit your contribution in a (WinZip compatible) zip file. If you have multiple simultaneous submissions, please place each in a separate zip and either put all zips in a composite single zip or add as multiple attachments to your email. (Note that we will not accept Word documents or Excel spreadsheets.)

You could get your name in lights!

Top

Copyright (c) 2002-2004 "The D journal". e-mail the webmaster