Alfresco as *web* content management tool?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2007 10:36 AM
Alfresco seems to be focused on Document Management and working in groups.
I am about to make the first intranet for our organisation, and I think that the concept of 'collaborative working' is too complicated to start with.
So I would like to begin with just information and some access to files. (MSWord-templates, logo's etc. etc.) Something I would use a *web* content management tool for.
Being charmed by Alfresco, I wonder if Alfresco can serve 'simple' webpages? And if variations (contenttypes, pre-defined templates) are possible? Oh, and if users can add and edit these pages in a simple way?
Basically: is it the right tool for me?
I am about to make the first intranet for our organisation, and I think that the concept of 'collaborative working' is too complicated to start with.
So I would like to begin with just information and some access to files. (MSWord-templates, logo's etc. etc.) Something I would use a *web* content management tool for.
Being charmed by Alfresco, I wonder if Alfresco can serve 'simple' webpages? And if variations (contenttypes, pre-defined templates) are possible? Oh, and if users can add and edit these pages in a simple way?
Basically: is it the right tool for me?
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2007 04:31 PM
Alfresco seems to be focused on Document Management and working in groups….
Basically: is it the right tool for me?
That's funny. My initial response is that Alfresco seems to be focused on Web Content Development. I'm finding some difficulty with it as a Document Management tool. Yet I have the same question as you - is it the right tool?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2007 01:03 PM
wernert,
I don't know what version of Alfresco you're on (an early pre-release?),
but we are able to virtualize "simple" static websites, as well as
more sophisticated things like webapps.
To demonstrate this, suppose we have a static website
in your UNIX or windows native file system. Let's say
this is in a directory called "xxx", and it just has one
file called "index.html". This is about as simple of
a website as you can get:
% mkdir xxx
% cd xxx
% echo "hello world" > index.html
Now, to import this website into Alfresco, you've got to bundle it up
as a war file. That's quite easy:
% jar -cfv example.war *
Just for the fun of it, let's see what's in that war file:
% jar -tvf examle.war
0 Thu Mar 22 12:51:20 EDT 2007 META-INF/
71 Thu Mar 22 12:51:20 EDT 2007 META-INF/MANIFEST.MF
12 Thu Mar 22 12:40:50 EDT 2007 index.html
Ok, now you've got a war file that contains the website you want
to import. Again. this war file (example.war) could have contained
lots of files & directories filled with servlets, JSPs, filters, and so
on, or it could have been something utterly mundane like a static
website. In the end, it's a war file – that's all.
So now we have our war file, and it's time to import it using
"bulk import". The fastest way is to just go into the staging
sandbox of a project you've created, click on the 'create' menu,
then select "bulk import". You'll be prompted to find the war file
you just created in your native UNIX/Windows file system.
Do the import, and that's it!
Assuming your virtuaization server is running, you can click on
the icon that looks like an eyeball (i.e. "preview") and you'll see
your website virtualized.
Put another way, just because you're importing a war file doesn't
mean the data *within* the war file has to be a full-blown webapp.
Simple websites can be virtualized too!
You can edit your html pages in a variety of ways.
For example, what *I* prefer doing myself is using the CIFS
projection, rather than web-based tools for that (this allows
me to use thick native apps directly rather than importing/exporting
via web interactions). However, if you've got a huge company
the web interface is probably the best way to restrict access.
What's best for you is your call… but if you're really up for
something drop-dead simple, the CIFS projection is calling
your name!
I don't know what version of Alfresco you're on (an early pre-release?),
but we are able to virtualize "simple" static websites, as well as
more sophisticated things like webapps.
To demonstrate this, suppose we have a static website
in your UNIX or windows native file system. Let's say
this is in a directory called "xxx", and it just has one
file called "index.html". This is about as simple of
a website as you can get:
% mkdir xxx
% cd xxx
% echo "hello world" > index.html
Now, to import this website into Alfresco, you've got to bundle it up
as a war file. That's quite easy:
% jar -cfv example.war *
Just for the fun of it, let's see what's in that war file:
% jar -tvf examle.war
0 Thu Mar 22 12:51:20 EDT 2007 META-INF/
71 Thu Mar 22 12:51:20 EDT 2007 META-INF/MANIFEST.MF
12 Thu Mar 22 12:40:50 EDT 2007 index.html
Ok, now you've got a war file that contains the website you want
to import. Again. this war file (example.war) could have contained
lots of files & directories filled with servlets, JSPs, filters, and so
on, or it could have been something utterly mundane like a static
website. In the end, it's a war file – that's all.
So now we have our war file, and it's time to import it using
"bulk import". The fastest way is to just go into the staging
sandbox of a project you've created, click on the 'create' menu,
then select "bulk import". You'll be prompted to find the war file
you just created in your native UNIX/Windows file system.
Do the import, and that's it!
Assuming your virtuaization server is running, you can click on
the icon that looks like an eyeball (i.e. "preview") and you'll see
your website virtualized.
Put another way, just because you're importing a war file doesn't
mean the data *within* the war file has to be a full-blown webapp.
Simple websites can be virtualized too!
You can edit your html pages in a variety of ways.
For example, what *I* prefer doing myself is using the CIFS
projection, rather than web-based tools for that (this allows
me to use thick native apps directly rather than importing/exporting
via web interactions). However, if you've got a huge company
the web interface is probably the best way to restrict access.
What's best for you is your call… but if you're really up for
something drop-dead simple, the CIFS projection is calling
your name!


Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-23-2007 07:23 PM
Hi John,
I have got a static site and an externally created JSP site to work in preview. I was also trying to use cifs for modifying the html and other JSP files already checked in via bulk import. Basically trying WCM on an ongoing basis.
Here is how I used CIFS.
- Connected to CIFS using \\servername_a\AVM (basically mapping to a virtual server)
- For a virtual server mapped drive no checkin/checkout is provided as in normal Alfresco cifs
mapping.
- Also once you are mapped in cifs there is no security. Basically having logged as me shows me the staging sites for all other users as well and allows me to change their files.
- Changing the file in Mapped drive:\Myproject\HEAD\DATA\www\avm_webapps\ROOT allows me to change any file.
- Once you save it, you can go to the Alfresco UI in your sandbox and submit the changed file again. When approved by the workflow process it creates ia new version.
- So, once the file is updated and saved and submitted to the workflow, versions/rollbacks do work.
- The issue about using CIFS is security for the virtual server. If there are multiple users I could change the files for those users as well.
When you mean "Use CIFS projection" is it this way or some other way? If it is this way then what does one do about security. Even if it is not this way then, any other user can still use this backend approach and change other users files.
thanks,
I have got a static site and an externally created JSP site to work in preview. I was also trying to use cifs for modifying the html and other JSP files already checked in via bulk import. Basically trying WCM on an ongoing basis.
Here is how I used CIFS.
- Connected to CIFS using \\servername_a\AVM (basically mapping to a virtual server)
- For a virtual server mapped drive no checkin/checkout is provided as in normal Alfresco cifs
mapping.
- Also once you are mapped in cifs there is no security. Basically having logged as me shows me the staging sites for all other users as well and allows me to change their files.
- Changing the file in Mapped drive:\Myproject\HEAD\DATA\www\avm_webapps\ROOT allows me to change any file.
- Once you save it, you can go to the Alfresco UI in your sandbox and submit the changed file again. When approved by the workflow process it creates ia new version.
- So, once the file is updated and saved and submitted to the workflow, versions/rollbacks do work.
- The issue about using CIFS is security for the virtual server. If there are multiple users I could change the files for those users as well.
When you mean "Use CIFS projection" is it this way or some other way? If it is this way then what does one do about security. Even if it is not this way then, any other user can still use this backend approach and change other users files.
thanks,
