Here's a list of tasks associated with the NAWG website improvement project.
For planned releases, project-related events and other milestones, please see the roadmap article.
Details of the structure of a task can be found by scrolling down.
The website plans navigation menu follows the task list.
(There are also website issues listed).
Displaying 29 of 42 Tasks
|0029||Not started||Could||Facilities||Gift Aid|
|0040||Not started||Could||Facilities||Online donations.|
|0037||Not started||Could||Features||PayPal: interface: requirements & design.|
|0025||Not started||Could||Management||Online meetings: choose technologies.|
|0038||Not started||Unassigned||Presentation||Mobile devices: site appearance & usability.|
|0012||Not started||Unassigned||Participation||Comments: policy & strategy.|
|0032||Not started||Unassigned||Participation||Contact form: reduce spam.|
|0033||Not started||Unassigned||Participation||Email: reduce spam.|
|0034||Not started||Unassigned||Participation||Chat rooms: research.|
|0035||Not started||Unassigned||Participation||Forums: research.|
|0022||Not started||Unassigned||Facilities||Competition: haiku.|
|0036||Not started||Unassigned||Facilities||Link magazine: online viewing.|
|0039||Not started||Unassigned||Facilities||Competition: "100": go fully online.|
|0006||Not started||Unassigned||Features||Price calculator.|
|0007||Not started||Unassigned||Features||Design new media handling.|
|0011||Not started||Unassigned||Features||Review security requirements.|
|0020||Not started||Unassigned||Features||Review software layers for complexity and performance.|
|0030||Not started||Unassigned||Features||Email: automatic initial replies.|
|0013||Not started||Unassigned||Management||Testing strategy.|
|0014||Not started||Unassigned||Management||Backups strategy.|
|0042||In progress||Must||General||Improve search engine rankings.|
|0005||Suspended||Should||Features||Restricted areas on the website.|
|0001||Suspended||Could||Content||Break up long articles into smaller ones.|
|0031||Suspended||Could||Content||Email: tips & etiquette.|
|0017||Suspended||Could||Presentation||Use appropriate branding and imagery throughout the site.|
|0003||Suspended||Could||Facilities||Redesign the writing groups directory.|
|0004||Suspended||Could||Facilities||Email: accounts and addresses.|
|0009||Suspended||Could||Features||Improve text filters.|
|0028||Suspended||Unassigned||Features||Online entry forms.|
Overview – The starting point for documentation about our plans for the website.
- Document structure
Strategy – Details of our strategy for developing the website.
- Evolution over revolution
- IT and joined-up data
Your input – We want your help. This is your website; we value your ideas and feedback.
- What are we looking for?
- How to send us your ideas.
Schedule – When things are going to happen. Time scales, as far as we are able to estimate them.
Participation – A website where you get to take part, rather than passively absorb information, will be more fun and productive. We have plans to make this happen.
- Members-only areas
Facilities – Plans for the website in terms of functionality, useful tools and other applications.
- Social media integration
- Directory of writing groups
- On-line competitions
- Link magazine
Features – Plans for the behavioural and technical aspects of the site.
- Privacy & security
- People database
Articles & editing
- Temporal content
- Markdown for content
- Automatic TOC generation
- PayPal integration
Content – Plans for what articles, pages and other information to have on the site. Examples: news, information, events, competitions, products and services.
- Revamp "who is NAWG?" area
Presentation – Plans for improvements and additions to the way the site appears, e.g. its layout, styling and navigation.
Management – Plans to improve the operational aspects of the site, i.e. the way it's run and maintained, and the way we respond to communications.
- Operations & procedures
- Who does what?
Some of the above titles are hyperlinks.
Click for more detailed documentation.
More will become links as things evolve.
Each task has a state and a priority. The state represents it's position in the following life cycle:
- Not started.
- In progress.
The priorities are based on the MoSCoW method, and are explained below:
- The task must be completed for, and is critical to, the next release.
- The task should be completed for the next release, if time/resource allows.
- The task could be completed for the next release, if time/resource allows and all should tasks have first been completed.
- The task's priority is unassigned. This might be because it is pending review, or perhaps because it has already been completed.
|Author:||Kevin Machin||Date:||April 30, 2014 2:28 pm|
|Comments:||0 – permitted||Article:||2887 – public|