* Much improved theme system.
* Redo page HTML and convert it to XHTML using CSS instead of tables – allow for much improved cross-platform support (just change CSS)
I was giving it much thouht recenty, when I was trying to convert a phpBB theme with little success.
I believe that we could overcome both issues if the crucial content-displaying pages would produce XML output formated with XSL.
Basicaly, XML contains data, and XSL fotmating.
XSL pages should be a part of theme.
That way, the designer gets all the data he needs, formats it any way he finds appropriate without modifiying core ASPX.
For example: now, if you want for some reason to disable private messages, or quotes, or you just dont want to see
other ppl's signatures or avatars, you would nead to modify your files and create de facto
your own private version of YAF.
If we use XML/XSL model, you'd just create a new theme file striped of the things you don't need.
XML + Aural CSS could also make reading the forum easier for the (visually impaired) people who use screen readers.
XML/XSL model would facilitate reading forum on other devices - primarily the mobile ones with smaller displays.
I believe most of you know what are XML and XSL. In a nutshell - XML acts like a database table in a file. It is interpreted on user's machine using the instructions from XLS file. The XSL file reads the data from XML an places XHTML tags around it.
I believe the code exists here
My two cents: (also in random order; in adittion to those already mentioned)
* to cleanse the code from hard-coded text, so the forum could be fully localised (just 3-4 places)
* export/import of dirty words filter. Also extend the filter to signatures and all the user input fields.
* minor tuning of the default forum installation settings (The avatars, smilies, No Acess Acess mask, version name...)
* Advanced search
* Turn "Host settings" to "Board settings" - now this one is big. If you need to run more (and more) separate independent boards, centralized managemend turns into a nightmare. The brute force solution of installing yet another instance of YAF could be avoided if what the settings currently located in "Host settings" could apply to single board.
* E-mail templates need to be linked to a custom board too! I was quite embarrased when a user subscribed to a topci in Board B got the email notification apparently from the Board A.
* "Ignore list" for pm molesters.
* differentiate Sticky and Announcement
* introduction of separate "display name". Appart from the fact that the username makes 50% of someones identity in the 'eyes' of the server, the separate display name would facilitate automatic generation of usernames and passwords for large amounts of users.
* Bulk import of users
* moving posts to other topics.
* fixing the minor "move topic" issues (moderators can move topics to forums they have no moderator rights; the Moved topic pointer remains even if the topic is returned to the original forum; the Moved topic pointer remains after "Show Moved Topics" is unchecked)
Regardless of the development ideas, I think we need some kind of goal - what we want YAF to be, and why are we making it. A mision statement.
If we want the fastest and the most robust board system on the net, or, if we want to have more instalations than any other board system on the net, or if we want the most disabled-friendly BS, or if we want the BS with the most supported languages on the net, will strongly influence which development ideas are more important than others.
Thank you for your time reading this.
... But trust me on the sunscreen!
There not bugs(in YAF)...it's either un-defined features or exceptions to expected behavior!!