(development site – not for public use – official site: www.nawg.co.uk)

Website Plans: Schedule: Tasks

Website Plans
Contents
  • Overview – The starting point for documentation about our plans for the website.

    • Introduction
    • Terminology
    • 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.

    • Communication
    • Members-only areas
    • Interaction
    • Contribution
  • 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.

    • Material

      • Revamp "who is NAWG?" area
    • Organisation
  • Presentation – Plans for improvements and additions to the way the site appears, e.g. its layout, styling and navigation.

    • Layout
    • Style
    • 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.

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.

List of Tasks

Note: some of these original tasks have been moved into the issues area.

Task 1: Break up long articles into smaller ones
Description

Many of the current articles are long, containing a lot of useful information, but also require a lot of reading and scrolling. This could be improved by devising methods for sub-dividing the content, where appropriate.

[01-Feb-2017] The following candidates have been identified:

Post Size Title Possible Remedy
5406 31,554 Restricted Areas: Specification Split into two: specification and project plan.
4389 31,189 NAWGFest 2016: Workshops, Talks & Timetable Move detailed timetable into separate article.
5421 26,538 Time Plan: Year Ending 2017 Put monthly tasks into separate articles.
3649 21,079 Festival 2015: Courses & Timetable Move detailed timetable into separate article.

The sizes were derived using the following database query:

SELECT ID, LENGTH(post_content) AS len
FROM  wp_posts
WHERE (post_status = 'publish')
ORDER BY len DESC
Resolution

[02-Feb-2017] Split up some articles:

  • "Festival 2015: Courses" and "Festival 2015: Timetable" are now two separate articles.
  • "NAWGFest 2016: Workshops & Talks" and "NAWGFest 2016: Timetable" are now two separate articles.

[15-Dec-2017] Task suspended.

Task 2: Front page improvements
Description

The front page is usually the first place a visitor lands. For this reason, it should be as user-friendly as possible:

  • Easy to understand,
  • Easy to use,
  • Convey information clearly.

Improvements can be made in this area.

Have a think about this and let me have your ideas. Please note that there's often a temptation to deem all things important and to try to put everything and the kitchen sink onto the front page. Doing that would just cause information overload and not help our visitors.

Most users would rather do one or two clicks to get to their information, than have to read through many paragraphs on the front page.

Shortcomings Possible Improvements
Too busy. There is too much information on the front page and it's too cluttered. Much of this information is of relatively lower importance and is duplicated elsewhere. Remove unnecessary information. In particular, the large category panels below the blue "benefits of joining" and "who are we?" panels. Category links are already provided in the side bar.
Stale headlines. The headlines panel (purple) requires regular human review and updating. This does not always happen. Regular automated reminders for the web administrator and other contributors.
How to do things?

It's not very clear how a visitor should go about actually getting things done, such as:

  • Joining up,
  • Finding a writing group,
  • Finding and entering competitions,
  • Finding and booking for events.

There are a couple of side bar panels for this, but they are easy to miss.

Add some "call to action" links, with clear and concise instructions.
Lack of emphasis.

The front page is an opportunity for NAWG to promote itself by emphasising its events, competitions, products and services.

This is not really happening. Instead there are catalogues of the most recent articles in various categories, with no real emphasis on anything.

In particular:

  • The "Friends of NAWG" panel is virtually useless. It contains a single link to a very outdated article and is of marginal interest at best.
  • The "Link – Our Bi-monthly Magazine" panel is also very weak. It contains a single link to the Link information article, but does nothing to promote the magazine. It is therefore little more than a navigational aid and, in that respect, redundant.
  • Four of the other panels have automatically generated lists of articles in the categories: "Events", "Competitions", "Writing Group News", and "Publications". Again, these can serve as navigational aids (though unnecessary, given the side bar navigation widgets), but do little to promote NAWG and its activities.
  • Chose only important categories that we wish to promote on the front page. For example:

    • Events. NAWGFest in particular.
    • Competitions. Currently active ones in particular.
    • Publications. Link in particular.

    Drop the existing ones that are of relatively low interest and/or low update frequency, such as "Writing Group News".

  • Replace the "automatic" panels with carefully worded promotional ones, with up-to-date information. This would have the additional benefit of reducing some of the items in the "headlines" panel.
  • Move the "Benefits of Joining" and "Who Are We?" panels to the bottom, as these are not necessarily the primary focus.
Uninteresting/poor graphics.

The graphics on the front page, what little of them there are, leave a lot to be desired. In particular:

  • The use of stock "clip art" style images, mostly with very weak relevance to the subjects they represent, give the site an amateur look and feel.
  • There's generally too much text and not enough graphics. This can cause visitors to lose interest quickly.
  • Remove all "clip art". In each case, replace with:
    • Stronger graphics with more relevance to the subject, or
    • Real photographs (not stock ones).
  • Improve the graphics to text ratio by having less text and more images.
Resolution

[23-May-2017] Requested input from the committee.

[17-Jul-2017] Added "lack of emphasis" shortcomings to the list, along with suggested improvements.

[18-Jul-2017] Added "uninteresting/poor graphics" shortcomings to the list, along with suggested improvements.

[20-Jun-2017] Produced a proposed new front page, version "alpha-1", as part of site iteration 2.8.0:1, on the test site. Main changes are:

  • Reducing the number of columns from two to one.
  • Absorbing and condensing all panels into a single multi-tabbed panel.

[04-Aug-2017] Version "alpha-2" made available on the test site, iteration 2.8.0:2. Changes are listed below the main panels.

[08-Aug-2017] Version "alpha-3" presented on the test site, iteration 2.8.0:3.

[30-Aug-2017] Version "alpha-4" presented on the test site, iteration 2.8.0:4.

[22-Sep-2017] Version "beta-5" presented on the test site, iteration 2.8.0:5.

[2.8.0] New version of front page released.

Task 4: Email: accounts and addresses
Description

Review the use of the various email accounts used by the site, particularly the administrative ones. Some early thoughts:

  • Consolidation – There are email links all over the place, without any particular consistency. If an email address changes, for any reason, then updating all the links will be a lot of work.

    A method for centrally storing the actual addresses, then using a referencing method when creating links in articles, would improve matters.

  • Decoupling – The email addresses in use are often the ones belonging to the individuals concerned. This is not necessarily the best way forward, since:

    1. Roles can change within the organisation.
    2. It can result in messages regarding NAWG business and personal messages being mixed together in a person's mailbox.
    3. There may often be no official NAWG site copy of important messages.

    A better technique would be to set up official, role-based email addresses for the site. Ones that need not change over time, unless the roles themselves are seriously reorganised. Messages can then be copied/relayed to whoever is currently fulfilling the role in question.

  • Symbolic addresses – Use short, symbolic names for email addresses, with a master look-up table and references for links, rather than hard-coding in each article. This will make email address changes easier to manage.
Resolution

[17-Aug-2016] Most of this work has been completed, with the exception of the last part – the use of symbolic names for email addresses in articles.

Task 6: Price calculator
Description

Some of our bigger events, such as NAWGFest, have a complex set of options when it comes to selecting and booking things. The current system of having a limited drop-down list of choices is insufficient and does not handle all situations. The result is that customers cannot select exactly what they want, nor can they be presented with the correct prices for their desired options.

The ability to render a price calculator would improve things greatly. This would permit every distinct option for an event (or other product) to be individually selected or omitted by the customer. The resulting price would be calculated and presented.

This new system would include the handling of things such as:

  • Amounts of money pre-paid for (say) advance booking,
  • Discounts,
  • Preset combinations for popular choices, to ease the selection process.

The price calculator software would need to be integrated with PayPal (see related task 37), since this is a popular method of payment.

$ 18 @type=5 @state=4 @level=2 @headline=Integrate the site with social media. @desc=

Many integrations are possible, but a first "quick win" step is to introduce the following widgets that can be applied to any article:

  • "Like us on facebook" buttons.
  • "Follow us on twitter" buttons.
  • Similar one-click tricks for other social media?
@res=[2.7.4] Support for Facebook and Twitter added, via "Social Links" software package. $ 21 @type=2 @state=4 @level=2 @headline=Link magazine: dates. @desc=

Provide a full calendar for Link magazine, showing the following dates:

  • The six publication dates.
  • The corresponding six deadline dates for submissions from contributors.

At a committee meeting, held on 21st November 2015, it was decided that:

  1. Publication dates will normally be on the 1st of the following months: Feb, Apr, Jun, Aug, Oct, Dec.
  2. The deadline for content submissions will be on the 1st of the month before each publication, i.e: Jan, Mar, May, Jul, Sep, Nov.
@res=[24-Nov-15] article 418 added. $ 27 @type=2 @state=4 @level=2 @headline=Writers' resources: list of first lines. @desc=

We have a collection of handy first lines, for writers who may be stuck for a beginning to their story. There are, at the time of writing, 416 lines. We intend to release these in smaller batches on a regular basis, in order to encourage people to visit the website frequently.

After every 50 lines, we'll add an alternative, such as a piece of writing advice, or a story prompt.

@res=

[29-Oct-2016] At a committee meeting, it was decided to display ten of the first lines per month.

[08-Nov-2016] The first ten are now on the website.

[08-Dec-2016] The second ten are now on the website.

[08-Jan-2017] The third ten are now on the website.

[08-Feb-2017] The fourth ten are now on the website.

[14-Mar-2017] The fifth ten are now on the website.

[10-Apr-2017] Added resource article: "Link to Think".

[14-May-2017] Added resource article: "Bare Bones Writing".

[17-May-2017] The procedure is now well under way. Task marked as completed.

$ 28 @type=6 @state=3 @level=4 @headline=Online entry forms. @desc=

Produce a feature which enables users to enter things directly using the website, rather than having to download entry forms as separate documents which must then be emailed or printed and posted.

The following are examples that could make use of this feature:

  • Application forms for membership.
  • Competition entry forms.
  • Booking forms for events.
  • Payment forms.

This would be an additional feature; the downloadable documents would still be available for those who prefer them.

Here are a number of WordPress plug-ins that might provide some of the necessary functionality:

@res=

[11-Nov-2016] There is an interesting WordPress TV presentation about the "MAPEE pyramid" way of thinking about forms.

[17-Mar-2017] Another WordPress TV presentation about creating good forms.

$ 29 @type=5 @state=1 @level=3 @headline=Gift Aid @desc=

Add information and a logo about Gift Aid to the "thinking of joining?" page.

@res= $ 30 @type=6 @state=1 @level=4 @headline=Email: automatic initial replies. @desc=

Many of our customers will be unaware of how NAWG is operated. In particular:

  • We have a relatively small number of staff.
  • We work part time and voluntarily, for no fee.
  • We have many other commitments in our lives.
  • Particular staff may be unavailable for long periods.

This can lead to frustration, particularly when email enquiries do not get a timely response.

A simple way to mitigate this issue, is to set up our email systems so that an initial automatic reply is given. This automated message (e.g. similar to an "out of office" reply) would need to politely:

  • Provide some or all of the information given in the list above.
  • Set a realistic expectation for when their enquiry will be addressed.
  • Suggest alternative means of interacting with us.
@res= $ 31 @type=2 @state=3 @level=3 @headline=Email: tips & etiquette. @desc=

Provide a "good email" guide, to include things like:

  • Tips for efficient use, e.g:
    • Organising messages and folders.
    • Who to include in which fields: "to", "cc", "bcc".
    • Writing good headlines and why.
    • Keeping messages simple and organised: one thread, one subject, one headline.
  • Etiquette:
    • Professional and polite.
    • Do's and don't's.

The initial thinking is that this guide would be for internal use, but it could be given a wider audience if deemed appropriate.

@res=

[27-Sep-2016] Started a mind-map to collect ideas.

[15-Dec-2017] Task suspended.

$ 32 @type=4 @state=4 @level=3 @headline=Contact form: reduce spam. @desc=

The contact form is allowing too much spam and other unwanted communications (see issue 0009). Measures need to be taken to reduce this.

@res=

[09-Apr-2018] Implemented Akismet handling to the contact form.

[14-Jun-2018] Spam significantly reduced. Task marked as completed.

$ 34 @type=4 @state=1 @level=4 @headline=Chat rooms: research. @desc=

We have successfully used Internet Relay Chat (IRC) rooms for committee meetings. The same technology may be useful as a means for our members to communicate. This needs to be investigated.

@res= $ 35 @type=4 @state=1 @level=4 @headline=Forums: research. @desc=

Discussion forums, sometimes referred to as "bulletin boards", are a useful way to communicate online. This may be a useful facility for our members. The possibilities need to be investigated.

@res= $ 37 @type=6 @state=1 @level=3 @headline=PayPal: interface: requirements & design. @desc=

Most of the website's commercial parts offer PayPal as a means of payment. This is convenient to the end user but, at present, is cumbersome for administrators to work with. Some of the reasons for this are given below.

  • The workflow to provide a new PayPal interface (e.g. an "add to cart" button) is complex and requires several people to administer. For example:

    1. The committee agree on options and prices for the new product.
    2. The treasurer logs into PayPal (as the "merchant") and uses this information to add the product and generate the markup code for the button.
    3. The markup code is copied or attached to an email message, then send to the web administrator.
    4. The administrator applies the markup to a testing area, after adjusting for site-specific concerns such as visual appearance and layout.
    5. During testing, issues are discovered which require changes to be made. Go back to step 2…
    6. No errors – the markup is deployed to the live site.

    It should be apparent that this is a very inefficient and error-prone way to work.

  • Every instance of a PayPal button on the site has its own set of complex and cumbersome markup. This is difficult to edit without making mistakes, particularly if the editor is relatively unskilled with HTML.

    The lack of consistency across the many PayPal buttons means that if something "global" should change, such as our account number or other credentials, then every single instance would have to be separately edited. Another time consuming and error-prone process.

A better system is needed and this needs to be designed. In particular:

  • The workflow needs to be improved.
  • Our software needs to support simpler and reusable markup.
  • Editing articles containing PayPal buttons should have a reduced risk of messing them up.
@res=

[17-Aug-2016] A possible way forward might be to use a PayPal API in order to provide a closer integration between their systems and ours.

$ 38 @type=3 @state=1 @level=4 @headline=Mobile devices: site appearance & usability. @desc=

The website in general, and in particular the "NAWG Classic" display theme, has been designed for desktop computers. When used on devices with smaller screens and/or resolutions, both the appearance and the usability are reduced.

Mobile devices gain popularity every day and are considered the "norm" by may users. Our website should look and feel good on all devices, e.g:

  • Desktop computers & laptops,
  • Netbooks & tablets,
  • Mobile "smart" phones.

The first step on the way to making improvements will be to research possible technologies and techniques to use.

@res= $ 40 @type=5 @state=1 @level=3 @headline=Online donations. @desc=

Provide a facility so that people can make donations online.

@res=

[27-Feb-2017] This may or may not involve Just Giving. We may simply handle this ourselves.

Task Structure

Each task has a state and a priority. The state represents it's position in the following life cycle:

The priorities are based on the MoSCoW method, and are explained below:

  1. The task must be completed for, and is critical to, the next release.
  2. The task should be completed for the next release, if time/resource allows.
  3. The task could be completed for the next release, if time/resource allows and all should tasks have first been completed.
  4. 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 ♦ Created: 30-Apr-2014 ♦ Access: public ♦ Article: site-plans-tasks ♦ Topics: old WordPress site, website, plans