"Is anyone, using the shortener for only faculty and staff, using CAS to authenticate?
Are you limiting them to your .edu URLs/site for shortening?
Are you automating URL shortening when someone uses a service like bit.ly to use your tinyURL instead…"
"I had hoped to reply to this earlier last week, but I was attending a five-day class. As I read through the responses, I noticed the pattern of people replying about several issues:
1. limited resources
2. small number of people affected
"I asked earlier this year, but didn't see any response. Has anyone reviewed the accessibility of the various options you're using? Seems to me a straight HTML site, whether implemented in WordPress or something else, is the most accessible…"
I'm hoping to publish my notes/takeaways from the Accessibility Summit conference. Got to find time!
If you're interested, there's a backup of the tweets from the conference at:
"At Naz we implemented go.naz.edu in Django. It was one of the simplest Django projects ever. We demonstrated it at the HighEdWeb conference in 2009 and made the source code available. (pardon the archaic design).
go.naz.edu is for internal…"
"We created our own here at FHU. We did it primarily to have an "fhu.edu" address when shortening URLs for our social media outlets.
Ours is public, but we just don't advertise it outside of our campus community. We also added an API…"
"Hi Naveen. Yes, UCLA partnered with bit.ly Pro to create http://ucla.in. We also created our own API so that developers could use http://ucla.in in a more automated fashion as well.
bit.ly Pro is free and the development time is relatively quick to…"
"We have started the move to make all our sites HTTPS. With our InCommon membership (paid by our State Chancellor's Ofice), we get free certificates, so there is no ongoing costs.
In 2014, Google said they give some SEO bumps to HTTPS sites.…"
"Yep, I got the same messages. Some of our sites use SSL and we've been talking about migrating all the rest our sites for a while now. I suspect we will be doing it rather than just talking about it sooner rather than later now. :\"
I recently got a notice from Google that in October 2017 Chrome V62 with show the warning "NOT SECURE" on all our web pages we have a input field for search. Since on most of our pages there is nothing that would require secure information I've never felt the need for HTTPS. Our class registration pages are secure but not the general information pages. The warning is going to scare people though. Are others upgrading their websites?See More
It’s the last week get HighEdWeb 2017 early-bird registration pricing! When you register for the Annual Conference by the end of Monday, July 31, you save $100 — and who doesn’t love that?!Register by July 31 to save $100…See More
"Hi Samuel – WordPress will be a good choice for this kind of project. Can you let us know more about what features you are thinking of adding? It seems to me that a combination of a WordPress site and tightly integrated social media channels…"
"Implementing a content governance plan, complete with workflows and approvals, is essential when building a digital strategy for your site. Register for our upcoming webcast with Stamats to learn best practices for content governance. "