Recently we were tasked to build a listing page in Drupal which would list down 200+ products on same page. It was already built in the system with pager, search-api facets and sort and some other custom features like showing thumbnail gallery for each product, triggering GA impression for each and many such things. So obviously choice of implementation was to keep using search-api for this to get the advantage of re-using the functionality and to avoid building facets.
No, I'm not going to share ideas about how to make customer successful. If you are here looking for that, sorry you are at the wrong place. What I'll try to share here is how I can help as a developer. Be patient for the next couple of minutes to understand my view and I'll keep the comments section open for anyone to suggest or correct my view.
I've heard from many that I'm pro-active. Thought I will just share what I do so it can help someone and more importantly help me get feedback on anything I can still improve on.
Day planning
I spend some time everyday to plan the day and set daily goals. I start my day by checking mails and checking if there is anything which has come up as new priority while I was sleeping, if there was any calimity which needs my immediate attention or anything which says I have the day off (party).
Below are few things I've learnt and I follow to be less irritating to the next person. It may be wrong, feel free to suggest better ways and give feedback on any or all points. You can even say I'm a messed up guy :D
Migrations in Drupal 8 are very stable and highly extensible. Still there are many cases though which would require custom code. I came accross one such scenario recently and will share some knowledge here which I gathered while working on it.
One - most of the examples shared are around process plugin or the plugins available in migrate (part of Drupal core) / migrate_plus modules. Ones that I browsed:
For all the developers of Drupal who had a very good development workflow in place and used to revert features in hook_update_N() to ensure the deployment notes were simply to run update.php or drush updb, there is a good news :)
Continuing to Reverting features in update hooks, I encountered a new scenario yesterday where I had to make a field translatable. Somehow we missed to make the field translatable during development and now since we are in update mode we need to handle it for existing sites as well.
