University Web Developers

University Web Developers

Hi, we're nearing the QA phase of our DotCMS implementation on campus. Our web department is just me and one other person. We're semi-technical & soon to be learning a lot more. I'm planning the next leg of this project and I'm wondering about other people's experiences. I'm just wondering if anyone has any great strategies for getting campus users working in the system? Who did you start with? Did you plan everything in detail or just dive in fearlessly? What did you do that you wish you had done differently?

I'm really excited and simultaneously a little overwhelmed. Any general thoughts or feedback about the time when you were getting started with DotCMS would be great.

Share

Reply to This

Replies to This Discussion

I feel your pain. Our web office is just me, and I am responsible for pretty much EVERYTHING dotCMS related (though I did manage to farm out the user training at least, to my boss and her assistant, heh). It sounds like you're starting a lot like I did. When we started, I had experience with small PHP CMSs, but never something of this scale and power, and I'm certainly no Java developer. But I just dove in head first, and didn't have any problem swimming in the deep end. It's really a marvel of a system in terms of learning curve.

With users, we tried to start with a small core group of more savvy user first. We also have a person in each college responsible for all their departments' web sites, so training those users is really up to them (as is deciding if they want the department to have any control over the content). I make it a point to never show people things that they don't need to know, and I try to make good use of groups to control their back end interfaces. YOU ABSOLUTELY MUST SHOW PEOPLE THE "PASTE FROM WORD" FEATURE IN TINYMCE. I cannot stress that enough, if your users are anything like ours. Tell them, tell them again, and remind them frequently.

Honestly, our process hasn't worked terribly, and we didn't do a lot of planning with it. As I mentioned, we just started with savvy users, and some of them are happy to help others. Then we started working our way through offices. Usually the smaller ones first, moving on to bigger ones. As we hit bigger ones, we concentrate on the most important info, and use redirects to pick up requests for old pages and forward them on to the old site until everything is converted. I've been in the process of making little tutorial videos to help refresh people on common tasks. I tend to NOT show people macros, unless I know they can handle it. As easy as macros are to use, if they can't handle basic HTML, I have no reason to believe they can handle macros, so save on the confusion later and just avoid it. Tell them YOU can do it for them in a jiffy. Odds are, the time it takes you to do it right will be less than the time wasted between them trying to do it themselves, and the support you end up giving to fix it later.

As we get further in the process, I print out my URLRewrite.xml file (where I manage redirects to the old server for unconverted areas) and see what is and isn't done. I just start cherry picking from there to see which ones we can bang out the fastest.

I also try to make myself very available to help out other dotCMS users, so feel free to contact me directly if you ever have any questions or need some help.

Reply to This

Thanks so much for the advice. It all makes a lot of sense & I was already thinking along these lines for some of my strategies so that makes me feel good about where I am. Good advice about not letting people know more than they need to. I've already made a misstep in that area. :)

Reply to This

Hi Jody! Nice to meet you! I know exactly how you feel.

I, myself, am a probie on the dotcms. Our college recently went through a Web redesign this past summer. I am semi-technical too (I originally worked in public relations before making the switch over and becoming their new Web Specialist).

I am pretty much a one person crew, and have been given the charge to train all identified dotcms users on campus. Before I began training groups (am still training, ugh!), I wrote out a basic Web Policy Guidelines and Procedures and a Basic Training Agenda. That way they have a "cheat sheet" of how to perform certain tasks on the dotcms after our training and also, I have their signatures, agreeing to the policies.

If I had to do anything over again, it would probably be training folks earlier. Now that the semester is in full swing, I am having a hard time getting folks to commit to a set date/time to be trained.

Best of luck to you! Stay in touch!
Courtney

Reply to This

RSS

Elsewhere

Latest Activity

Employment Opportunities is one of the 12 main navigation links in the header of our Web site template. Therefore, it appears not only on the home page, but on almost every page of our site.
14 hours ago
Erik Espana, Rick Gould, Gloria Edwards and 3 more joined University Web Developers
14 hours ago
I just opened my account jfduguid (at) googlewave
15 hours ago
Off topic, but the hide/show social media icon bar on your site is very well done.
15 hours ago
Global footer that says "We're Hiring". It is one of our top visited pages.
16 hours ago
Thanks for the feedback - the backstory here is that our HR office has requested to be on the homepage, but the college's Web Advisory committee has been refusing the request. I thought a link in the global footer would be a nice solution, so I'm ...
16 hours ago
"Employment at SJC" is a link in our footer that is on every page, including the homepage. We also have a prominent link in the navigation one level down under our "About Us" section. It's one of our top hits also.
16 hours ago
Share your experiences using OmniUpdate CMS
16 hours ago
We have an Employment link in the footer of every page, including our home page.
16 hours ago
OmniUpdate’s CMS business is booming and we are looking for several Web Services Technicians. Help us grow our team.
18 hours ago
Yes, we list it on the homepage. Our HR person requested this as part of our redesign about a year ago and I thought it made sense.
18 hours ago
We have a "Jobs" link in our global footer.
18 hours ago
We do have a link at the bottom of the home page in the footer. We have gone one step further however, because the footer is a common include used across everyone of our pages that is in our new template. We have about 75% of our pages using it. I...
18 hours ago
shannon johnson added a discussion
hello uwebd! we're hiring a developer here @ Rensselaer's Experimental Media & Performing Arts Center in Troy, NY. www.empac.rpi.edu. We started this search last year but then went into a hiring freeze, and now have a window where we're quickly tr...
18 hours ago
I can tell you how we do it- I work in marketing on the web team. We control the front page. I'm the content person, so I make a lot of those judgment calls. For our specific design (www.oc.edu), there are a few guiding principles. For the top ...
19 hours ago
joleflow @ googlewave.com
19 hours ago
Georgiana Cohen added a discussion
What is the editorial process for your university homepage? Specifically, I'm curious about: - what type of content gets featured (news, events, blogs, social media, contests, etc.) - number of people making decisions about what content gets feat...
20 hours ago
It is a link on our homepage and is one of our top hits as well.
20 hours ago
We don't, but it is one of the first menu items from the top drop down menu. I would say it is worth it, especially if you are a large school. We're a small school (for example at this time we have 5 only openings on campus), but that page is one ...
20 hours ago
20 hours ago

An adjunct to UWEBD. UWEBD has been in existence for more than 10 years and is the very best email discussion list on the Internet, in any industry, on any topic.

About

© 2009   Created by Mark Greenfield

Badges  |  Report an Issue  |  Privacy  |  Terms of Service

Sign in to chat!