[TYPO3-typo3org] What should happen to buzz.typo3.org?

[Stephen Bungert]

I don't like creating the whole output in TypoScript. I would much rather 
have an html template that I can edit. It took ages to get the blog looking 
like I wanted it to. Most of the time was taken up just trying to find where 
in the TypoScript that I should make the changes. If it had had an html 
template I could have be finished in 10th of the time.

Can you imagine if tt_news didn't have an html template, and you had to do 
everything through TS? that's what it's like using t3blog.


"ben van 't ende" <ben.vantende at typo3.org> schrieb im Newsbeitrag 
news:mailman.1.1340802693.4762.typo3-team-typo3org at lists.typo3.org...
> Hey,
>
> Templating in typoscript is fine. It depends on how you do it. Do you mean
> t3blog is hard to handle?
>
> gRTZ ben
>
>
>
> On 27/06/12 14:38, Stephen Bungert wrote:
>> I tried this once... never again.
>>
>> The template is created in TypoScript...
>>
>> "ben van 't ende" <ben.vantende at typo3.org> schrieb im Newsbeitrag
>> news:mailman.1.1340798682.23741.typo3-team-typo3org at lists.typo3.org...
>>> Heyla,
>>>
>>> I do agree that we still need both. Not everyone has a blog that can be
>>> aggregated and we do have the team blogs as well that need their home.
>>> Thanks to
>>> the others in this thread for suggesting software. Snowflake developed
>>> t3blog,
>>> which should perfectly do the job for Buzz I would think. Anyone have
>>> experience
>>> with that?
>>>
>>> gRTZ ben
>>>
>>>
>>>
>>>
>>> On 27/06/12 11:35, Fabien Udriot wrote:
>>>> Hello,
>>>>
>>>>>> I would prefer having a "better buzz" over private blogs and an
>>>>>> aggregator. As Steffen mentions, Buzz posts are often information 
>>>>>> about
>>>>>> new TYPO3 stuff that are more interesting for devs than for the whole
>>>>>> world.
>>>>>
>>>>> +1
>>>>
>>>> Can't we have both actually?
>>>>
>>>> A blog system where people could buzz without the need to have / 
>>>> maintain
>>>> their own blog system *and* a TYPO3 Planet where feeds get aggregated 
>>>> and
>>>> where people can push an "external" blog entry to be listed there. I 
>>>> find
>>>> that a Planet would bring the benefit to collect all the noise around
>>>> TYPO3
>>>> and therefore would increase visibility.
>>>>
>>>>> Isn't it funny that most samples for Extbase and FLOW3 were about a 
>>>>> blog
>>>>> extension but there is no well working blog solution for TYPO3 ?
>>>>
>>>> Isn't it the occasion to properly finish the (FLOW3) blog plugin if 
>>>> there
>>>> are
>>>> enough good souls around. I would prefer that over WP, personally. But
>>>> that's
>>>> a matter of man power eventually.
>>>>
>>>>>> When we aggregate blogs, we may have posts from some very cool blogs,
>>>>>> but
>>>>>> we will also have posts like book announcements, "I found a new and
>>>>>> very
>>>>>> cool TypoScript snippet", off-topics that have less relevancy than 
>>>>>> Buzz
>>>>>> posts.
>>>>>
>>>>> but a book announcement is also something which interests me as core 
>>>>> dev
>>>>> as
>>>>> there are alreays people asking me "which book should i use" and the
>>>>> answer
>>>>> "i read the code" isn't very helpful ;)
>>>>
>>>> True that a Planet might have less flavour and focus that a buzz. 
>>>> That's
>>>> because two independent systems with different needs in mind would make
>>>> sense.
>>>>
>>>> Cheers,
>>>>
>>>> Fabien
>>>>
>>>
>>> -- 
>>> TYPO3 Community Manager
>>>
>>>
>>
>>
>
> -- 
> TYPO3 Community Manager
>
>