[TYPO3-typo3org] What should happen to buzz.typo3.org?
Steffen Gebert
steffen.gebert at typo3.org
Wed Jul 25 12:44:07 CEST 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Robert,
> What do you think?
I would say that it sounds very nice! Having a blog based on Phoenix
would be great. So i would say, we stop redesign efforts for the
moment and look forward to your implementation!
Kind regards
Steffen
- --
Steffen Gebert
TYPO3 v4 Core Team Member
TYPO3 Server Administration Team Member
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
I work for TYPO3 solely in my spare time. If you think that
my work helps you running your business, you are invited to
send me a donation via PayPal to this email address. Thanks
Am 7/10/12 12:47 PM, schrieb Robert Lemke:
> Hi folks,
>
> On 28.06.2012, at 19:35, ben van 't ende <ben.vantende at typo3.org>
> wrote:
>
>> Please add your thoughts, ideas and requirements here:
>>
>> http://wiki.typo3.org/Buzz
>
>
> some more thoughts, not added to the wiki yet:
>
> I agree that we need both - a planet and a blog platform for those
> who don't have or don't want to have their own blog which is being
> aggregated (typically teams). The FLOW3 "Blog Example" _basically_
> works for me for some time now but of course lacks various
> features. However, I have some plans with this package: I recently
> started looking at converting the blog example app into a plugin
> for Phoenix. My goal is to convert my own website into a Phoenix
> site soon and make blog posts some first-class content type in the
> Phoenix content repository. From then on I also want to implement
> features I wished I had for a long time, such as support for code
> syntax highlighting and better media support (more images, videos
> …).
>
> So my suggestion is this: create a well-designed planet which
> basically aggregates any source. That planet could be the original
> planet FLOW3 app converted into a Phoenix plugin so that
> planet.typo3.org would actually become a Phoenix website. For teams
> and others interested, there will be backend logins so they can
> write blog posts (buzz replacements) which are included in some way
> or the other.
>
> What do you think?
>
> Robert
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJQD833AAoJEIskG/rSlyw4mmQH/05e2DjnI1JIzVOQufc17cmm
+FwEESx0sjO08CZJRoA94O/mai+iOvxcF5U3QHs31sB0mL4umi3COn8U18pra2VI
93XuEOUfzoP3BICDzBrZuFL3dOr/02+Q2bt6GIkZRZflGqcbyzC58qSJ88U5tbtt
pldFjQm7N1HVZwFGFRmWIiSPTeJ8V5WPpZCN3oplpW/sB5f8HpPSTGOPy1mYwX1Y
hLUiW6P4nrSwg8C1l8wZYa1rMOscf+W2/SiyZnS74dHkWwimrJSjbqjlq0+C/IXh
TdEyWmpJF1l/DLqB141WnCC0QdnGDZ9JxHmHLaZG2qMb9DCBLN2fW/3whxm1VxA=
=l/Cb
-----END PGP SIGNATURE-----
More information about the TYPO3-team-typo3org
mailing list