3 Jan
2011
3 Jan
'11
2:59 p.m.
Hello Scott,
similar situation here - small consulting shop running a couple of XWiki
instances here since ~2 years.
Sort of love-hate relationship.
What worries me most is that's quite cumbersome yet almost impossible to
create a sleek skin without a routined designer in your team.
I am kind of envious about the sleek wordpress designs of other peoples
interactive sites where you can pick a design from the many free (and
commercial templates).
Skin creation is sort of moving target as it changes from version to
version meaning migration efforts of a customized site cannot be
predicted. Some people suggested some time ago to add support for design
creation tools like Artisteer but that's obviously not on the roadmap.
OTOH it fits in our consulting repertoire Java Spring Postgres Tomcat
and I think we will still go ahead with it.
FWIW one of our playground sites is teamsched.com the 'docs' part is
powered by XWiki.
have fun
Andreas
Am 29.12.2010 23:02, schrieb Scott Serr:
Greetings XWiki Users,
We are a small company of 3 people. For internal use and portal, I've
rolled out Trac... Then Redmine... then back to Trac. I have fond
memories of my Trac install and usage 3-4 years at "the big company" but
now that the 3 of us are on our own it doesn't seem to be that helpful.
Interconnecting Wiki, Issues/Tickets, and SCM Change Sets has great
powers in Trac. But we don't seem to be taking advantage of that now.
A year ago, I rolled out Plone for our external web. I managed to tweak
an attractive Skin/Theme. I added necessary content. Now it sits --
getting old and tired.
I'm starting to evaluate XWiki. So many options on a page is a bit
overwhelming, but other than that it looks very usable. My idea is to
merge our external web and internal portal -- so there isn't such a
distinct line drawn between our knowledge base and our customer facing
pages. I think we can manage (Trac) Issues/Tickets less formally on a
wiki page. The SCM integration was nice, but a simple Source Repository
Viewer might be all we need.
We are all familiar with Java and normally use Linux. The WebDav "fs"
features look nice.
I'm concerned about vitality. Maybe half of the "references" for XWiki
are stale -- site being dead or running something else now.
I'm concerned about security.
I'm concerned about resource footprint. (I imagine it's just App Server
+ a little, but migrating to a VPS would costly.)
Maybe I need some encouragement as I go along. :) And ideas about how
to make pages look less busy.
Thanks,
Scott
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users