Traditional homepage

[fboender]

Not exactly a feature request for MvBlog, but more a meta-feature. MvBlog doesn't have a very good homepage listing such things as Features, downloads, etc. I believe this may hold MvBlog back from becoming more popular.

[fboender]

I'm currently implementing the design I attached.

[fboender]

MvBlog homepage design v0.3

[fboender]

I've attached the latest version of the design (v0.3).

[fboender]

MvBlog homepage design and implementation.

[fboender]

I've implemented the design. It's attached to this ticket (mvblog_site-0.1.tar.bz2). You can preview it here: http://www.electricmonk.nl/temp/mvblog/

Requirements

• It requires tlib-php, which is included in the attached tarball.

Tested with

• Internet explorer v5.5
• Internet explorer v6
• Firefox / Iceweasel v2.0.0.1
• Links v1.00pre12
• Opera v9.10
• W3M w3m/0.5.1+cvs-1.968
• Lynx v2.8.5rel.1 (04 Feb 2004)

All listed browsers display the page as intented, except for the small bugs below. The various text browsers (links, W3M, Lynx) show that the page regresses nicely.

Bugs

There are a number of small bugs. Browsers mentioned refer to those listed above.

• Firefox shows a small content shift depending on the page you're looking at. This is probably due to scrolling issues. If the page becomes longer than the view of the window, the contents shifts right. *WONTFIX*
• Pages that are too small (e.g. pages that don't have enough text to fill the whole view window) show white-space at the bottom of the shadowy layed-in contents section of the page. This isn't very pretty. Not sure how to fix this, except for putting a fairly large margin at the bottom, but that's not a good enough solution. Javascript could offer a solution here. A small piece of JS could determine the height of the contents section and the height of the view window. If the first is smaller than the last, we change the hight of the contents section using javascript. Should regress nicely for older browsers. We could also just let it be ;-)
• Internet Explorer _always_ shows a small white space at the bottom of each page. I'll see if I can find out why.
• Very large text sizes (user settings) screw up the menu. *WONTFIX* Blind folkes will just have to cope.

Todo

• Content hasn't been put in yet. I'm willing to create some content for the site, but perhaps it's better if someone with more knowledge about MvBlog does it. Or we could split the work and I'll just let you know what things I can't do myself.
• Inclusion of the 'news' page so that it shows the official MvBlog blog. Perhaps we need a fix for bug #103 before we can do this.

[michiel]

(In [348]) Added website as Ferry Boender made it. The content still has to be figured out.

Re #118

[fboender]

(In [349]) Menu items are 'activated' now. When they're clicked, they stay dark. Re #118

[michiel]

(In [356]) do it right this time. It's nice to have the website running locally so you can see what you are doing ;)

Re #118

[fboender]

(In [358]) Fixed the bottom cutoff.

[fboender]

Replying to fboender:

Bugs There are a number of small bugs. Browsers mentioned refer to those listed above. * Pages that are too small (e.g. pages that don't have enough text to fill the whole view window) show white-space at the bottom of the shadowy layed-in contents section of the page. This isn't very pretty. Not sure how to fix this, except for putting a fairly large margin at the bottom, but that's not a good enough solution. Javascript could offer a solution here. A small piece of JS could determine the height of the contents section and the height of the view window. If the first is smaller than the last, we change the hight of the contents section using javascript. Should regress nicely for older browsers. We could also just let it be ;-)

Issue above has been fixed.

* Internet Explorer _always_ shows a small white space at the bottom of each page. I'll see if I can find out why.

Issue above has been fixed.

All bugs for the website have now been fixed. Only contents needs to be added. Closing this ticket.

[fboender]

Reopening this ticket for communication purposes.

[fboender]

What remains to be done?:

• About page: Features: More features.
• News page: Inclusion of MvBlog news log. (old homepage) See #103.
• Development: Page is still empty. Michiel, are you working on this?

[michiel]

Replying to fboender:

What remains to be done?: * About page: Features: More features.

Do we want to list all the features?

* News page: Inclusion of MvBlog news log. (old homepage) See #103.
* Development: Page is still empty. Michiel, are you working on this?

Yeah. I'm working on this one.

[michiel]

(In [457]) explain where development pages are.

Closes #118