You just put the finishing touch on your Drupal site, all the images are just right, the calendar feed has your events displayed and every bit of content is informative and engaging. It sounds great, but here are some things you should know about live sites and some checks you should do for your site before deployment.

  • Links, images and navigation, these are the cornerstones of a good site. We have some ‘best practices’ items you should check before pushing your site live.
  • Menus – part of the navigation system your visitors depend on in order to find relevant content on your site.
  • Brand Identity Guidelines for OSU web content. Does your site measure up to University expectations, we’ll show you how to find out.
  • Do you have contact information? It can be very aggravating if a user doesn’t have a way to reach out to someone in order to have a question or concern addressed.
  • What do you need to do after your site goes live? Yes there are things you should check after your site is moved to production.

All of these items and others are covered in detail at http://oregonstate.edu/cws/training/book/drupal-deep-dive/osu-drupal-site-procedures/drupal-deployment-checklist.

 

CWS is happy to present Doug Fir, the latest theme in the OSU Drupal 6 distribution.

the web, table, and phone views of doug fir
Doug Fir – What Responsive Looks Like

Designed by WebComm and engineered by Central Web Services, Doug Fir has been developed similarly to OSU Standard in regards to configurable theme options, integration with Google Analytics, and layout regions, but it sports a fresh, clean look which is consistent with the default theme that will be supplied in our upcoming OSU Drupal 7 distribution.

Using Doug Fir provides us with two distinct advantages:

  • It allows OSU Drupal 6 sites to look like OSU Drupal 7 ones from the front end.  What this means is that you don’t have to panic if you’re not ready to roll into OSU Drupal7, instead you can just easily switch the theme out by following the Switching to Doug Fir instructions found in our CWS Training site. (We realize that sometimes these things can seem tricky.  If, after reading over the instructions, you still feel nervous about making the switch, just submit a Help Ticket to us and we’ll be happy to lend a hand.)
  • The bigger advantage to using Doug Fir lies in the fact that the theme is responsive.  What this means is that the display will automatically adjust, as needed, to fit the screens on your mobile devices.  It doesn’t matter if your device is a tablet or smartphone, the responsiveness of Doug Fir will give you a nicely formatted appearance.

Want to see for yourself how a responsive theme works?  It’s really easy to do.  Just go to a site with a responsive theme and resize the width of your browser window.  You’ll immediately see how the layout responds.  Take a look at a couple of early adopter sites who so graciously assisted us in the development of this theme: OSU Admissions and TAC (Technology Across the Curriculum).

So let’s talk Drupal 7, and some bits and bytes about Drupal in general.  Central Web Services maintains a central Drupal installation.  Like any piece of software, it has multiple versions.  Drupal 5, 6, 7, and 8 which is in development.  The CWS stable version is Drupal 6.  Drupal 5 is no longer supported.  Right now we are getting numerous requests for Drupal 7.

We want to let you all know that we are actively working to get Drupal 7 tested, documented, and functional for the needs of OSU.  Well, why can’t I just get it now, it’s just a download, you ask?  The answer is, while if you were hosting on your own ISP this would be the case, the OSU infrastructure is such that we have to ensure security, reliability as well as integrations with other solutions, such as authentication, themes and modules in use by OSU CWS Drupal sites.  We have a number of concurrent activities happening to make progress toward rolling this out for the University, including actively working on the theme necessary for Drupal 7 (yes we have to rewrite the theme to work for new Drupal versions).  This is in partnership with the rock-star team over in Web Communications.

Now more importantly, what we are trying to do with Drupal 7 is reduce our site footprint and number of individual sites.  Can you believe we have over 400 sites?  That becomes a maintenance and support headache.  With Drupal 7, there will be a new feature called Organic Groups.  This will allow us to have a smaller subset of sites, and areas and departments within the same site but still allow the finer grained control that some of you desire.  With Organic Groups, you will be able to take control of the portion of the site that is your relevant content, and have control so others cannot access that portion of the site as a Drupal administrator to modify something in error.  This is where we want to go and what makes sense for Oregon State University.

So when will this be done?  With Organic Groups, we are in the pilot stage with Information Services, and then we are going to ensure we have it done right by piloting the College of Liberal Arts.  Doing this we will ensure we understand the technology well enough to teach, document, and support it going forward so people are not left out on their own to figure things out.

Individual main colleges in working with Web Communications can look at Drupal 7 with the Doug Fir Theme (the theme that we have available for Drupal 7), and then incorporate changes for Organic Groups as we roll that out.  Science and Liberal Arts main college sites are already in Drupal 7.

Departments however, we will not be rolling out with Drupal 7 at this time, as they are to be incorporated into Organic Groups, working with your colleges, once we roll out Organic Groups.

For those sites that are in Drupal 6 and want to look like the main college sites that are using Drupal 7 Doug Fir, we are working on a version of Doug Fir for Drupal 6.

What is Doug Fir?  So besides being an evergreen confier species, Doug Fir is an OSU responsive Drupal theme.  This means that the site resizes depending on the device that you are on.  Liberal Arts is a good site to see using this theme.

For us it is imperative that we do this right and do not add to the overhead and support it would take to enable OSU.  This is why you might hear us say that we are not providing Drupal 7 to individual sites at this time.

Our rough timeline as of now is:

  • Spring and Summer to test and roll out Organic Groups.
  • Winter:  Migrate Drupal 6 sites to Drupal 7
  • 2014 Drupal 6 moves to maintenance fixes only
  • 2015 End of Life (EOL) Drupal 6

With all of this we are re-architecting the infrastructure, and then we will have Drupal 8 on the Horizon.

We hope this information helps you to be aware of the progress we are making.

On Monday, February 18th, if you hadn’t seen information about or attended the training sessions, Central Web Services and Media Services released a new version of Kaltura’s MediaSpace.  This is version 4 of MediaSpace.

The new version of MediaSpace, OSU’s open source and cloud-based media solution, integrates many requested features and some important new functionality, including privacy / access control, captioning, HTML5 support, and improved layout.

One of the best ways to understand the new features is to watch the video in MediaSpace about the new version.

Every department hopes for collaboration and cooperation among all of its members. Here at Central Web Services we are working towards making that a reality. In September, our office had a face lift. Out went the dull grey cubicles and in came new wooden desks and an open work space. The removal of the cubicle walls created an open and inviting workspace. Here are some pros and cons we’ve noticed since the redesign:

 

Pros

  • More space in the office
  • Easier to talk to one another
  • Collaboration among different areas within the department is easier
  • The office appears brighter and more inviting
  • Seeing who’s in the office at a glance

 

Cons

  • Nosier at times
  • No cubicle walls to hang things on
  • Spontaneous drop-ins by visitors can cause more disruption then previously

 

Although there was some hesitation on taking down the cubicles, we all agree that the change in the work environment has helped strengthen the team dynamic.

OSU Responsive ThemeWe have rolled out a new blog theme which is named OSU Responsive.  Why Responsive?

Responsive really means responsive web design.  The goal behind responsive web design is to have the design of a given web page be adjusted dependent on the size of the screen.  So on a phone, the look and feel changes to be more of a mobile experience where reading a full web page doesn’t necessarily make sense.

The theme is a two column theme, with only a main sidebar, and the bottom contact area as available areas to put widgets in.  Remember, not all widgets will look good in different areas so you will have to see what works and doesn’t.

Who can use OSU Responsive?  Responsive is available for everyone, however, there are some things to note.  The use of the OSU logo or tag is restricted to certain use.  The theme will display the tag or not based on the Organization Type as specified by the table below.

Organization Type Can Use Branded Theme?
Student No
Staff No
Faculty Yes
Department Yes
Sponsored Student Organization (SSO) Yes
Voluntary Student Organization (VSO) No
Non-Affiliated Student Organization (NSO) No

Student Organizations are governed by the policies of Student Leadership and Involvement.  If you are a student group and do not know which type of organization you are, please visit the Student Leadership and Involvement site.

What do you need to do to use it?

1.  If you are switching over from an existing theme, and you switch it immediately, it might seem that your site is broken in layout.  It isn’t.  It is simply that the widgets need to be removed and put back into the areas available for it.  So we recommend first removing all the widgets in use from the sidebars.

2.  Go to Appearance -> Themes in your WordPress dashboard, and select the OSU Responsive theme.

3.  Put your widgets back into the sidebar.

4.  Deactivate the Sociable Skyscraper plugin if you are using it.  Use of this inserts a thin horizontal line and makes the theme look broken.  Go to Skyscraper Options in the Select Sociable Plugin expanded menu to deactivate.

Skyscraper Option in Menu Settings

And that’s it.  Good blogging to you all.

Accessibility and Brand Guidelines

As part of the OSU Responsive use, the use of a different background image or color must adhere to OSU’s policies regarding Accessibility and Brand.  Any failure to do so may cause your blog to be disabled.  The net takeaway here is don’t change it if you don’t understand the policies, which is why we at Central Web Services, take care of these things for you in creating the default theme.  However, do remember within your articles, accessibility policies still apply if this is used in any official capacity for students, staff, or faculty or OSU.

Connect IconWith the beginning of a new school year just around the corner, something big has been brewing. Connect Week is all about connecting new students to Oregon State through events that introduce them to the different resources available on campus. Since the events are not restricted to just new students, they have the opportunity to connect with returning students who have already been through the ropes and can give them some tips. To help with the transition, this year there is a Connect app! The app helps you:

 

 

  • Keep track of the new student events
  • Get up-to-date info through social media sites like Twitter and Facebook
  • Information about the assortment of food options  open on campus at the time
  • Connect week FAQs
  • Connect week and new student news

 

What did the lead student developer, Nicole Phelps, have to say on the release of her first official app? “The OSU Connect app is a great way for students to get involved at OSU’s Connect week. Its theme is ‘Connect the Dots’, so I see it as an allegory for how each new student comes to the school with a blank slate, ready to connect their own dots.” You’ve connected the dots your whole life; from connecting the dots to discover the picture on the page to connecting the dots between classes to earn your diploma. Now you can use the app to help you stay connected at OSU while you earn your degree. It’s a connection to important up-to-date information on what’s going on and where to be right on your phone. This app provides a searchable campus map for the term (or multiple terms if you have luck like mine) that you have a class in a building like Wiegand Hall and you have no idea where it may be. Its list of the open food establishments on campus keep you informed and on time for meals. I wish I would have had an app like this during my first year on campus to save me from learning the dining center hours the hard way and showing up too late for a meal. Save yourself from the disappointment of missing new student events, and meals, and check out the app for Android and iOS!

 

Case Award Silver Team

No oops, but we did it again.  Add another award winning design and implementation for the category of Overall Website in the CASE VIII 2012 Communication Awards.  Oregon State University proudly brought home the Silver for the OSU College of Public Health and Human Sciences Website.  If you don’t know by now the work of Web Communications and Central Web Services, you should.  For the Central Web Services team of Sher Fenn, Paul Lieberman and Mauricio Cordoba, congratulations!  Congratulations to Web Communications and CPHHS team members.  It was a truly a team effort and another win-win-win for OSU in its collaborative efforts.  This could not have happened by any of us individually and reflects what comes from working together.

 

iOSU Flash Screen

It’s here!  Central Web Services and the iOS App Development Club have been busy over the last several months getting the next version of the iOSU App for iPhone ready to release to the Apple store.

So…why did it take us such a long time for our next release?  In the initial release, we identified a number of items that needed further investigation to fix some quirks that existed.  It also took us a little time to get the specifics going with the iOSU App Development Club.  If  you are a student and don’t know about the club and are interested in iOS App Development, you should visit the Student Leadership Site and search out the group.

Why did we wait and not just put up to the store a while ago when we  did our initial beta release? It was important that the App be of a quality level high enough for us to put up, and we were waiting for the budget to have additional training to enhance our skills so we could move in a knowledgeable and purposeful direction.  We were able to go forward with the training in August of 2011.

After the onsite training by a company named Appcelerator we learned a few better methods to develop for their Titanium platform, so we have taken that to incorporate a couple new features with the addition of Videos and iTunesU to the App. While we were in our beta phase, we received some good feedback, through the use of the feedback method available directly in the App!  We also received some small praise on its value, with one person even using it from India to look up contact information back at OSU.

iOSU Dashboard

For the current release, we’ve incorporated some of the feedback, and made some additional changes, such as the removal of the mobile site button, and a few other other enhancements.  And of course what would a release be without fixing some previous bugs.

What was the process we went through for this release, you ask?  We planned for a release prior to class start as part of our roadmap and strategic planning.  After releasing 1.1.0 to our Enterprise customers (that is everyone at OSU), we discovered a few additional bugs that delayed our originally scheduled pre-start-of-classes launch.  So we went on to version 1.1.1 to do some additional fixes, and then on to 1.2.0 for a few more feature changes.  After checking against iOS5 and those pesky last minute fixes, we were ready to go.  The next step was to go through the various steps to get an App submitted to the Store.  For those who don’t know, it’s a step process, where we have to enter all the various information you see, submit images that you see on the store, and then submit the built app for Apple to review.  Once Apple reviews, and the App meets Apple standards, they send us a notification that it was accepted.  At that point it is ready for the World to download!

iOSU Dashboard 2Now saying all this do we, as a Software Organization, expect a 100% bug free application?  Not at all.

However, we will fix the issues that we see or hear about, as we did with version 1.2.1 which came out shortly after to fix some bugs that came directly from your feedback, and some accessibility issues that we noted ourselves.

There is of course still more to do working with partners around campus to deliver more features, and for all the Android fans, we haven’t forgotten about you. The purpose of the training was also to take what we have and deliver an Android app in the near future. So that will be coming. Stay tuned!

EvalS is now Online
Now available to classified employees.

The performance of the EvalS application is now ready for primetime use.  The team worked hard, in conjunction with help from Enterprise Computing, to make changes to the code to improve upon the speed of the application.  Locally, you should see a significan improvement.  What took over 30 seconds to load before now takes a second or two on bringing up a person’s evaluation.  The initial load of the application is about 4 seconds, and still a little slow for our liking, so the team is looking at how to make it better.  Half a world away, in Malaysia, I can access the EvalS system and begin entering in results, and on a slow-wi fi connection, it takes about 15 seconds to load.  Not too bad.

The official notification went out on October 19th, by Jacque Rudolph.  If you haven’t read the email from the inform list, you should.  A kudos to the HR and Business Center team for all the hard work put into it.  I found out more than I imagined about the process, and there are a lot of nuances to consider, with bargaining agreements, and other particulars to work with.  Along the way, we hope we improved the process as well.

So how did it begin?  Well it all began with a request for development of an electronic time reporting system, funded by the Provost.  As Bob Nettles and I discussed, the decision was to ultimately look at a vendor system for the time reporting piece, as there are good systems already out there.  So we couldn’t just sit around and develop nothing, and discussing with Jacque Rudolph and Bob Nettles, we said why don’t we tackle some of the other paper processes, and the evaluation process came to mind, due to its specific nature.  With approval from the Provost, we set off in discussions and Agile development.  We didn’t wait until all the details were there, otherwise it would have taken significantly longer.  The Agile method allows for more rapid development, while gathering the particulars.  We did show and tells along the way, and worked out many of the specifics.

The development team of  Lead Developer Jose Cedeno with some assistance from Kenneth Lett, Mauricio Cordoba on styling, and Joan Lu, the software architect responsible for the overall technical design, put in a lot of hours, working weekends and then some to bring it together.  We didn’t have the staff of a Google or a Microsoft, or my former company IBM, to implement this, but the talent of the two helped bring this to life.  I put in a little time, myself on the original concept of the User Interface design, and Mauricio filled in the rest, so we do hope you find it as a good and modern interface.  There’s still some things we can do to make it better, but we have to save some things for the next few releases, don’t we?

For those who don’t know what it takes to develop portlets, the little apps in a portal, send us a note, and we’ll fill you in.  It does take some knowledge of Portal development, along with java programming expertise.  So it’s not just for anyone to develop in.

This is one of the steps Central Web is taking in Greening OSU.  So we encourage everyone to start using it.  For the Classified IT and Professional Faculty, we will be working toward your electronic evaluations next, so as I always say, stay tuned.   Sincerely, Jos Accapadi, Associate Director