Hi You could take a look a open atrium (http://openatrium.com/)

On Tue, Feb 12, 2013 at 12:27 PM, Dan Katz dan.katz@electricsage.comwrote:

Domain is probably a bad idea for an intranet, as it's likely that there are significantly different business requirements from between a public facing site and the intranet:

-different users -different content -different access controls

Domain module is great when you have multiple sites that need to share some content, but for an intranet I would recommend a standalone drupal instance or if that wasn't possible a multisite configuration with your public facing site.

I've seen many intranets built on the organic groups solution (http://drupal.org/project/og). Other than that, stick to the basic Drupal building blocks - content types, views, blocks, etc... I like context (http://drupal.org/project/context) for defining "landing pages" and laying out your main pages.

Good luck!

On Tue, Feb 12, 2013 at 11:42 AM, Earnie Boyd earnie@users.sourceforge.net wrote:

...

Maybe http://drupal.org/project/domain?

Also go to http://drupal.org/project/modules and search for domain, there are quite a few modules.

Earnie

On Tue, Feb 12, 2013 at 11:04 AM, Rasmus Falkenberg rf@humac.com

wrote:

...

...

Hi all

I have been told to establish a new intranet for the company that I

work in

...

...

and since we already have Drupal running our website/online store I

think it

...

...

would make sense to have it run the intranet as well.

I have been researching the WWW and the Drupal community to find out

how to

...

...

get started. Perhaps there is a suitable module for this that we can

easily

...

...

add to a stand-alone Drupal installation and build from there?

What is the most common way to get started with building an intranet in Drupal?

Thanks in advance Rasmus F.

-- [ Drupal support list | http://lists.drupal.org/ ]

-- Earnie

-- https://sites.google.com/site/earnieboyd

[ Drupal support list | http://lists.drupal.org/ ]

-- Dan Katz

http://www.linkedin.com/in/mtndan

[ Drupal support list | http://lists.drupal.org/ ]

I agree. An intranet is simply a network location accessible only by the people within the firewall. Typically the users access sites on it using an IP address. But no matter how they access it, a Drupal site on the intranet would run just like a Drupal site on the Internet. There need be no difference other than access, unless the content requirements etc. are different for the site. It is not much different than having a local version of a Drupal site running on your own machine, other than other people within the firewall can access it.

On Feb 12, 2013, at 2:10 PM, Miles Fidelman mfidelman@meetinghouse.net wrote:

Kind of depends on what you mean by "intranet," but a Drupal instance, with access limited only to employees (and maybe business partners), sounds a lot like an Intranet to me. For internal access only, put it behind a firewall. For finer grained access control, and/or for remote/outside access, require log in for all access.

Beyond that, it's more a matter of what functions you want.