Do you have a great story to share?  

Write an article for the first printed magazine of Magento Community, let your voice be spread out, and connect with a global audience.

Do you have a great story to share?  

Write an article for the first printed magazine of Magento Community, let your voice be spread out, and connect with a global audience.

    Write a text and join the group of the top-notch names in Magento world!

    There will be no Magezine without you – let’s get this straight at the beginning.

    Choose a topic you feel most competent in.

    You’re welcome to write any e-commerce related subjects, but as Magento-oriented journal we expect the articles to be focused on the platform and the community.

    What can you write about?

    Omnichannel, interesting Magento implementations (migrations), case studies, tutorials, tips&hints, how-to guides.

    If you are a developer, write about new features and work on code, feel free to share with us what challenges you were facing when coding.

    We value your time and effort, so send us your text proposal first and we’ll let you know by a week if the topic has been accepted.

    Write a text and join the group of the top-notch names in Magento world!

    There will be no Magezine without you – let’s get this straight at the beginning.

    Choose a topic you feel most competent in.

    You’re welcome to write any e-commerce related subjects, but as Magento-oriented journal we expect the articles to be focused on the platform and the community.

    What can you write about?

    Omnichannel, interesting Magento implementations (migrations), case studies, tutorials, tips&hints, how-to guides.

    If you are a developer, write about new features and work on code, feel free to share with us what challenges you were facing when coding.

    We value your time and effort, so send us your text proposal first and we’ll let you know by a week if the topic has been accepted.

    How to write for Magezine?

    We want you to have a space in Magezine to express your thoughts and ideas, share knowledge and experience. But we will not give up one thing – we want every article to be of the highest quality.

    To avoid any misunderstandings we have prepared a short guide for you on how to write texts for Magezine.

    Keep it simple (not stupid)!

    Don’t forget to explain difficult terms, avoid complicated sentences, long introductions and industry jargon (for merchants’ zone). However, if you’re a developer and write a piece for dev zone, you know best what language your professional group speaks. Just make sure that all terms you mentioned in the text are understandable.

    Make the message more attractive

    Use as many forms as possible to make the message more attractive e.g. text distinctions, graphs, stats, etc.

    Address the reader directly

    When writing, address the reader directly (per you).

    Do not reproduce content!

    Do not reproduce content that is already published, but this seems to be obvious, right?

    You don’t have to be a professional writer.

    You’re busy, we get it. So if you’re facing some troubles when creating a piece, keep calm – we’ll figure something out.

    The sources!

    If you use data, put a link to the sources at the end of the text.

    Some of the topics will not be published

    We believe that everyone brings unique perspectives that are valuable to our readers but the newspaper has its own volume limits and some of the topics will not be published. Which is why we have to choose what texts will appear in the current issue. But don’t worry, there will always be another chance and another issues.

    Deadlines

    Remember that Magezine is printed, so we have a deadline which we can’t exceed (try to negotiate with our printer – good luck with that). So if you delay sending us your text and miss the deadline, we won’t be able to include your article in the number.

    How to write for Magezine?

    We want you to have a space in Magezine to express your thoughts and ideas, share knowledge and experience. But we will not give up one thing – we want every article to be of the highest quality.

    To avoid any misunderstandings we have prepared a short guide for you on how to write texts for Magezine.

    Keep it simple (not stupid)!

    Don’t forget to explain difficult terms, avoid complicated sentences, long introductions and industry jargon (for merchants’ zone). However, if you’re a developer and write a piece for dev zone, you know best what language your professional group speaks. Just make sure that all terms you mentioned in the text are understandable.

    Make the message more attractive

    Use as many forms as possible to make the message more attractive e.g. text distinctions, graphs, stats, etc.

    Address the reader directly

    When writing, address the reader directly (per you).

    Do not reproduce content!

    Do not reproduce content that is already published, but this seems to be obvious, right?

    You don’t have to be a professional writer.

    You’re busy, we get it. So if you’re facing some troubles when creating a piece, keep calm – we’ll figure something out.

    The sources!

    If you use data, put a link to the sources at the end of the text.

    Some of the topics will not be published

    We believe that everyone brings unique perspectives that are valuable to our readers but the newspaper has its own volume limits and some of the topics will not be published. Which is why we have to choose what texts will appear in the current issue. But don’t worry, there will always be another chance and another issues.

    Deadlines

    Remember that Magezine is printed, so we have a deadline which we can’t exceed (try to negotiate with our printer – good luck with that). So if you delay sending us your text and miss the deadline, we won’t be able to include your article in the number.

    Technicals requirements

    Let’s stop for a moment at the structure of the text. Here are some essentials:

    Text volume:

    8000-15000 characters (including spaces).

    Title:

    catchy, as short as possible but to reflect the essence of the text.

    Lead:

    explanation what this article is about, a short summary of the most important information, 250-500 characters (including spaces).

    Graphics:

    tables, stats, charts, etc., are welcome. Each graphic must have a short title and a source. If the graphic illustrate a particular content of an article, a footnote (e.g., Fig. 1) must be added after the sentence describing the graphics.

    Graphics format:

    .png, .jpg, .tiff lub .pdf are allowed, saved in the highest possible resolution for printing (preferably 300 dpi) and sent as separate files.

    Authors details:

    short bio (up to 500 characters including spaces, written in third person) with a photo (high quality in .png, .jpg or .tiff format) should be also sent in separate files. You are welcome to add links to your social media accounts or/and website.

    Want to know more about Magezine?

    Have any questions? Let us know!

    Send an e-mail to: contact@magezine.co

    Technicals requirements

    Let’s stop for a moment at the structure of the text. Here are some essentials:

    Text volume:

    8000-15000 characters (including spaces).

    Title:

    catchy, as short as possible but to reflect the essence of the text.

    Lead:

    explanation what this article is about, a short summary of the most important information, 250-500 characters (including spaces).

    Graphics:

    tables, stats, charts, etc., are welcome. Each graphic must have a short title and a source. If the graphic illustrate a particular content of an article, a footnote (e.g., Fig. 1) must be added after the sentence describing the graphics.

    Graphics format:

    .png, .jpg, .tiff lub .pdf are allowed, saved in the highest possible resolution for printing (preferably 300 dpi) and sent as separate files.

    Authors details:

    short bio (up to 500 characters including spaces, written in third person) with a photo (high quality in .png, .jpg or .tiff format) should be also sent in separate files.