intranet

Associate
Joined
6 Jul 2007
Posts
431
Location
Notts, UK
Whats the best way of developing an intranet?

How is an intranet built and how is it hosted?

Is it better to use/buy a ready made template and adjust it? if so what do you recommend?


TIA
 
Two options really....

1. Host it on a standard web host but protect it with a password.

2. Host it on a computer on your companies network, no passwords.

TWO is best for security of private data, ONE is better for home users.

Depending on your company size a old P2/P3 computer with a small fast hard drive and plenty of memory should be fine install Debian on it, with Apache2, PHP 5, MySQL5 and your set, tbh.
 
Right, for now you should ignore hardware/software/hosting issues and work out what you actually want the intranet system to do. Do you want it to help workflow, track projects, track customers etc...

Once you have a clear idea of what purpose it needs to perform, have a look and see if there's any software out there which is fit for purpose. If not, you'll need to develop your own. This is when you need to speak to someone who knows how to develop an intranet system really, don't ask on a forum or you'll get replies like the one above :p

One thing I'd really reccomend though is not trying to cut corners while building the intranet system. These things have a habbit of growing in to big systems which the whole company relies on. You really don't want that sort of thing cobbled together by someone inexperienced as it'll only get harder to maintain and add new features to. You certainly don't want it running on some old computer you were using as a foot rest either ;)
 
Right, for now you should ignore hardware/software/hosting issues and work out what you actually want the intranet system to do. Do you want it to help workflow, track projects, track customers etc...

Once you have a clear idea of what purpose it needs to perform, have a look and see if there's any software out there which is fit for purpose. If not, you'll need to develop your own. This is when you need to speak to someone who knows how to develop an intranet system really, don't ask on a forum or you'll get replies like the one above :p

One thing I'd really reccomend though is not trying to cut corners while building the intranet system. These things have a habbit of growing in to big systems which the whole company relies on. You really don't want that sort of thing cobbled together by someone inexperienced as it'll only get harder to maintain and add new features to. You certainly don't want it running on some old computer you were using as a foot rest either ;)

I think the problem is we need some more information from the OP because your perfectly right, except if its a small company, then just using a software platform which is expandable would be best, i.e. a Wiki tends to be good or a CMS like Drupal or Wordpress etc...

I personally was thinking of a small business in mind, in which case a small web server is fine, but your thinking medium/big business so a proper server would be better especially like you said if it takes off.
 
I think the problem is we need some more information from the OP because your perfectly right, except if its a small company, then just using a software platform which is expandable would be best, i.e. a Wiki tends to be good or a CMS like Drupal or Wordpress etc...

I personally was thinking of a small business in mind, in which case a small web server is fine, but your thinking medium/big business so a proper server would be better especially like you said if it takes off.
I'd say any business big enough to need a custom intranet system is big enough to need it built well ;)

Most 'intranet' systems smaller than this tend to be either simple information pages which could be handled by a simple CMS as you said, or simple document stores which could be solved with a network share and sensible file names, there is good web based software that handles documents well though.
 
We use a system called Trac - it ties very neatly into subversion (we're a software house) and we can log work tickets as well as it having a wiki.

The subversion logs can auto-link to wiki pages and tickets by use of wiki-style formatting, so for us it's very useful.

My last company just had some html pages put onto a network share and pointed the browsers at it, it worked OK but it wasn't brilliant - all that was really on it was the procedural documents for emergencies and the like.
 
Back
Top Bottom