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.
This article sets out the future plans for this website, as far as they are known.
Older versions of the website (prior to release 2.4.1, 20-Mar-2014) had a number of shortcomings and limitations. We plan to address these and make improvements.
↑ Time Line
Incomplete at present, but…
Here are the planned website releases, along with some major events, shown in reverse chronological order.
|Date||Release||Event / Notes|
|18-Oct-2017||2.8.0||Front page improvements.|
|05-Jun-2017||2.7.10||Displaying articles in a category no longer includes sub-categories.|
|13-Jan-2017||2.7.9||Handling for restricted areas (prototype).|
|11-Oct-2016||2.7.8||Changes to clarify display of multiple article sets.|
|04-Sep-2016||AGM & committee meeting.|
|13-Jul-2016||2.7.7||Introduced writers' resources area.|
|10-May-2016||2.7.6||Bug fixes and software updates.|
|22-Dec-2015||2.7.4||Social media integration. Logo changed.|
|14-May-2015||2.7.1||Software packages update.|
|10-Apr-2015||2.7.0||100 Word Mini-Tales competition.|
|31-Mar-2015||2.6.4||Update core & library software.|
|02-Mar-2015||2.6.3||Tabbed display on front page.|
|04-Feb-2015||2.6.2||Migrate the entire site to a new hosting company.|
|12-Nov-2014||2.6.1||Improve content filters.|
|29-Aug-2014||Annual writing festival (Warwick).|
|12-Aug-2014||2.6.0||Utilise dynamic sidebars and widgets features.|
↑ Future Releases
Planned New Features – General
- Make use of WordPress theme customisation features, to make cosmetic changes easier and avoid the need for code changes.
- Support for writing articles using markdown.
Planned New Features – Appearance
Add new components to the side bar, such as:
- A PayPal widget to allow subscription fees to be paid.
Planned Changes – Technical
Make the "NAWG Classic" WordPress display theme into a child theme of "K-Lattice".
This will pave the way towards some of the new features, including:
- Support for dynamic sidebars and widgets.
- Theme customisation support.
Improve the content filters that are used by WordPress.
Raw content is stored in and retrieved from the back-end database. Before that content is presented on the web pages, a number of filters are applied. The WordPress default filter configuration is unsatisfactory for a number of reasons, so we aim to improve this situation.
- Improve auto-paragraphing and line break display. To be honest, the native WordPress handling of these things is a right pig's ear, often resulting in invalid mark-up and mangled content layout. We intend to clean this up by replacing it with a simple and robust system.
Where possible, corrections for bad mark-up will be applied.
Bad mark-up can often be generated, for example, by pasting data from Microsoft Word into the post or comments editors.
Particular things to address are:
- Invalid element names, attributes and values.
- Elements not properly closed, or incorrectly nested.
Superfluous elements and attributes,
e.g. useless empty
<span></span>constructs, or useless empty attributes such as in:
Apply corrections to incorrectly formed URIs (internet and e-mail addresses). Here are some examples:
Bad URI Description Corrected URI http//person.blogspot.com/about-me Missing separator between scheme and domain name. Add colon after scheme name. http://person.blogspot.com/about-me mailto://firstname.lastname@example.org Incorrect separator between scheme and domain name. Remove double-slashes. mailto:email@example.com
Replacing UTF sequences, international text, and other special characters with named entities, for better cross-browser portability.
The text "the renewal fee remains at £40" would be encoded as: "
the renewal fee remains at £40", rather than having the pound symbol hard-coded.
Some of the filtering will need to be done each and every time pages are displayed. Other filtering need only be applied when an article or comment is submitted or edited.
|Author:||Kevin Machin||Date:||April 11, 2014 9:03 pm|
|Comments:||0 – permitted||Article:||2785 – public|