I'm intrigued by the Prosepoint Installation. I am overseeing the construction of a new drupal based site for my organization. The organization has a magazine that it produces (in print now, expanding to web) -- but is only a part of its work. I've been thinking about how to have a magazine and an organization portal (with lots of drupal-like functionality) as part of the same website.

I'm thinking of:
www.organization.org
www.magazine.organization.org

With Drupal 6.6 on the first and Prosepoint on the second. They'd share users, and perhaps even content, if possible -- but the layouts and functionality would differ. We'd also use the Prosepoint site for article revisions, drafting, approvals, etc.

Does this make sense? Can I have a subdomain run off a different installation profile?

Do you have better ideas of how to integrate the two?

Comments

bengtan’s picture

bengtan commented

Hi,

Interesting use case. It depends a lot on the details, but I'll answer as best as I can.

> share users, and perhaps even content

If sharing by running both sites off the same database, then I think you'll have a clash between vanilla D6 and ProsePoint. For example, the extended_status field in stories would have no effect in D6, which means you lose some of the workflow capability. Theoretically, however, you could customise D6 to have some of the functionality of ProsePoint so that both sites can operate from the same database, but it might not be feasible in practice.

Alternatively, you could set up some sort of mechanism whereby both sites operate from separate databases, but content on the ProsePoint site gets pushed to the Drupal site. Again, it'll come down to the specifics of the requirements.

Or, you could run the domain site as a ProsePoint installation profile, but then disable the ProsePoint specific bits you don't want. Of course, this would no longer be a freely supported use of ProsePoint, but we could support it commercially, I guess.

> Do you have better ideas of how to integrate the two?

Not presently (other than what I've said above). Sorry for not being able to provide a definitive answer. Something like this needs consideration and evaluation of potential solutions in light of the requirements, and that's probably outside the scope of this issue.