Joomla! Discussion Forums

I'm happy with Angie and i'm impressed by you guys!
Thnks


Sven Jenzer
Access for all
Swiss foundation for technology adapted to people with disabilities

[mod note: please add signature to your profile and not to each post.]

Don't normally have my prayers answered, but ...



Flippin' excellent!

Well done.

- Vince

Thanks for this solution. Don't forget: accessibility works hand in hand with search engine optimization.

I prefer broader view: Joomla! and its community have problems, because Joomla! doesn't have high-level model (description/specification) on top of its code.
So:
- if you, as an ordinary user, don't know, why (and how) things are done, you have to figure it out yourself or to search forum (that may mislead you...) or you may try to look into code (if you understand it...). In any way, what you will find, would be private (not official) opinion of some person.
- if you feel, that something is wrong on a conceptual level (like on the level of "barrier-free, standard conform webpages") , there is no way to say: "Hey, guys, you've (probably) made an error!" - because Joomla! doesn't have any official commitments about that "barrier-free, standard conform webpages" and so "This is not a bug" 

I've personally thought about creating some list of "Joomla! architectural bugs" (I have some "not-a-bugs" in my list already...), but this thread convinced me, that we (Joomla! core team?) should start from creating "Architecture of Joomla!" document (conceptional description) , that should be superior to Joomla!'s code. Only in this case we may guarantee, that our investments in some conceptual things (like 'Joomla! MUST conform to 'AAA' standard') will be protected... This is classic and well proven approach to complex systems, what Joomla! becomes now.

Of cause, I don't mean to describe in human words (and specify) everything... but we already see areas (principles), that are important: they should be specified and, thus, protected from "code improvements" and other low-level activities...

Semantics and usage of Database schema (tables, fields, relations...) - is one of obvious areas that should be specified... not everything at once, but such "non-obvious" places, as "title-alias" in this thread - should be the first...

Could I express the idea clearly, what do you think?