Book Image

Magento 2 Developer's Guide

Book Image

Magento 2 Developer's Guide

Overview of this book

Magento is one of the most exciting, flexible, and customizable e-commerce systems. It offers you an extensive suite of powerful tools for creating and managing an online store. After years of development, Magento 2 introduces itself with a strong emphasis on modularity, Web API's, automated testing and overall new technology stack platform.The long-awaited Magento 2 release introduces a whole new e-commerce platform to develop online stores. The all new Magento 2 architecture, Web APIs, and a host of other features are equally challenging to master as much as they are exciting to use. Tshis book will ease the learning curve by offering step-by-step guidance on how to extend the core functionality of your Magento 2 store. This book is your one-stop guide to build and customize a quality e-commerce website from the latest version of one of the largest, fastest growing, and most popular e-commerce platforms—Magento 2. We start off with an introduction to the fundamental concepts of Magento to give you a foundation to work from. We then move on to configure the development and basic production environment for Magento. After this, you’ll get to grips with the major concepts and conventions that are new to the Magento 2 platform. We then delve deeper to get to the core of automated deployments, persisting data, writing data fixture scripts and applying various backend and frontend modifications. As we near the end of the book, you will learn to make API calls and write automated tests. Finally, you will be guided through building a full-blown helpdesk module from scratch. By the end of this book, you will have learned a wide range of techniques to extend and customize your Magento 2 store to fit the requirements of your business.
Table of Contents (19 chapters)
Magento 2 Developer's Guide
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Module requirements


Module requirements are defined as follows:

  • Name used, Foggyline/Helpdesk

  • Data to be stored in table is called foggyline_helpdesk_ticket

  • Tickets entity will contain ticket_id, customer_id, title, severity, created_at, and status properties

  • The customer_id property is to be foreign key on the customer_entity table

  • There will be three available ticket severity values: low, medium, and high

  • If not specified, the default severity value for new tickets is low

  • There will be two available ticket statuses: opened and closed

  • If not specified, the default status value for new tickets is opened

  • Two e-mails templates: store_owner_to_customer_email_template and customer_to_store_owner_email_template are to be defined for pushing e-mail updates upon ticket creation and status change

  • Customers will be able to submit a ticket through their My Account section

  • Customers will be able to see all of their previously submitted tickets under their My Account section

  • Customers will not be able to edit any...