Difference between revisions of "DevelopmentPriorities"

OurWork

Create a tool where a user can input a word or phrase (for example, a domain name) and the corresponding AboutUs WikiPage is automatically tagged with an inputted set of categories, as well as a badge (via a template probably). This will make it painlessly easy for visitors to AboutUs (and portal builders) to add WikiPages to portals or other aggregated pages like PortlandTech or LASIK.

The code for the button would need to be editable to specify which template to add so that the user doesn't have to input these things AND we have flexibility for different intersected sets (all we need is a new template), allowing this 'Add This Here' to work as a universal tool for a variety of Content and Community projects, as well as being something the external portal builders can use for creating their own aggregated content areas.

Example

The button would appear next to the various listings on a page, like the 'Software' heading on PortlandTech/Companies, prompting the user to enter a domain to add. On click the corresponding WikiPage would have a template added to it that includes categories PortlandTech, Company, Software and the PortlandTech badge. Once these tags are added to the page it should automatically load in the intersect set on the example page. (Might require Purgepage to purge the server's cache so that users aren't adding their URL a bunch of times because it isn't showing up immediately on the intersected list.)

Why this is important

Critical to UI of PortlandTech. Is also a large part of the "One-click Portal" (making it easy for anyone to create and edit their own portals).

DoneDone

When I can enter a page and see it added to the intersected list (via categories added to the page). What to do about bots hitting the add category special page?

Steps to get to DoneDone

• Read out community suggestions and make appropriate changes.

Not Related to this Task

• Fix the category casespace problem in the intersect extension.

Discussion

Badge template order

Not sure where to put this, but because the order of the badges matter (for the Google tracking and portal skinning), when the tool adds the badge, it needs to be able to add it to the bottom of the badge list, not the top, so as to not off-set previous badge tracking/skinning. (See a page like: AboutUs.org or Mentor.com for examples of what I mean). Otherwise, my preliminary tests work pretty well. -- TakKendrick | talk

• The order has been reversed. New badges should now appear at the end of existing ones. --Ali Aslam 04:28, 8 February 2008 (PST)

Julia's thoughts (with comments by Tak)

I used the tool to add instituteofmosaicart.com. It added the template to the "badges" area with

... also, I'm not sure why the portlandtech badge was added. It put instituteofmosaicart.com in the portlandtech sphere.

• Julia (and others), I just switched the template it's calling around so that it adds what is clearly a test badge. Obviously, the test badge was based on the PortlandTech badge and has inadvertantly included that coding. -- TakKendrick | talk 14:49, 7 February 2008 (PST)

I would like to suggest a wording change on the first screen: At the very top: Be Included in PORTALNAME / In the main box: Being included in a portal is a great way to gain industry recognition. Enter the page name below. In italics: (For Example: Foo.com). And I think the button could say: IncludeUs/ on the next page, the main title: Congratulations! and in the main box: PAGENAME has successfully been added to PORTALNAME. Needs a Button: Return to PORTALNAME.

• I for one would also like to discuss a wording change, primarily to one that specifically says, "You'll be adding yourself to this portal: PORTALNAME". Also, this current implementation doesn't do "mass" inclusion for portals (either add a variety of pages, or add a single page to several categories in the portal) at all, but my thought was that was always a "Rev 2.0" feature anyway. What do the developers think? -- TakKendrick | talk 14:49, 7 February 2008 (PST)

• It would be great if we could improve on the current 'Add This Here' wizard text. We'll happily change it.
• The current implementation does not allow mass inclusion of pages in a particular portal. We'll have to do it one at a time until that improvement is rolled out. --Ali Aslam 04:36, 8 February 2008 (PST)

AddThisThere

What I mean by this is that it would be great to see some functionality for folks who are building portals (along with AddThisHere which is to be included in an existing portal).

• Fix Statistics
  
  our stats so that they show up properly here: http://meta.wikimedia.org/wiki/List_of_largest_wikis
• TrackPageVisits
  
• MiscellaneousTasks
  
• UrlMagic
  
• FixMediawikiRedirects
  
• AboutUsSiteMap
  
• EmailConfirmation/Preferences
  
• ClaimsCasespace
  
• InfluenceUs dev task
  
  still need to add influence us comments to user pages (see task list)
• FlagOkForAllAudiences
  
• Print Bug
  
• Semi-Automated InfluenceUs PingPong
• UberPatrolImprovements

Handoff Lahore to Portland

• FixMediaWikiRedirects deployed. Kindly read the comments on its task page. Need your comments as well.
• Print Bug deployed. Need Vinh's attention on some styling issues (A weird bar shows in the footer).
  • Works for all pages except for a small glitch in the portal pages where it leaves the banner in the print version.
• AddThisHere deployed. Check this on Portal:AddThisHere.
• InfluenceUs Tweaks:
  • Suppressed influence us button on all but default namespace (i.e. 0).
  • Addressed Stephen's concern on AJAX request.
• Firefox Issue:
  • Fixed css which now allows edit cursor to appear on all input fields in our popup dialog boxes when viewed in firefox.
• Need to discuss PageLevelStatistics that how we would be storing the data.
• New task created Fix Disabled Contols On Save Problem
• Kindly someone clean up this page. Thank you =) --Ali Anwar 05:13, 7 February 2008 (PST)

Handoff Portland to Lahore

• Working on articulating a few AboutUsProjects ... tasks will spin out from them
  • Great! The tasks look very exciting. Can't wait to get our hands dirty.
• Can we put together a short page on the correct steps for creating, staging and testing branches? I thought I was good to go, but ran into a few snags while setting up a new branch. Ethan also expressed interest in knowing. -- Vinh
  • export ABOUTUS_USER=UserName (where UserName is your nimbus user name).
  • To Create a branch
  • To Stage a branch
  • Note: You need to 'unstage BranchName' if the branch is not correctly staged before.
  • dev_tools updated + fixed minor bugs.
• The InfluenceUs javascript is making an AJAX request when every single page is loaded. It should only be loaded on demand when someone invokes the wizard. -Stephen Judkins
  • Thanks for pointing that out. The AJAX request is now made only when someone clicks on the influence us button.

To Consider for Next Iteration

1. Graphic Design of portal skins
   
2. Override Automatic Scaling of Intersected Maps
   
3. Geocode and map domain pages with multiple addresses
   
4. Integrated CRM pilot
   
5. Emit hCalendar microformat for tech portals
   
6. Category Advertising
   
7. Uber Patrol
   1. Update UberPatrol to allow us to leave edit summaries on Roll-to (because reverts hurt).
   2. Alter UberPatrol so we never see blank edits such as: this one (alternatively, this could be done by a bot on "save page", setting the patrolled flag to yes at that time, or even not saving an edit that's blank.
   3. See the "possible adult content" flag on uber patrol just as we can see it on the main wiki pages.
8. Interface
   1. An AboutUs home page tab next to edit.
   2. Promote the "Random Page" button to somewhere in the skin so people can find it more easily Ray
   3. Show the "Get a Badge" capability somewhere where people can easily find it (like maybe in the skin also?) - Ray | talk

      What happened to this? Wasn't it supposed to be the 4th offer? TedErnst (talk) 02:21, 14 January 2008 (PST)

9. Add an upload a logo affordance similar to the upload portrait affordance to make it easier to add logos to company pages
10. for email alerts task, we need list(s) (perhaps daily these are just added to the bottom of a page - and community staff removes items from the top of the lists as we do the edits - would that work for dev?)
    1. newly watched pages (both get page alerts and my watchlist) and
    2. watched pages that have been edited by non-sysops so we can provocatively edit them again
11. Mark all edits by a particular login or ip as "patrolled"
12. We want a list on admin wiki of pages edited last week (each week) by logged in folks where email of the editor matches domain of page; we want a link to the history of the page edited and a link to admin wiki domain page.
13. List of pages watched by logged in folks, (If possible, show on the page itself "people watching this page")

The rest

• (?) ChannelTracking (?)
  
• (?) Monitor Meaningful Modifications (?)
  
• Sponsor CRM
• (?) Category as default for search terms (?)
  
  (?) Category results for basic search (Umar)
  

• Simple Badge
• (4) WhoisRefreshRunRefresh (Jason and Ali)
  

• (?) Granular Recent Changes (TakKendrick, ChrisBabson, JohnStanton, MarkDilley)
  
• Revise and Implement Google Maps API
• Advertising on possible adult content pages - after Mark identifies vendor
• Every domain page 5 calls to action
• Search Improvements
  
• Deploy widgets on Domain Pages
• (3) FrontPage AB Testing (?)
  
  • (3) Redesign Layout of Homepage (Vinh)
    
  • (5) ActionReporting (Umar)
    
  • DomainPage AB Testing
• (2) AboutUs Widget (Vinh, Ward)
  
  • (5) Redesign DomainBox Template (Vinh)
    
• (8) Topsoil Shadow of Admin Wiki (?)
  
• (?) Solve Adult Content 302 Issue (?)
  
• (5) ConsensusPollingAffordances for Participants (Laiq Jafri | Arif Iqbal )
  
• (1) Upgrade Admin Wiki to Ver 1.11 (?)
  

Open Tasks