Difference between revisions of "Extensions:Design Update Voting"
(Created page with "{{subst:Extension Page}}") Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 1: | Line 1: | ||
| − | {{Extensioninfobox|title= | + | {{Extensioninfobox|title=Design Update Voting|desc=Adds the ability for staff with masterlist permissions to vote on pending design updates.|auth=Mercury|status=Testing|github={{Github|user=itinerare|branch=design-update-voting}}|migration=yes|package=no}} |
<!-- Put a short summary of your extension here! --> | <!-- Put a short summary of your extension here! --> | ||
| + | Note that this incorporates the changes in {{Github|user=preimpression|branch=bootstrapTables}}! | ||
| + | |||
| + | Adds the ability for staff with the Manage Masterlist permission to vote on pending design updates and MYO submissions. Note that this doesn't actually process submissions either way, it is just intended to serve as a communication tool (since sometimes a drive-by "looks good" button press is more manageable for folk). The number of votes "required" is provided via an added site setting; the default is 3. | ||
| + | |||
| + | Specifically, it adds a card to the header of pending and approved design updates. Staff can only vote on pending updates, but the information remains displayed on approved design updates for the sake of archival. In the top right are buttons to vote to approve or reject, above which are displayed the current number out of the total required number of votes. The bottom half is given over to the lists of each sides' votes/voters, with usernames for the sake of record keeping. It also adds a display of the current votes in the admin queue/index displays. | ||
== Installation == | == Installation == | ||
<!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. --> | <!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. --> | ||
| + | Pull the branch; run <pre>php artisan migrate</pre> and <pre>php artisan add-site-settings</pre> | ||
== Configuration == | == Configuration == | ||
<!-- Is any configuration necessary? Describe it here! --> | <!-- Is any configuration necessary? Describe it here! --> | ||
| + | If desired, change the number of votes requested in the "site settings" admin panel. | ||
== Usage == | == Usage == | ||
<!-- Is there anything users should know about using your extension? --> | <!-- Is there anything users should know about using your extension? --> | ||
| + | The voting panel will appear on pending design updates/MYO submissions. Staff can then click the voting buttons in the top right of it to cast their vote. | ||
== Troubleshooting == | == Troubleshooting == | ||
<!-- Are there known issues or errors that require user action? Who should they contact, and where, for support? --> | <!-- Are there known issues or errors that require user action? Who should they contact, and where, for support? --> | ||
| + | Find me in the Lorekeeper discord! | ||
== See Also == | == See Also == | ||
<!-- Any relevant other pages. You may consider linking to related extensions, for instance. --> | <!-- Any relevant other pages. You may consider linking to related extensions, for instance. --> | ||
| − | |||
Revision as of 14:41, 13 August 2020
| Description | Adds the ability for staff with masterlist permissions to vote on pending design updates. |
|---|---|
| Author(s) | Mercury |
| Status | Testing |
| Github | design-update-voting |
| LK Version | Unspecified |
| Contains a Migration | |
Note that this incorporates the changes in bootstrapTables
!
Adds the ability for staff with the Manage Masterlist permission to vote on pending design updates and MYO submissions. Note that this doesn't actually process submissions either way, it is just intended to serve as a communication tool (since sometimes a drive-by "looks good" button press is more manageable for folk). The number of votes "required" is provided via an added site setting; the default is 3.
Specifically, it adds a card to the header of pending and approved design updates. Staff can only vote on pending updates, but the information remains displayed on approved design updates for the sake of archival. In the top right are buttons to vote to approve or reject, above which are displayed the current number out of the total required number of votes. The bottom half is given over to the lists of each sides' votes/voters, with usernames for the sake of record keeping. It also adds a display of the current votes in the admin queue/index displays.
Installation
Pull the branch; run
php artisan migrate
and
php artisan add-site-settings
Configuration
If desired, change the number of votes requested in the "site settings" admin panel.
Usage
The voting panel will appear on pending design updates/MYO submissions. Staff can then click the voting buttons in the top right of it to cast their vote.
Troubleshooting
Find me in the Lorekeeper discord!
