|
Size: 2854
Comment: wiki-link
|
Size: 2018
Comment: Overhauled the page, removing the discussion aspects.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == A rough sketch == | = Build an Intranet = |
| Line 5: | Line 5: |
| 1. choose applications: discussions, announcements, manage info, manage documents 1. choose server: Like MS IIS WebProgramming 1. choose database, SQL Server is a good choice 1. generate content: Using Front Page works well, Python XML libraries, libraries to generate HTML 1. generate navigation buttons: GraphicsAndImages 1. test: urllib, htmllib, xmlrpc 1. use Python to automate deployment, testing, documentation 1. ???? 1. Profit! == The free way == Well, the above looks like been written by and for "Microsoft people". A potentially more stable and definitely more ''free'' way to build an intranet is like that: 1. choose applications: discussions, announcements, manage info, manage documents 1. choose server and OS: Apache on Linux 1. generate content: use a wiki engine like MoinMoin (it is like that thing you are looking at ''right now'') 1. teach yourself and people to do it the Wiki:WikiWay 1. just use it - you will see that you can do LOTS of things with that setup without needing to extend it. == The traditional way == If you need a more traditional Intranet solution, you might do it like this: |
For an intranet solution for a company or organisation of almost any size, the processes might look something like this: |
| Line 46: | Line 8: |
* Announcements - this is often needed, but where do they come from, how are they entered? * Discussions - are these really required? Do employees really get to have a say on announcements and other things? ;) |
* Announcements - this is often needed, but where do they come from, how are they entered? Consider the review workflow (if any). * Discussions - are these really required? Do employees really get to have a say on announcements and other things? What about the public? |
| Line 52: | Line 11: |
| Line 54: | Line 12: |
1. Now think about WebProgramming solutions for a moment. * Would Zope and some add-on application (like Squishdot, for example), or even a stand-alone solution do the business? * Or are you looking at some development on top of a framework? 1. Now choose a server! Apache on Linux is quite nice, but you may not need Apache if you're set on running a multi-protocol server like Zope. 1. Generate content: if you're lucky, you get to choose one of the PresentationTechnologies. And there's probably lots of existing documents lying around anyway. 1. Navigation buttons don't really merit a "top level" mention. :) |
1. Now think about ContentManagement solutions for a moment. * Would an established solution like Plone be enough, perhaps with customisation? * Or are you looking at some development from the ground up on top of one of the ["WebFrameworks"]? 1. Now choose a server! Apache on GNU/Linux is quite versatile, but you may not need Apache if you're set on running a multi-protocol server like Zope or even one of the ["WebServers"]. 1. Generate content: * A Wiki engine like MoinMoin (the basis for the Python Wiki) can provide a flexible solution, especially where the editing and review processes aren't fully defined or mapped out. * You may be extracting data from different sources and then need to present it as Web pages. Here, the PresentationTechnologies and ["Templating"] may provide good solutions. And there's probably lots of existing documents lying around anyway which can be served up as they are. |
| Line 68: | Line 20: |
| Line 71: | Line 22: |
| Any profit will come from reducing those costs which come from people shuffling paper around all day. ;) |
Build an Intranet
For an intranet solution for a company or organisation of almost any size, the processes might look something like this:
- Find out what applications you need:
- Announcements - this is often needed, but where do they come from, how are they entered? Consider the review workflow (if any).
- Discussions - are these really required? Do employees really get to have a say on announcements and other things? What about the public?
- Other information - project databases, competence databases - are these already around, or is it some Excel spreadsheet someone is keeping?
- Manage documents - are they structured or categorised in some way? What kind of documents are they?
Now think about ContentManagement solutions for a moment.
- Would an established solution like Plone be enough, perhaps with customisation?
Or are you looking at some development from the ground up on top of one of the ["WebFrameworks"]?
Now choose a server! Apache on GNU/Linux is quite versatile, but you may not need Apache if you're set on running a multi-protocol server like Zope or even one of the ["WebServers"].
- Generate content:
A Wiki engine like MoinMoin (the basis for the Python Wiki) can provide a flexible solution, especially where the editing and review processes aren't fully defined or mapped out.
You may be extracting data from different sources and then need to present it as Web pages. Here, the PresentationTechnologies and ["Templating"] may provide good solutions. And there's probably lots of existing documents lying around anyway which can be served up as they are.
Integrate into business processes - not only merits a "top level" mention, but an entire Web site devoted to it.
Test! It's nice if your WebProgramming framework allows development and testing outside a Web browser, XML-RPC, SOAP, etc. Like from the command prompt, for example.