Mobile sites

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website

We are also using Responsive Web Design (RWD) at UC San Diego as the primary technology to support all devices that access our web properties.  We launched using RWD in January of 2012 and since then have been retrofitting all our sites maintained in our central CMS to use this approach (we use Hannon Hill Cascade Server CMS). 

In addition to our CMS powered websites, we’ve also begun using RWD for web applications like the campus directory:

http://act.ucsd.edu/directory/faculty_staff?list_code=16003 (shrink your browser to see RWD in action or pull it up on your phone)

Again the advantage is you build with one set of code and the layout automatically conforms to the resolution of the device accessing the website or web application.  And with the explosion of different sized mobile devices the line became blurred between large phones like the Galaxy Note and small tablets such as the Google Nexus.  In 2012, our campus home page was viewed by 523 different screen resolutions…

We also maintain a mobile website at http://m.ucsd.edu.  We are using the Mobile Web Framework (http://mwf.ucla.edu/) to power these apps. These “mobile optimized tools” are primarily for an on-campus audience.  Our thought is most of these could be converted using RWD but the framework is still very much a viable, lightweight solution.

We also understand apps in the Apple and Google app stores still have cache and a presence in those stores is warranted.  Our iOS and Android apps are essentially wrappers that point back to m.ucsd.edu.  In terms of tablet support the iOS app is optimized for both iPhone, iPad, and iPad mini. 

If you have specific questions, let me know…

Cheers,

Brett

Brett Pollak

Director, Campus Web Office

UC San Diego

cwo.ucsd.edu

858-246-0239 (w) | 858-349-3523 (m)

Posted by listserv-anon on January 2, 2013

Message from ted.dodds@cornell.edu

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

Posted by: acambre on January 2, 2013

·         flag this

At Webster we have done the same with our recently launched redesign of our website

Wm. Kenneth Freeman

Wm. Kenneth Freeman, CIO

Webster University

470 E. Lockwood Ave.

St. Louis, MO 63119-3194

Phone:   314.246.5990

kennethfreeman@webster.edu

http://www.webster.edu/

Posted by: wmkfree on January 2, 2013

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website

Bob,

Our CMS will detect whether you are accessing the site from a mobile device or a computer and will render the mobile version or the standard version accordingly.  Tablets will get the standard version of our site. 

We plan to launch our mobile site this month.

Bob,

Our CMS will detect whether you are accessing the site from a mobile device or a computer and will render the mobile version or the standard version accordingly.  Tablets will get the standard version of our site. 

We plan to launch our mobile site this month.

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website

We are also using Responsive Web Design (RWD) at UC San Diego as the primary technology to support all devices that access our web properties.  We launched using RWD in January of 2012 and since then have been retrofitting all our sites maintained in our central CMS to use this approach (we use Hannon Hill Cascade Server CMS). 

In addition to our CMS powered websites, we’ve also begun using RWD for web applications like the campus directory:

http://act.ucsd.edu/directory/faculty_staff?list_code=16003 (shrink your browser to see RWD in action or pull it up on your phone)

Again the advantage is you build with one set of code and the layout automatically conforms to the resolution of the device accessing the website or web application.  And with the explosion of different sized mobile devices the line became blurred between large phones like the Galaxy Note and small tablets such as the Google Nexus.  In 2012, our campus home page was viewed by 523 different screen resolutions…

We also maintain a mobile website at http://m.ucsd.edu.  We are using the Mobile Web Framework (http://mwf.ucla.edu/) to power these apps. These “mobile optimized tools” are primarily for an on-campus audience.  Our thought is most of these could be converted using RWD but the framework is still very much a viable, lightweight solution.

We also understand apps in the Apple and Google app stores still have cache and a presence in those stores is warranted.  Our iOS and Android apps are essentially wrappers that point back to m.ucsd.edu.  In terms of tablet support the iOS app is optimized for both iPhone, iPad, and iPad mini. 

If you have specific questions, let me know…

Cheers,

Brett

Brett Pollak

Director, Campus Web Office

UC San Diego

cwo.ucsd.edu

858-246-0239 (w) | 858-349-3523 (m)

Posted by listserv-anon on January 2, 2013

Message from ted.dodds@cornell.edu

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

Posted by: acambre on January 2, 2013

·         flag this

At Webster we have done the same with our recently launched redesign of our website

Wm. Kenneth Freeman

Wm. Kenneth Freeman, CIO

Webster University

470 E. Lockwood Ave.

St. Louis, MO 63119-3194

Phone:   314.246.5990

kennethfreeman@webster.edu

http://www.webster.edu/

Posted by: wmkfree on January 2, 2013

Bob,

Our CMS will detect whether you are accessing the site from a mobile device or a computer and will render the mobile version or the standard version accordingly.  Tablets will get the standard version of our site. 

We plan to launch our mobile site this month.

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website

Bob,

Our CMS will detect whether you are accessing the site from a mobile device or a computer and will render the mobile version or the standard version accordingly.  Tablets will get the standard version of our site. 

We plan to launch our mobile site this month.

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website

We are also using Responsive Web Design (RWD) at UC San Diego as the primary technology to support all devices that access our web properties.  We launched using RWD in January of 2012 and since then have been retrofitting all our sites maintained in our central CMS to use this approach (we use Hannon Hill Cascade Server CMS). 

In addition to our CMS powered websites, we’ve also begun using RWD for web applications like the campus directory:

http://act.ucsd.edu/directory/faculty_staff?list_code=16003 (shrink your browser to see RWD in action or pull it up on your phone)

Again the advantage is you build with one set of code and the layout automatically conforms to the resolution of the device accessing the website or web application.  And with the explosion of different sized mobile devices the line became blurred between large phones like the Galaxy Note and small tablets such as the Google Nexus.  In 2012, our campus home page was viewed by 523 different screen resolutions…

We also maintain a mobile website at http://m.ucsd.edu.  We are using the Mobile Web Framework (http://mwf.ucla.edu/) to power these apps. These “mobile optimized tools” are primarily for an on-campus audience.  Our thought is most of these could be converted using RWD but the framework is still very much a viable, lightweight solution.

We also understand apps in the Apple and Google app stores still have cache and a presence in those stores is warranted.  Our iOS and Android apps are essentially wrappers that point back to m.ucsd.edu.  In terms of tablet support the iOS app is optimized for both iPhone, iPad, and iPad mini. 

If you have specific questions, let me know…

Cheers,

Brett

Brett Pollak

Director, Campus Web Office

UC San Diego

cwo.ucsd.edu

858-246-0239 (w) | 858-349-3523 (m)

Posted by listserv-anon on January 2, 2013

Message from ted.dodds@cornell.edu

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

Posted by: acambre on January 2, 2013

·         flag this

At Webster we have done the same with our recently launched redesign of our website

Wm. Kenneth Freeman

Wm. Kenneth Freeman, CIO

Webster University

470 E. Lockwood Ave.

St. Louis, MO 63119-3194

Phone:   314.246.5990

kennethfreeman@webster.edu

http://www.webster.edu/

Posted by: wmkfree on January 2, 2013

Bob,

Our CMS will detect whether you are accessing the site from a mobile device or a computer and will render the mobile version or the standard version accordingly.  Tablets will get the standard version of our site. 

We plan to launch our mobile site this month.

Robert,

Cornell uses the community source platform known as Kuali Mobility. It is device agnostic due to its underlying HTML5 technology and can be test-driven from here: https://kuali.org/mobility. Currently two other schools – U. Michigan and Indiana U – also use the platform, with other institutions in planning mode. If you have BYOD issues, I think you’d find it worth a look.

…Ted

Ted Dodds

CIO and Vice President

Cornell University

On www.smu.edu, SMU’s main marketing web presence, we are doing responsive web design (RWD). This uses CSS3 magic to make the page scale to several device widths, including tablets and phones.

You can experience this at http://www.smu.edu/. Gradually narrow your browser; as with width narrows past certain points, the whole layout shifts (responds).

For example, the same code that does this:

…also does this:

We’re using Sitecore CMS for our WCM. We investigated using a Sitecore feature that would allow us to detect device capabilities. With this, we could render the page differently based on the device. RWD was easier to implement, but I still see value for different renderings for some uses. RWD doesn’t work for everything.

Only a portion of our site has RWD. We are rolling out a new set of templates for the campus over the next several months or so, and sites will pick up RWD as they get these new templates.

At Webster we have done the same with our recently launched redesign of our website