[TYPO3-dev] Subheader (sorry, sibtitle is wrong)

[ben van 't ende]

Hi Robert,

I am sorry to see you this frustrated. As Jigal said it is a community product
and we are dependent on voluntary contributions most all of the time. Please put
your request in the issuetracker none the less so we can refer to it. I will try
and see what can be done.

gRTz

ben



On 29/08/11 15:25, Robert Wildling wrote:
> Thanks for your responses! - It seems nobody has a link at hand to a
> documentation deadling with the palettes in TYPO3 4.5... Kay?
> 
> @Jigal:
> I already fought for the subheader problem more than only once. But it is so
> hard to convince programmers, who seem to lack the possiblity to look at TYPO3
> as a USER (not PROGRAMMER), that a change would make it easier. Instead they
> point out that everything is configuarble - EASILY configurable (which is just
> not always true - definately in this case).
> 
> A lot of code for needless configurations! That's what TYPO3 in many places is!
> And no documentation for it!
> 
> I CANNOT help with documentation, if there is NOWHERE any hint that things
> changed!!! (Which should be AT LEAST in either of these files: "NEWS.txt",
> "README.txt" or "CHANGELOG").
> And even then I have to learn it first - and how shall I manage that, if there -
> again - is no documentation???
> 
> Sorry, but that's sth you core developers have to provide first, at least in a
> slim version - the very least in form of some hints!!
> 
> And I want to feel that there is an open ear for the community - which is: make
> the subheader visible, please.
> 
> Good day and thanks again for your responses.
> 
> 
> Am 29.08.11 14:57, schrieb Jigal van Hemert:
>> Hi,
>>
>> On 29-8-2011 14:41, Robert Wildling wrote:
>>> you provided an answer, where is the real documentation that deals with
>>> that problem??
>>
>> As you may have read in a lot of places there is always room for
>> contributions. The documentation team can use a helping hand or two (or
>> three).
>>
>> People can help in many areas, ranging from writing information,
>> designing things, testing if bugs can be reproduced, answering questions
>> in newsgroups, etc.
>>
>> TYPO3 is a community product, so also *you* as a part of this community
>> produces TYPO3 (not only the code, but the rest of the documentation,
>> support, etc.)
>>
>>> Please! Just make it visible!
>>
>> There is a very nice bug tracker [1][2] available where such feature
>> requests / bugs / etc. can be filed. A posting in a list will very
>> likely be forgotten and there is also no way to track progress, etc.
>>
>> [1] http://forge.typo3.org/projects/typo3v4-core/issues
>> [2] http://forge.typo3.org/projects/usability
>>
> 

-- 
TYPO3 Community Manager