A bit of a brief is that there are a number of locations throughout the site that will allow customisation of the layout of the page (widget form) for each user. There is currently a finite amount of available widgets although this may be set to change in the future.
The naming or identification convention could/would be something similar to WordPress in that status_1v_widget.php, marketing_add_stat_widget.php etc or via assigning widgets with ID numbers and storing these along with details (active, description, etc) in a database table or a combination.
Currently I'm stuck in the mind set of a table containing the following:
tblpage_custom
*ID (int)
*User_id (int)
*widget_id (int)
*widget_settings (string, comma seperated or similar)
widget_order (int)
site_location (string pagename)
Might be a tad arcaic and db intensive is my only concern with multiple calls per certain pages and several entries per page considering many will contain multiple widgets which in turn will need to call their associated data...
opinions welcome
This post has been edited by CSN-UK: 27 January 2012 - 03:00 PM
Help
















