Ok a bit more
Messageboards should be forums, otherwise new people will continue to ask the question "where are the spring forums?" despite having the webpage open infront of them.
So I tried to change it with the translation system. The name needs changing to content management as thats a more accurate name.
So i changed it only to be confronted with a page of text that to read I had to press ctrl+a and found I had to put in my forum login (wouldnt it be more logical to use the wiki login than the forum login?). I should never have gotten to this, it should have asked for my forum login before hand and prevented me trying to make changes if it failed.
Encasing the entire translation webpage inside one of those div boxes used on the other pages would vastly improve their readability.
Pages such as the development page or the about me page should use the wiki instead so that full wiki markup can be used along with various other wiki features.
Site: Requesting participation
Moderator: Moderators
-
Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18
About the big circus that is greatly intimidating, that's not true, I actually think the main reason for this perception is that you are very vocal about any potential disadvantage. Not that I don't appreciate your input, it has allowed me to get on top of quite a few details. But it's the extensive discussions about every nook and cranny that give that impression.
Helping with getting the site in shape is something that most people on this forum can do. And I think that once I get one or two people to contribute others will see that it's not hard, scary, technical or require the lengthy discussions like we have (had) on the forum to get things going.
Now the problem is that I need a few brave souls that are willing to lead the pack and start using the new tools and work flow.
---
More practical,
Tutorial/documentation about the translation system is still a good idea for those that can't read code but do like to know how it works technically.
It's easy to translate a string but I can write some stuff about how the system determinates the language, debug mode, what the development and empty languages are, etc.
A more general remark, I consider the graphics part of the content, more exact everything in the theme dir is content. Not that it's that important in practice but that's my definition.
I like "messageboard", but I'm not "territorial" about it
If you think that it would be a improvement then go for it.
Maybe that "content management" would fit better from the perspective of the development language, I don't know, "translation system" will do for now.
I would have to look into that "ask for login beforehand" thing.
The translation page uses the same div boxes as on other pages now.
The major disadvantage of using the wiki for the more important pages like "about" and "development" is that they can't be translated effectively. Mark-up should be done with the html pages.
Helping with getting the site in shape is something that most people on this forum can do. And I think that once I get one or two people to contribute others will see that it's not hard, scary, technical or require the lengthy discussions like we have (had) on the forum to get things going.
Now the problem is that I need a few brave souls that are willing to lead the pack and start using the new tools and work flow.
---
More practical,
Tutorial/documentation about the translation system is still a good idea for those that can't read code but do like to know how it works technically.
It's easy to translate a string but I can write some stuff about how the system determinates the language, debug mode, what the development and empty languages are, etc.
A more general remark, I consider the graphics part of the content, more exact everything in the theme dir is content. Not that it's that important in practice but that's my definition.
I like "messageboard", but I'm not "territorial" about it
If you think that it would be a improvement then go for it.Maybe that "content management" would fit better from the perspective of the development language, I don't know, "translation system" will do for now.
I would have to look into that "ask for login beforehand" thing.
The translation page uses the same div boxes as on other pages now.
The major disadvantage of using the wiki for the more important pages like "about" and "development" is that they can't be translated effectively. Mark-up should be done with the html pages.