User:Luccagenes/Sandbox/Maintenance2

  Wiki Projects highlights    News cycle:  1    2    3    4    Wiki Projects highlights   News cycle:  1    2    3    4    Wiki Projects highlights    News cycle:  1    2    3    4 

Notes: Determine the best equation to get most flexibility and how to configure the manual selection option that will allow the user to "browse" all the NEWS highlights at their discretion. Also note that templates could be randomly inserted if excess space is available and "fillers" could be dispersed here and there (a filler could be an image in combination with a "thought of the day", an "inspirational quote", or "words to live by".

Which equation is best: (each of the two adboxes, and the sidebar could have different timers)

Could switch on an ODD EVEN basis using minutes, hours, days, weeks, or months. Very limited as only two options (displays) would be available.

Could switch hourly (24 options plus could group by leaving blanks, 3 hours with same display) but this would result in limited versatility (every night at same time, the same display).

Could switch daily based on a week interval (7 options at most) provides good versatility assuming the user does not access the page only on Tuesdays, for example, as this would repeat week after week unless changed.

Could switch daily based on a month interval (31 options but blanks and repeats out of order would increase variety). Once set, it could be ignored for several months unless new templates were added. If templates were modified (outside the equation) this would be easier for editors. Problem is the long list (31 item spaces) and how to gain "manual access and display all 31 efficiently. Good question-no answer yet.

Could switch monthly (12 options but using 2 to 12 different templates which could be randomized). Might be good for the sidebar changes and this is a manageable amount of options.

Could switch weekly (52 options) but this would make the "manual" access even worse than the 31 choices for the daily switch.

Note: There is also a problem with how to link and display the "News cycle" for example, should the template number be displayed or the position number or just one instance of each template number. The latter would eliminate the long list (31) and is probably the way to go as the usere will not care about how the system works (only the option to check out other "news". Possibly call it something other than "cycle".   More thought needed.

  Wiki Projects highlights    '''News cycle: 1 2 3  4   5   6   7   8   9   10   11   12   13   14   15   16   17                     18   19   20   21   22   23   24   25   26   27   28   29   30   31 '''

| 1=Adbox1 News1 | 2= Adbox1 News2 | 3=Adbox1 News3|4=Adbox1 News4 | 5=Adbox1 News5 | 6=Adbox1 News6 | 7=Adbox1 News7|      default error }}

test multiple switch functions. {{#switch:{{#expr:{{CURRENTDAY}} <8}} | 0=result1 | 1={{#switch:{{#expr:{{CURRENTDAY}} <16}} | 0 = result2 | 1={{#switch:{{#expr:{{CURRENTDAY}} <24}} | 0 = result3 | 1={{#switch:{{#expr:{{CURRENTDAY}} <32}} | 0 = result4 | error

{{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.01}}}} mod 2}}| 0= | 1= |  }}   truncated minutes

minute {{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.01}}}} mod 2}}| 0= | 1= | }}

hour {{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.0001}}}} mod 2}}| 0= | 1= | }}

day {{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.000001}}}} mod 2}}| 0= | 1= | }}

month {{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.00000001}}}} mod 2}}| 0= | 1= | }}

year{{#switch:{{#expr:{{#expr:trunc{{#expr:{{CURRENTTIMESTAMP}}*0.0000000001}}}} mod 2}}| 0= | 1= | }}

<div style="position:absolute; font-size:15px; top:33px; left:15px; width:650px; height:715px; padding-bottom:5px; padding-top:5px; font-family:museo; background-color:#99ccff; color:maroon; border:5px solid gray; overflow: auto; box-shadow:10px 10px 5px #404040;">

<div style="position:absolute; top:0px; left:660px; width:275px; height:180px; border-radius:5px; background-color:#eeeeee; box-shadow:0px 0px 7px 1px #fdb34b; border:3px solid #fdb34b; font-size: 16px; padding:7px;"> Wiki Home Page <div style="position:absolute; top:40px; left:20px; width:230px; height:20px; border-radius:5px; background-color:#eeeeee; box-shadow:0px 0px 7px 1px #e33d7a; border:3px solid #e33d7a; font-size: 15px; padding:7px;"> New to the Genealogy?   <div style="position:absolute; top:90px; left:20.5px; width:230px; height:20px; border-radius:5px; background-color:#eeeeee; box-shadow:0px 0px 7px 1px #3c8ff7; border:3px solid #3c8ff7; font-size: 15px; padding:7px;"> New to the Wiki?   <div style="position:absolute; top:140px; left:20px; width:230px; height:20px; border-radius:5px; background-color:#eeeeee; box-shadow:0px 0px 7px 1px #87b940; border:3px solid #87b940; font-size: 15px; padding:7px;"> Want to Help?      <div style="position:absolute; top:210px; left:660px; width:275px; height:100px; border-radius:5px; background-color:#eeeeee; box-shadow:0px 0px 7px 1px #fdb34b; border:3px solid #fdb34b; font-size: 15px; padding:7px;"> Share your Opinion  We want your feedback Question of the week, enter question here.

Note for future reference: If the EasyAccessSeries is successful, a page called EasyAccessSeries should be created for search purposes (it could also list all pages in the series). Currently if EasyAccessSeries is entered in search box it will bring up all related articles but the full "word" has to be used. Searching " "familysearch wiki:e" wil display all related articles in the dropdown but a specific article may make searching easier..  <div style="position:absolute; font-size:12px; top:0px; left:0px; width:640px; height:175px; padding-bottom:1px;background-color:#ffffff; color:gray; border:5px double #d2bbff"> The "Easy Access Series" of articles provides a focused approach (a hub) to find a number of wiki pages related to a specific topic.             If you have suggestions for pages or topic that might benefit from this format: enter suggestion here. I

{{Hub ImageMapTest}}

Note: The effect is the opposite of what I anticipated. The first coordinates laid down receive the highest priority. Later ones (on top of a previous map are not recognized. I anticipated the upper most (last laid) coordinated would be recognized - NOT so.