How To Get Published on Java Channels

Version 1

    Would you like to share your insight and technical expertise with other Java community members? If so, submit your article for publication. We are looking for application developers, architect, and experienced freelance writers to write articles that provide specific and useful information that will help members become more successful in their jobs.

    Before submitting an article, please familiarize yourself with our audience and editorial approach by reviewing previously published technical articles in our tech article archives (see categories to the left).

    Editorial Needs

    We have standing requirements for the following types of articles:

    • Tips, tricks, and techniques for using a particular technology, tools or methodologies (Agile, Devops..)
    • Performance planning and tuning strategies

    We are particularly interested in  the following technology areas:


    • Java SE and JavaFX
    • Java EE
    • Mobility/Embedded
    • Microservices
    • JVM languages


    Article Specs 

    Ideally, technical articles are between 2,000 and 3,000 words (exclusive of code listings).
    When writing a technical article, focus on adding value for the reader. Help readers make their use of the technologies involved more successful. Consider the following questions:

    • Who is the intended audience for your article?
    • How will readers benefit from reading your article? Is it actionable?
    • Will they learn a new technique?
    • Will they work more effectively if they implement the list of tips you provide?
    • Will they get started with a new product more successfully based on the implementation plan you describe?

    In your article, be specific about the details of your project. For example, rather than say "data migration can take a long time," quantify what you know, even if it's anecdotal: "Data migration can take two to four months, depending on the size of the database."

    • Provide rules-of-thumb and guidelines, and including point out obstacles they might encounter and offering workarounds for obstacles.
    • If talking about a specific project, what do you know now that you wish you knew before you started?
    • Offer sample code and detailed examples wherever possible.


    Submission and Editorial Process 

    Submit your article, proposal, or any questions to  . The article can be in plain ASCII text, Rich Text Format (RTF), or as a .doc or .odt. Include your full name, email address, postal mailing address, and daytime phone number and if the article is accepted, an OTN Community Manager will contact you.


    Authorization to Publish an Article

    When you submit an article, you are stating the following:

    • The article was created solely by you (and your co-author(s) if applicable),
    • The article is an original work and has not been published in any other form,
    • You authorize Oracle's use, modification, reproduction, and distribution of the article.

    Please do not submit articles that you've also submitted to another publication.

    Response to Your Article Submission

    If you've submitted a completed technical article, please note that it can take anywhere from 6 to 12 weeks for us to evaluate your article, and you may not be contacted immediately.

    Editorial Process

    If we decide to prepare your article for publication, you must be available for and respond to editorial queries on the content of your article. Articles may be edited for length and language, and will be published online only.

    By the end of the editorial query process, we will determine when the article is scheduled for publication. (Note that our needs change very quickly so all schedules are subject to change.)

    Commissioned Articles

    OTN occasionally commissions in-depth technical articles from the community with an author stipend upon publication.  If you would like to propose an in-depth outline for consideration, contact: