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.
The plans in this document are of a more technical nature. It's all about the behavioural and technical aspects that provide support for the website's content and facilities. #### Privacy & Security One of the ideas for the site, is to provide areas that are accessible only to NAWG members. For this to work, there will need to be sufficient levels of security and privacy. Ideas for this include: * User accounts with passwords. * Role-based permissions & privileges. * Multiple levels of access. Other security related plans may include: * Using secure connections with HTTPS. * Anti-spam measures for commenting and other user input. #### People Database In order to support other plans, such as the revamping of the [who is NAWG?](/?cat=15) area, we plan to develop a **people database**. Initially, this will include the following: * NAWG president and patrons. * Board of trustees, committee members and executive officers. * Volunteers and regular associates. Later, we might extend this to include: + Festival tutors, past and present. + Friends of NAWG -- see [old page](/?p=232). The design of the database is yet to be done, but will probably include the following information for each individual: * Name. * Official titles. * Roles. * Contact details. * Photograph. * Mini-biography. Not all of the above information will be public, as we will respect each individual's right to privacy. #### Articles & Editing ##### Temporal Content Certain types of web content ought to have a well-defined and finite lifetime. A good example of this is paid-for adverts that expire after the paid period is up. Developing software features to handle temporal content will make this easier and more automated, cutting down on the amount of necessary manual editing work. ##### Markdown for Content For those who don't know, *markdown* is a lightweight "language" for writing and formatting web documents. It has many advantages over traditional *markup* languages (such as HTML). To name a few: * It's human readable. This document you're reading now is in unconverted markdown. * It's much easier to create, edit and maintain documents using markdown. There's a [Wikipedia page](http://en.wikipedia.org/wiki/Markdown) that has a good summary. We plan to develop a markdown based infrastructure for our content. This will: + Remove the "barrier to entry" for new content editors, that is HTML. + Allow useful features, such as automatically generated tables of contents. + Reduce the size and complexity of our existing content. HTML, as well as being difficult for non-programmers to work with, takes up much more space than markdown. ##### Automatic Table of Contents Generation Useful for longer articles. This would allow you to jump around on the page, rather than relying on the scrolling bars. The headings within the article are used to make the links within the TOC. #### PayPal Integration At present, the site has various PayPal buttons scattered about the pages and articles. These have been individually coded on an as-needed basis, so there's virtually no consistency nor cohesion between them. We plan to address this, in order to: + Make it easier for content editors to add or modify PayPal controls, without the need for lengthy HTML code fragments. + Give all the PayPal facilities a consistent look and feel. In order to do this, some research will be necessary. In particular, the various Application Programmer's Interfaces (API) will need to be studied.
|Author:||Kevin Machin||Date:||September 28, 2015 9:05 am|
|Responses:||0 – open||Article:||210 – published|