The Lightning - Writers' Guidelines

  1. Submission

    2. Currently, all material intended for the magazine should be sent to Morten Lehmann. 

       Internet:       ml@db.dk
   Snail-mail:     Morten Lehmann
                   Kisumparken 77, 1. tv.
                   DK-2660  Brondby Strand
                   Denmark

    Material should be in either standard ASCII-format or HTML2-compliant format. If you submit your material in ASCII-format you're encouraged to attach a document with guidelines as to the final formatting of your material.
    Blitz-code should be submitted in ASCII-format. (Use ...[menu-item, which I can't recall at the moment] ). Also, whenever possible, try to list any special libraries you use, which are not in the standard Blitz-package.

  2. Copyright

    3. All authors retain copyright on their material. Therefore please enclose a note, that you're allowing us to use the material submitted, or that you're issuing the material into the Public Domain.
    Please note though, that readers are allowed to use the sourcecode presented in the magazine as they wish.
    'The Lightning' or it's editors can not be made responsible for the content of anything submitted to and used within the magazine, following these conditions.
    [Now, I don't know s**t about law. Could someone try to translate this into something that will not give us any trouble?]

  3. Payment

    4. 'The Lightning' is freeware. As such we're making no money, and so the people submitting won't either. But you can go to sleep in the evening, knowing you have done something good for the Blitz-community!
    All those submitting material to the magazine are entitled to a free copy of the disk-based version, should they want it. Please state in the material that you want the disk, otherwise you won't get it.

  4. Content

    1. Tips
      If you've got a good tip regarding Blitz, just send it. A simple description should be OK here

    2. Article/SourceCode
      If you're submitting sourcecode, please take the time needed to fully comment it. We're not going to feature *any* uncommented sourcecode (except for perhaps the most trivial stuff). Whenever possible, also write a small article describing what your sourcecode does, and how it is structured - use your imagination :-)
      If you choose to go the other way around, that is writing an article and then illustrating it with some sourcecode, or source-snippets, please see to it, that all your sourcecode is either documented in the article or otherwise commented on.
      Don't worry about spelling mistakes etc. We'll be able to proofread everything.

    3. Tutorials/Series
      If you've written a tutorial/how-to article, please try to illustrate it with the odd source-code.
      If you've written a series or just part of a series, try to divide it into sensible parts. Divide the thing where it seems right logically. Also try to be at least one installment ahead! This way your readers won't despair, should you get 'writers block' or something.