I am experienced with http://symphony-cms.com/ (not symfony php
framework) it's in between a MVC framework and a CMS, extremely
abstract flexible and elegant (more then expression engine), and uses
xml transformed by xslt. Its nice backend GUI enables non-programmers
to build websites/applications with a few clicks, extensions (oo php),
and basic knowledge of xslt.
A visual overview;
http://symphony-cms.com/workspace/assets/learn/visual-overview-1258682736.png
Let me know if you have any questions, I'd be happy to setup a mock-up
site for you.


PS. Any hints about on what newsgroup/forum/community the question
about external blogging engines might be more appropriate? do let me
know.

On May 8, 1:30 am, Cédric Krier <[email protected]> wrote:
> On 07/05/10 16:24 -0700, newnomad wrote:
>
> > I assume the engine must be phyton based, otherwise I'd love to help.
>
> Not necessary. I'm not linked to a programming language.
>
>
>
> > I see where you are going, but didn't mean to criticise. I rather
> > would like to hear your opinion about wether a blog should still be
> > hosted on your domain, or can be fed by an external service. I
> > considered this path for a long time, and was pleasantly surprised to
> > find this setup here.
>
> I would like to be getting rid of any blog.
>
>
>
> > Today the blog feature of a website seems to be the only one that is
> > still internal, all the rest is api based
> > (pics by flickr, comments by disqus, docs by scribd, bookmarks by
> > delicious, feedback by get satisfaction,...).
> > What would be the reasons to keep your blog under your own thumb?
> > Blogger might not be perfect, but there migth be better platforms
> > offering i18n?
>
> Because it must not be a blog.
> We use a blog by default because we did not find a good tool.
>
> --
> Cédric Krier
>
> B2CK SPRL
> Rue de Rotterdam, 4
> 4000 Liège
> Belgium
> Tel: +32 472 54 46 59
> Email/Jabber: [email protected]
> Website:http://www.b2ck.com/
>
>  application_pgp-signature_part
> < 1KViewDownload

-- 
[email protected] mailing list

Reply via email to