ResearchWikis/notes/2007-09-04 guru.com project: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
sekrit>Woozle
(morning stint)
(removed obsolete header)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[category:paid work]]
==Hours==
===2007-09-04===
* 17:24 - 19:58
** set up database
** uploaded MediaWiki files
*** MW upload was horridly slow; maybe knock off some time. Did some other things while waiting.
** glxp.com had to be re-pointed, and enom.com was down...
** located and uploaded extensions
** successfully installed MediaWiki
** installed extensions
===2007-09-05===
* 09:07 - 09:39
** Installed [http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion Labeled Section Transclusion] extension to help with non-editable sections
** Started creating non-editable sections example
* 09:51 - 10:54
** Finished non-editable sections
** sent email to John (via ''real'' email)
** Started on automatic indexing (created some dummy pages)
* 13:40 - 15:24
** automatic indexing: 2 examples created
** sent email about index samples
** patrolling enabled; trying to figure out how to use it
* 16:50 - 17:13
** added Add a Page, but it may be too simple
===2007-09-06===
* 08:36 - 10:30
** found CategoryTree extension; installed it; found it to be not what was needed
** status update email
** researching Patrolling feature
* 11:45 - 11:53
** email about Patrolling
* 14:38 - 15:24
** phone conversation
** another email
* 19:17 - 20:00
** started adapting main page to match mockup
* 20:44 - 21:33
** continuing mockup matching
** checking to see if there's an ''easy'' way to modify the toolbox contents
===2007-09-07===
* 12:53 - 15:21
** latest to-do from PowerPoint #2: modify logo, modify links at top, remove extra links from toolbox
* 17:30 - 18:12
** CSS stuff
* 21:11 - 22:16
** reworked the table in the middle to get rid of vertical line
** long email summing up status
===2007-09-11===
* 06:32 - 7:32
** changes from 0908 powerpoint
** got sample image ready to upload
==Access==
* '''domain''': glxp.com
* '''database''': hypertw_guruproj
** '''db user''': hypertw_gurubot
** '''db pass''': {{password|Th3Pa55w0rd}}
* '''wiki sysop''': WikiSysop
** '''password''': {{password|T3hSys0pRhulez}}
==Questions==
==Questions==
* Was the sample wiki shown in the PowerPoint presentation an actual MediaWiki installation? If so, I could use a copy of the skin and relevant .css files to make the wiki I am developing start out with that look. Since the appearance is 2nd priority, however, I won't focus on this until the functionality has been implemented.
* Was the sample wiki shown in the PowerPoint presentation an actual MediaWiki installation? If so, I could use a copy of the skin and relevant .css files to make the wiki I am developing start out with that look. Since the appearance is 2nd priority, however, I won't focus on this until the functionality has been implemented.
Line 68: Line 9:
==Proposal==
==Proposal==
===1. Tasks to be done===
===1. Tasks to be done===
* non-editable sections
* non-editable sections
* automatic indexes
* automatic indexes
* enable the patrolling feature
* enable the patrolling feature
* "add a page" feature as in wikihow
* "add a page" feature as in wikihow
====1a. non-editable sections====
====1a. non-editable sections====
* Create 1-3 pages with protected sections as specified by employer
* Create 1-3 pages with protected sections as specified by employer
* Includes creation of individual protected pages for transclusion in main page, with contents specified by employer
* Includes creation of individual protected pages for transclusion in main page, with contents specified by employer
====1b. automatic indexes====
====1b. automatic indexes====
* Install  [http://www.mediawiki.org/wiki/Extension:DynamicPageList extension] or make other code changes as necessary so web site has the ability to automatically display lists of pages based on <nowiki>[[category]]</nowiki> tags.
* Install  [http://www.mediawiki.org/wiki/Extension:DynamicPageList extension] or make other code changes as necessary so web site has the ability to automatically display lists of pages based on <nowiki>[[category]]</nowiki> tags.
Line 89: Line 26:
* create page for adding a page, if necessary
* create page for adding a page, if necessary
* make any necessary technical modifications (i.e. anything which can't be done through the web browser by a person familiar with normal MediaWiki editing) to bring the "add a page" page in line with the look-and-feel of the rest of the site
* make any necessary technical modifications (i.e. anything which can't be done through the web browser by a person familiar with normal MediaWiki editing) to bring the "add a page" page in line with the look-and-feel of the rest of the site
===2. Breakdown of time===
===2. Breakdown of time===
These estimates do not take into account any unexpected complications I may run into once the content requirements are known and I have actually looked
These estimates do not take into account any unexpected complications I may run into once the content requirements are known and I have actually looked
at the site.
at the site.
====BILLABLE HOURS====
====BILLABLE HOURS====
* 2a. non-editable sections: 1-2 hours
* 2a. non-editable sections: 1-2 hours
* 2b. automatic indexes: 1-2 hours
* 2b. automatic indexes: 1-2 hours
Line 103: Line 36:


I didn't list a time estimate for the "add a page" feature in my original time estimate (email of 8/30 5:37 pm) because at the time I needed more information. Of all the requested features, this is the one I where I am least certain of the exact process to make it work, hence the higher time-estimate and greater variation. Even with the maximum of 5 hours, however, this still falls within the allocated budget for this project.
I didn't list a time estimate for the "add a page" feature in my original time estimate (email of 8/30 5:37 pm) because at the time I needed more information. Of all the requested features, this is the one I where I am least certain of the exact process to make it work, hence the higher time-estimate and greater variation. Even with the maximum of 5 hours, however, this still falls within the allocated budget for this project.
====CALENDAR TIME TO COMPLETION====
====CALENDAR TIME TO COMPLETION====
7 days maximum
7 days maximum

Latest revision as of 15:30, 5 January 2020

Questions

  • Was the sample wiki shown in the PowerPoint presentation an actual MediaWiki installation? If so, I could use a copy of the skin and relevant .css files to make the wiki I am developing start out with that look. Since the appearance is 2nd priority, however, I won't focus on this until the functionality has been implemented.
  • For next stage: need to pin down how they would like each user's "credits" to be displayed.

Progress

  • non-editable sections - done; turned out not to be really necessary
  • automatic indexes - done
  • enable the patrolling feature - done
  • "add a page" feature as in wikihow - done, but may be too simple

Proposal

1. Tasks to be done

  • non-editable sections
  • automatic indexes
  • enable the patrolling feature
  • "add a page" feature as in wikihow

1a. non-editable sections

  • Create 1-3 pages with protected sections as specified by employer
  • Includes creation of individual protected pages for transclusion in main page, with contents specified by employer

1b. automatic indexes

  • Install extension or make other code changes as necessary so web site has the ability to automatically display lists of pages based on [[category]] tags.
  • Create 1-3 such lists either as needed for actual use or as examples for others to follow. Additional lists can be created if budget permits.

1c. enable "patrolling" feature

1d. Install "add a page" feature

  • decide which extension is best for implementing this feature
  • install extension
  • create page for adding a page, if necessary
  • make any necessary technical modifications (i.e. anything which can't be done through the web browser by a person familiar with normal MediaWiki editing) to bring the "add a page" page in line with the look-and-feel of the rest of the site

2. Breakdown of time

These estimates do not take into account any unexpected complications I may run into once the content requirements are known and I have actually looked at the site.

BILLABLE HOURS

  • 2a. non-editable sections: 1-2 hours
  • 2b. automatic indexes: 1-2 hours
  • 2c. enable "patrolling": <1 hour
  • 2d. install "add a page": 2-5 hours

I didn't list a time estimate for the "add a page" feature in my original time estimate (email of 8/30 5:37 pm) because at the time I needed more information. Of all the requested features, this is the one I where I am least certain of the exact process to make it work, hence the higher time-estimate and greater variation. Even with the maximum of 5 hours, however, this still falls within the allocated budget for this project.

CALENDAR TIME TO COMPLETION

7 days maximum