@jacksneed wrote:How many hours would you guess it would take an expert to do? Want to get a sense for how much it costs, considering I understand the hourly wages of these developers.
Transplant/porting is an advanced customization even if does boil down to a copy paste.
8hrs - If they've never built a section before but are comfortable with themes themselves(architecture,liquid, settings, html,css,js) and could work through the dev docs to build a theme section; assuming stumbling blocks like bugs JS incompatibility ,etc.
2-4hrs, an afternoon, if they are comfortable with sections but never made one before, assuming minor stumbles.
30m-1.5hr if they have done a similar operation before* and they are already setup in tooling and have been working on the exact source theme and or maybe the donor theme and no bugs occur. I.e. they are already in mental-flow and everything plops in.
Replicating , not transplanting , the index to a page maybe the same metrics but i'd times it by 1.5 if not x2 for any timelines as there's more moving parts, ... though those parts are made for that theme so /shrug.
But the alternate layout method should be checked first 1-2-3 hours including communications time.
The index page in most themes relies on {{ content_for_index }} populated almost exclusively through the theme visual editor i.e. dynamic sections. Gut that and insert sections???. JSON sectioned pages have certain limitations see docs.
~4 hours for both with specialist expert with prior experience and they are all ready setup and ready to go.
Though an actual expert will give pushback to sanity check this and understand better why this has to be done instead of just using the index page as an index page as intended. Because this can lead to a very confusing merchant support situation.
Add 1-2 hours to have them make an onboarding doc/video explaining to stakeholders what was done and how to use this theme that is no longer like a standard theme in the editors.
Add 1-2 hours for version control & docs especially if multiple people in repo/theme.
*That DOES NOT include stumbling blocks, comms, integrations, revisions: theme javascript, custom javascript, styling, bug checks, browser testing. Some things just plop in, others not so much.
