Editorial Contributions

Note: If you're ready to submit an article to Embedded, please be sure to follow our submission guidelines. If you're still in the planning stages in writing an article, read on!

Embedded is a website devoted to the concerns of professional engineers developing embedded systems -- the software, firmware, and hardware – and integrating them and testing. We publish articles and blogs that explain all techniques, methods, and algorithms related to embedded systems. Our goal is to advance the state of the art for our readers, making their lives easier and simultaneously improving their productivity. To that end, we need your help. We are looking for embedded systems engineers and developers who will share their experience with our site users.

We define an embedded system as one based on a microcontroller or microprocessor or other IC that has a dedicated function and is part of a larger system. The range of such systems is quite large and Embedded regularly publishes articles on a variety of subjects. Embedded systems range from 8-bit microcontrollers to 64-bit RISC machines, with software ranging from simple data logging to sophisticated applications using real-time operating systems and multiple processors. Typically, an embedded system is housed on a single microprocessor board with the programs stored in ROM. Virtually all appliances that have a digital interface -- watches, microwaves, cars, airplanes, medical devices, robots -- use embedded systems. Some embedded systems include an operating system, but many are so specialized that the entire logic can be implemented as a single program.

In a similar vein, we consider Embedded a website for professionals, not for hobbyists or academics. Our readers prefer the proven technique to the theoretical novelty. We won’t refuse to deal with new or controversial topics, but your article should demonstrate a practical solution.

Types of articles and content we accept

Embedded primarily focuses on the “how-to” in development, with occasional forays into the “why-to” as well. The vast majority of the articles in the website discuss various techniques and methods for improved development. While the topic discussion and examples might use specific processors, hardware, or software, the underlying lessons of the article should be applicable to other target configurations.

Most of our articles are contributed by embedded systems developers and in some cases, vendor or industry experts. Embedded.com has evolved from a solely developer-written site to a community where both embedded systems developers and engineers working for tool or hardware vendors write content and interact in forums. Although our community now includes some technical representatives of vendors, we serve the embedded systems developer first and foremost. Our editorial staff uses the same editorial standards and process to review and approve all contributed content on the site. If you see the article on the site, an editor deems the article as useful to our readers. We promise to clearly identify what company an author represents.

For technical articles, we look for articles that address some common or emerging design problem and offer alternatives, tradeoffs and solutions. We tend to stay away from product-focused articles for a very pragmatic reason: Embedded's readers are quite savvy and appreciate a rounded problem/solution piece but typically lose interest quickly in something that's so specific to the authoring company's product line that there's little general benefit to a typical embedded systems engineer. Of course, specific products can be included as examples in discussing solutions but as a "for instance."

Our readers like to see code fragments - even pseudo-code. The presence of code in the article is also a positive indicator for us - or put another way: An embedded systems design/development article that doesn't have an opportunity to present some code or other design detail might be too conceptual to use as a technical article. (That said, it might be a fine candidate as a guest blog and we'd of course be happy to consider it as such.)

Figures and tables should positively contribute to the author's explanation (and the reader's understanding) of the topic. For an article on an MCU-based wireless sensor, it's not helpful to see a figure that only includes three blocks (for sensor, MCU, and wireless function or component); better would be one that a unique aspect of the design such as circuits for excitation, temperature compensation, and linearization (for example).

Technical articles tend to run ~2000 words but if the topic needs less, we'd rather see a focused piece than something padded to stretch. If the topic needs more, that's fine. We often split particularly long technical articles into multipart series.

Guest blogs tend to run ~800-1200 words or so. In contrast to technical articles, our blog posts tend to be much more opinionated naturally, but we still need to stay away from product-specific opinions!

Any contributed article must of course not have been published elsewhere.

To propose an idea or submit an article, please contact Clive "Max" Maxfield (max.maxfield@aspencore.com) or Steve Evanczuk (stephen.evanczuk@gmail.com). When you're ready to submit an article, please first check our submission guidelines for more details on what you'll need to provide with your article.

Read on for more explanation about the kinds of content we post on Embedded:

Opportunities for embedded systems developers, engineers, designers, and managers:

  • Long-form development articles: These tutorials instruct colleagues how to do achieve a proven development technique, improve performance of a system or a team, and avoid pitfalls. Written by embedded systems developers for other embedded systems developers, we put these articles into one or more of our Development Centers, on our home page, and in our newsletters.
  • Blogs: Commentary written by expert embedded systems developers. Are you the next embedded systems expert? Do you want to write a blog?
  • Source code: Often submitted with a how-to-develop article, you may also submit a standalone code to us that you are willing to share for free with other developers.
  • Video: We’ll be happy to look at a video you’ve made of a project you are working on or a day in the life of your team. If an editor likes it, we’d love to post it on our web site in the appropriate Development Center.
  • Product reviews: Want to review a product that you use, a new version of a product?
  • Book reviews: Want to review a book?

Opportunities for vendors, marketeers, book publishers, press reps, industry groups:

  • Long-form articles: These articles follow the same process and standards as a development article submitted by developers (see above). Topics here include general tutorials on a proven software technique, how to use an up-and-coming technology, and standards updates and what to expect.
  • Events: Submit your industry event for posting on our events calendar. Email us the details.
  • Competitions: We keep track of competitions our readers might find interesting and fun. We also work with vendors who want to create a simple competition and give away a free dev kit or samples to our readers. Contact us for more information.
  • Video: Vendor-sponsored videos can be very popular on our site. The editors may embed interesting vendor videos in their blogs or collections and may plug a video they like in our newsletters, but we don’t mix vendor videos advertise products in the editorial playlist on our video players. Your videos, however, can be placed prominently on our home page in the vendor sponsored play list, right next to the editorial playlist. Talk to our sales department about posting your video on our vendor playlist.
  • New product announcements: We do not run product announcements but send us your press release. It may stimulate an idea for a blog we write or for an article article we could suggest to you to tell the Embedded community about the development problems you are addressing.
  • Industry announcements: We do not run industry announcements but send us your press release. As with product announcements, industry announcements spur ideas for editor-written blogs or an opportunity for you to write a guest blog.
  • Book chapters: We post book chapters from newly published books in exchange for linking to the publisher’s information page or to the book page on Amazon.com. Book chapters get a mention in our newsletters and are treated as development articles, so they are placed in our top carousel on home page (and may sit there for as long as a month) as well as being featured on relevant Development Center home pages.

Please note: Webinars, technical papers, and courses are often paid, sponsored content from TechOnline library. However, our editors will often highlight useful content from TechOnline.

Parts Search Datasheets.com