Magento Training Examples

Question

If you prepared a new Magento developer, what were some of the dummy tasks you gave them. Besides reading all the articles and examples, I’m looking for some ideas to give developers the opportunity to work after reading as much as possible about Magento, without working on the task.

If anyone has any good ideas, please let me know, you can even post some useful snippets of code for possible answers and what not. It can be a good thread if we get a lot of good answers because we, the technical manager, are responsible for the training here.

They can be a design template or a design module, it does not really matter. If someone publishes a really good example, I will mark this as an answer.

I’m not sure if this is suitable for Stackoverflow, but I’m not sure where else to put it, where qualitative answers will answer it.

Answer 1

The tasks that I gave really depend on what the developer should perform as part of his usual work. I tend to ask tasks that make the rabbit hole situation early on in the process, and make sure that the developer has enough support to come and ask when they get stuck.

For developers with an interface, it is best to develop a relevant topic or any tasks that need to be performed in some current project. As examples, ask them:

• Create a new theme directory with catalogs of skins, etc.
• Modify the template (along with the product /list.phtml and product / view.phtml) to accommodate some of the desired new features.
• Add the JS library to the product page for scaling or some other features that need to be loaded using Magento tools.
• Create a new page, including, if necessary, complete controllers and layouts, with the functionality that will be highlighted by the backend developer.
• Change CSS to check one page to fit the new theme of the site without breaking CSS for the rest of the site.

For backend developers, again the best thing is the real thing. The development of backend modules requires some considerable knowledge, but hitting the main points is not so bad. Examples:

• Launch the new Magento module.
• Override Magento core class using one of the local module
• Create some administrator functions to work with the new module.
• Add an ACL so that this feature is enabled / disabled for specific admin users.
• Integration with external code (see frontend developer above) for end-user functionality.
• Attach to the system configuration to use the new functionality as part of a normal system.

These are just general ideas, but they will make the developer think about how Magento is laid out and how it works. Of course, it may take several weeks or months of mentoring support to force the developer to such an extent that he is a self-sufficient Magento developer, but basically it is a matter of filling in the details after such things.

Hope this helps!

Thanks Joe

Answer 2

This is what we send to applicants to find out if they know what magenta does / how it works ... not sure if this is what you had in mind ...

Please follow these steps:

Cancel the action of the controller . Override Mage_Customer_AccountController, retaining all original functions, except that logoutAction redirects to the home page immediately not the logoutSuccess page.

Override Model Function : Override the Mage_Customer_Model_Customer model, retaining all the original functions, except that the getName () function always returns "Magento Rocks".

Edit Block : Change one of the blocks used on the client / account / index page to display a message of your choice.

Add observer : Add an observer so that after creating an order in the frontend, the last name changes to "Is Awesome"

This is not entirely practical ... in general ... but it allows us to see if people can write correctly in Magento, and not just modify kernel files, etc. As in any case in Magento, there are various ways to solve various problems, perhaps they define different methods or determine which one will be the most suitable.

Note. To emphasize that no one points to this, these “tasks” were not intended for practical use, and in fact, you probably NEVER would have performed any of them, they were designed to see if someone really do something (override model method, etc.) Magento way.