{"id":26550,"date":"2016-06-03T21:01:29","date_gmt":"2016-06-03T13:01:29","guid":{"rendered":"https:\/\/www.hongkiat.com\/blog\/?p=26550"},"modified":"2024-01-29T20:41:45","modified_gmt":"2024-01-29T12:41:45","slug":"what-i-learned-being-an-editor","status":"publish","type":"post","link":"https:\/\/www.hongkiat.com\/blog\/what-i-learned-being-an-editor\/","title":{"rendered":"30 Things I Learned in 30 Days As a New Editor"},"content":{"rendered":"

Transitioning from a writer to a Technical Editor at Hongkiat.com (HKDC)<\/strong> has been an enriching journey. With about a year of writing experience, I\u2019ve stepped into my first editorial role<\/strong>, learning the ropes under the guidance of an adept editorial team.<\/p>\n

In this piece, I aim to share my experiences and insights<\/strong> with readers, fellow writers, and budding editors. This is an exploration of my journey from a writer to an editor<\/strong>. For those interested in the HKDC editorial process, I\u2019ll touch on that first. However, feel free to skip to the next section for a dive into my practical experiences.<\/p>\n

\n\t\t\t\t\tRead Also:<\/strong>\u00a0\n\t\t\t\t\tConfessions of a Web Editor \u2013 An Inside Look<\/a>\n\t\t\t\t<\/p>\n

A Glimpse into Our Editorial Process<\/h2>\n

Let\u2019s take a quick tour of our 10-step editorial process:<\/p>\n

    \n
  1. Our journey begins with receiving the raw articles<\/strong> from our talented writers.<\/li>\n
  2. The initial review<\/strong> phase helps us determine if the article is fit for publishing. This includes checking for originality and relevance in areas like design, development, technology, and entrepreneurship.<\/li>\n
  3. Next is the technical editing<\/strong> stage. Here, we rigorously verify facts<\/strong>, test any included code<\/strong>, and assess recommended software, apps, or tips. We also scrutinize the external links provided in the article.<\/li>\n
  4. Another crucial aspect of technical editing is the structural checkup<\/strong>, ensuring each article has a clear and logical flow.<\/li>\n
  5. If we spot technical issues or areas needing clarification, we return the article<\/strong> to the author for revisions. This back-and-forth can occur multiple times.<\/li>\n
  6. Once technical and structural concerns are resolved, we move to language editing<\/strong>. This step involves correcting stylistic and grammatical errors and performing an initial SEO check.<\/li>\n
  7. We then format the post in proper HTML<\/strong>. This task is interwoven with technical and language editing, with various team members contributing.<\/li>\n
  8. Subsequently, a thorough proofreading<\/a> session takes place.<\/li>\n
  9. We then focus on graphics<\/strong>, ensuring they are appropriate and well-integrated into the post.<\/li>\n
  10. Finally, the post is scheduled<\/strong> for publication.<\/li>\n<\/ol>\n

    This process can span weeks, with the article moving between editors and often revisiting the writer for further refinement.<\/p>\n

    Key Lessons from My Editorial Journey<\/h2>\n

    Insights into the Editing Process<\/h3>\n

    1. The Unexpectedly Long Path to Publication<\/strong><\/p>\n

    Before becoming an editor, I underestimated the extensive effort behind each post. I used to think writers were the crux of a magazine, but now, as an editor, I see our role is equally pivotal. Join me as I delve into why I believe this.<\/p>\n

    2. The Critical Importance of Meeting Deadlines<\/strong><\/p>\n

    For editors, deadlines are incredibly stringent compared to those of writers. A writer\u2019s slight delay might not cause a stir, but an editor missing a deadline can disrupt the entire publication schedule. This highlights the value of having multiple editors in a team to maintain smooth operations.<\/p>\n

    3. The Value of Version Control in Editing<\/strong><\/p>\n

    Editing often involves revisiting earlier drafts for a better result. Here, version control tools are indispensable<\/strong>. Keeping the original draft is also crucial for resolving any potential disputes with writers.<\/p>\n

    4. Navigating First Drafts with Color and Care<\/strong><\/p>\n

    There\u2019s no set standard for marking issues in first drafts. While some editors use the <del><\/code> tag, leading to a plethora of deletions<\/del>, I prefer the <mark><\/code> tag for a less intimidating, colorful approach. It seems less frustrating for writers than seeing their work crossed out.<\/p>\n

    5. Establishing Your Own Style Guidelines<\/strong><\/p>\n

    Deciding on handling minor style errors, like exaggerations, word repetitions, tautologies<\/a>, and clich\u00e9s<\/a>, can be tricky. I\u2019ve learned it\u2019s beneficial to set personal style rules for consistency and efficiency.<\/p>\n

    6. Balancing Editing and Writer Collaboration<\/strong><\/p>\n

    It\u2019s crucial to decide what to edit directly and what to send back for writers to revise. I\u2019ve found that substantial changes and additions are better sent back to writers to avoid altering their original voice too much.<\/p>\n

    7. Editing: The Unseen Art of Perfection<\/strong><\/p>\n

    As an editor, your best work goes unnoticed \u2013 it\u2019s only when readers encounter issues that the absence or inadequacy of editing is called out. At HKDC, we\u2019re fortunate to have writers who invest heavily in their articles, making our job a bit easier.<\/p>\n

    8. The Inevitability of Errors<\/strong><\/p>\n

    No matter how hard we work, some errors inevitably slip through. Despite a meticulous editorial process, these oversights often go unnoticed until pointed out by our observant readers.<\/p>\n

    \n\t\t\t\t\tThe Truths About Self-Editing in Freelance Writing<\/span><\/a>\n
    \n\t\t\t\t\t\t\t