A lot has been said about the changes that need to be made on the
new NL. I think it is now time for NLers with some programming
experience to suggest solutions to the outstanding issues. Here
are some of the issues and their solutions from my own point of view.
Feel free to add yours.

PROBLEM 1: Usually after you click a link on a web page, that link
changes colour (eg from blue to orange or purple). The change in
colour serves the purpose of reminding the visitor that he has
visited that link when he sees it the next time. But links on the
new NL do not change colour after you click them. As a result, you
cannot tell the links you have visited from the ones you have not
since they all remain the same colour (blue).

SOLUTION 1: Resolving this problem should not be difficult. Looking
under the hood of the new NL, it appears the layout is controlled by
a CSS file named nl2.css. So to ensure that visited links are easily
identified, a visited link code should be added to nl2.css as follows:

a:visited
{
color: # FF9900 };
}

Comment: In this example #FF9900 is the colour orange. But it can be
changed to any colour different from blue.

PROBLEM 2: The boards on the new NL have only rows with no columns. For
instance, the following headers: Topic / Author / Posts / Views / Updated
are all on the same row with no columns demarcating them. This makes it a
bit difficult to scan the boards for interesting topics.

SOLUTION 2: Again looking under the hood of the new NL, it appears that
Seun and his programmers correctly used the <tr> and <td> table tags. But
it seems that since they did not invoke the width property of the <td> tag,
everything appeared in rows with no columns. If that is the case, specifying
the width for the <td> tags may resolve the problem. An example is shown below.

<table border="1" width="100%">
<tr>
<td width="47%">Topic</td>
<td width="20%">Author</td>
<td width="20%">Posts</td>
<td width="17%">Views</td>
<td width="16%">Updated</td>
</tr>
<tr>
<td width="47%">Free Vin Checks And Reports</td>
<td width="20%">inspired_m</td>
<td width="20%">2180</td>
<td width="17%">37734</td>
<td width="16%">7 hours</td>
</tr>
</table>

The HTML code above is translated below (unfortunately, the row and column
lines are not showing since this page is plain text. So I manually inserted
dividers where the columns should have been):

Topic | Author | Posts | Views | Updated
Free Vin Checks And Reports | inspired_m | 2180 | 37734 | 7 hours

PROBLEM 3: If you try to read an article on the new NL, you find out
that sentences begin from one end of the screen and stretch all the
way to the other. This is extremely problematic for PC and Laptop users.
As an article on web usability notes, “It's difficult to keep track of
a string of text that is written completely across the screen from one
end to the other. But it is easier to read the string of text if it is
only taking up part of the screen and then wraps to another line…”

SOLUTION 3: Just as in solution 2 above, specifying the width of the
<td> tags may resolve this problem. So instead of having an article occupy
100% of the screen, it should be made to occupy 60% eg <td width=”60%” Topic</td>.
For me, this is one of the most critical issues that require urgent resolution.
I deliberately wrapped my sentences after every 15th or so word to prevent them
from stretching to the end of the screen.

P.S: The examples used above have worked for me in the past. But since no
two programming environments are the same, there is no guarantee they will
work here. In that case other methods should be used to achieve the same objective.

Nice suggestions. Problem 1 and Problem 2 are by design. A fix for problem 3 was planned, but not implemented earlier because I was not experiencing any issues with the width on my laptop. The solution you proposed would not have worked, though. Fixed it just now!!

Nice suggestions. Problem 1 and Problem 2 are by design. A fix for problem 3
was planned, but not implemented earlier because I was not experiencing any
issues with the width on my laptop. The solution you proposed would not have
worked, though. Fixed it just now!!

While I don’t agree with the absence of columns on the boards, it is good
to know it was by design. Maybe it will be implemented in the future. For
now, the blazing speed of the new NL compensates for the short-comings.