At 4:22 PM + 9/5/07, Steve Potter wrote:
> >
>> Try coding each module as a Django template tag.
>> Then, create a template that returns an html fragment rather than a
>> full html page.
>> Associate each rendered template with a specific URL.
>> Perhaps something like:
>>
On Sep 5, 11:31 am, "Dorai Thodla" <[EMAIL PROTECTED]> wrote:
> Steve,
> This is a great idea that may work as a migration strategy from lot of other
> portals/content management systems or even websites. I wonder whether there
> is some wikispace where we can preserve migration strategies.
>
>
>
> Try coding each module as a Django template tag.
> Then, create a template that returns an html fragment rather than a
> full html page.
> Associate each rendered template with a specific URL.
> Perhaps something like:
> mysite.com/components/module1.html
> In Joomla, create a plug-in
At 4:59 AM + 9/5/07, Steve Potter wrote:
>... you have many different modules, each of them being a separate
>application that
>functions independently of the others, but they are all displayed on
>one page.
>I want to be able to convert these modules one by one without having
>to replace
>
> You can use url rewriting to point your users at the old site while you
> code up the new one. Apache's mod_rewrite is pretty well documented.
> You would capture incoming URLs that aren't yet in your new Django app
> before they get to it, sending them to the legacy app instead.
>
>
On Tue, 4 Sep 2007, Steve Potter wrote:
> I have an existing website currently built with Joomla. I would like
> to convert it to a custom designed Django site. The problem I am
> running into is that I will not be able to do it all at once. To
> start with, I would like to take some of the
I have an existing website currently built with Joomla. I would like
to convert it to a custom designed Django site. The problem I am
running into is that I will not be able to do it all at once. To
start with, I would like to take some of the business logic and form
process and move to
7 matches
Mail list logo
