If you are looking to reuse the layout for more then one page, then Display suite with a bunch of fields seems like the best choice.
If you want individual layouts per page, then Panels might be the right thing.
If you want the latter, but are afraid of Panels (as I am), then there is something else you can try. (from https://drupal.stackexchange.com/a/90744/2974)
- Create a node type "frontpage".
- Add a multiple-value block reference field with "Multiple Selects list" widget.
- Set up some bean types to allow different kinds of fancy boxes that can be placed on the frontpage.
- Use blockreference within a bean for nested layouts.
- One of the bean types could have a multiple-value entityreference to e.g. reference a bunch of products (and have them sortable). I generally prefer this over nodequeue.
- Use Display suite to define how each bean and the frontpage itself should be displayed.
- Use Display suite custom field templates to have decorated boxes around each bean/block in the blockreference, or each product, etc. Check hook_ds_field_theme_functions_info(). This stuff is powerful and awesome!
- Tell the client / content editor to use the contextual links to edit individual beans.
- In addition you can have Views blocks to be used in the block reference.
- Inline entity form might be useful, but I have not actually tried it in this combination. This is homework :)
The strategy is that everything that is unique to one page should be a block (or bean instance). We can afford that because those blocks don't pollute any theme regions.
This should give you some material to play with ..
More detailed questions should be discussed in dedicated stackexchange questions, since this is quite broad.