When clients are contemplating a new web development project, the question we most often hear is “How much will it cost?” The answer is usually “That depends.” Many factors can make a project more or less expensive. Here are a few to keep in mind, courtesy of the Jazkarta team (especially David Glick.)
- How important is it to have a polished visual design? The more polished and refined, the more time and money will be spent.
- Does everything need to be perfectly customized for your organization? If you are open to compromises that allow things to work in ways that are simpler to build you could reduce costs.
- Is the functionality public-facing or internal? This can play into the previous two questions. In general it is easier to make compromises and keep expenses down on an internal site.
- Does the project focus on a single feature area or a bunch of loosely connected areas? How much variation is there within a feature? How standardized are your processes? More features and variations lead to more work and more expense. Standardizing on one way of doing things might save on both development budget and staff time.
- Is the functionality managed by a single part of the organization or does it require buy-in across the organization? It can be difficult to get a diverse group of stakeholders to agree, and their diverse opinions might cause the scope of the project to increase. Try to prevent surprise stakeholders with a lot of organizational clout from emerging late in the project and announcing significant “critical” changes. This can wreak havoc with budgets and demoralize project staff.
- Does the project require coordination between multiple teams? This will take time and is another path to potential scope creep.
- Can the project be built on one major platform, or does it require integrating multiple platforms? Each integration will increase expense.
- How much traffic is expected? Traffic determines how much effort needs to be put into scaling and optimizing the site.
- Are you building a tool tailor-made for your organization, or something that you aim to release for use by other organizations? Generalizing features often takes more time and makes writing automated tests more critical.
- Does the project require migrating data from an old system? This will add to costs in proportion to the complexity of the data.
- If the project involves updates to an existing system, how well-maintained is it? Poorly maintained systems are more difficult to work with.
Big web development projects are daunting and it can be hard to figure out your budget and stick to it. The two best tools for controlling costs are:
- A thorough discovery process with your technology partners, to figure out what exactly you need to build and how you’re going to build it.
- A flexible implementation process that lets you change your mind when you discover problems or opportunities – an “agile” as opposed to a “waterfall” process.
If you’d like to hear more and you’re coming to the Nonprofit Technology Conference in Washington DC this week, come hear Karen Uffelman (of Percolator Consulting), Loren Drummond (of Washington Trails Association) and me talk about a big project we did together to develop a volunteer management system. The session is called For the Love of Volunteers! How Do You Choose the Right Technology to Help Manage Them?
Hope to see you there!
The annual Digital Humanities Awards allow the public to recognize outstanding digital humanities resources on the web. This year not one but two Jazkarta projects are nominated in the “Best Use of Digital Humanities for Public Engagement” category!
- Pleiades, a gazetteer of ancient places that recently won the Archaeological Institute of America’s 2017 Award for Outstanding Work in Digital Archaeology. It lets enthusiasts use, create, and share geographic information about the ancient world – associating locations with ancient places, names and scholarly references.
- Dumbarton Oaks’ Online Catalog of Byzantine Seals, which allows users to browse photographs and detailed information about the 17,000+ seals in the collection. Tools include a faceted search, bibliography, and “save my favorites” feature, as well as two informative online exhibitions.
Jazkarta helped develop the software that powers these sites – in both cases, custom add-ons for the Plone open source content management system. But the real work was done by the Pleiades and Byzantine Seals teams who conceived and designed these projects and did the heavy lifting of data entry and curation.
You can cast your vote for either of these projects – or for the National Endowment for the Humanities’ Office of Digital Humanities – by visiting dhawards.org/dhawards2016/voting/ and completing the voting form linked at the bottom before midnight this Saturday, 25 February.
Here at Jazkarta we’ve been working with the Institute for the Study of the Ancient World (ISAW) for the past year on a project funded by the National Endowment for the Humanities to upgrade and improve Pleiades, a gazetteer of ancient places that is free and open to the public. Thus it was very gratifying to learn that Pleiades is the 2017 recipient of the Archaeological Institute of America’s Award for Outstanding Work in Digital Archaeology. Congratulations to the Pleiades team, headed by ISAW’s Tom Elliott!
Pleiades is the most comprehensive geospatial dataset for antiquity available today, giving scholars, students, and enthusiasts the ability to use, create, and share geographic information about the ancient world. It was developed between 2006 and 2008 on version 3 of the open source Plone content management system. Pleiades allows logged in users to define geographic locations and associate them with ancient places, names and scholarly references. The system remained in place from 2008 to 2016 without significant upgrades to the core Plone stack, despite the addition of a number of custom features. Over that time, over 35,000 places were added to the system – and performance degraded significantly as the content expanded.
Our most important NEH deliverable was improving site performance, which we accomplished through an upgrade from Plone 3 to Plone 4.3 and the elimination of performance bottlenecks identified with the help of New Relic monitoring. As of last September we had reduced the average page load time from 8.48 seconds before the upgrade to 2.1 seconds after. This 400% speed-up is even more impressive than it sounds because bots (search engine indexers and third party data users) were severely restricted during the pre-upgrade measurements, and all restrictions were lifted after the upgrade.
Performance improvement was just the start. Here are some of the other changes we’ve made to the site, which you can read more about in the August NEH performance report.
- Process improvements that streamline content creation, review, and publication
- UI improvements that facilitate the use of Pleiades data
- Improved citation and bibliography management through integration with the Zotero bibliography management system
- Enhanced Linked Open Data capabilities
- Comprehensive daily exports
- Bulk imports of Pleiades content
Because of Jazkarta’s high level of expertise in Plone and related technologies, we were able to deliver the Plone upgrade and related performance improvements 6 months ahead of schedule. This left more time for feature improvements than were originally envisioned. As Tom Elliott put it, “our investment in Jazkarta is paying dividends.”
David Glick and I had a great time presenting at the 2016 Nonprofit Technology Conference with The Mountaineers’ Jeff Bowman and Percolator Consulting’s Karen Uffelman (here’s a link to our session page.) We gave a soup to nuts run through of the big website project we did together. Jeff provided some context for the project and showed off the final result. Karen described the development of The Mountaineers’ engagement strategy, which was the basis for everything we did. She also explained how user experience and graphic design was integrated into the overall project. David and I described technical discovery, our agile process, and the year-long implementation of the Plone website and Salesforce.com back end. Karen and Jeff also covered how to survive project disasters (the consulting partner that The Mountaineers had carefully selected and vetted essentially went out of business after their initial round of technical discovery), and the importance of planning for ongoing support and development after the site is launched.
Through it all, we emphasized the keys to this project’s success, which were:
- A solid engagement strategy guiding what we wanted to accomplish – Percolator’s superpower.
- An agile process that minimized risk and adapted quickly to change – Jazkarta’s superpower.
- Working with trusted partners with great communication skills who understood The Mountaineers and the technologies they were adopting – as Karen put it, “Choose your project partner like you’d choose a spouse.”
How successful was this project? In addition to all the oooo’s, aaaah’s and good feelings, we have some numbers about that. In the first year post launch, the site had 69% more unique visitors, 72% more page views, and a 23% reduction in bounce rate. That trend continues through the present day.
If you’d like to learn more, you can view or download our presentation on Slideshare. You can also view the Twitter stream for our talk at #16ntcwebanatomy and read the shared document where the audience took collaborative notes. I’ll share here the most fun item on the stream – Twitter user @fulltrucker‘s artistic and amusing session notes:
I’m excited to share the news that the 2016 Plone Conference will be right here in Boston! Save the dates October 17-23 for a solid week of excellent training, informative talks, inspiring keynotes, and productive sprints like we’ve come to expect from a Plone conference – all for one reasonable (not yet finalized) price. The Microsoft New England Research and Development center has graciously agreed to host us, and we’ll be spreading ourselves liberally around Kendall Square and the MIT campus. (Yes, that’s technically Cambridge, not Boston, but that’s a distinction most non-New Englanders don’t make.)
At this conference we plan to extend the Plone community’s greetings and space to the larger Python Web community which many of us are also involved in. This happened in San Francisco several years ago; in Boston we hope to integrate these threads rather than having separate tracks. We want to include talks, trainings, and sprints on a variety of Python web frameworks, but we especially want to encourage talks and activities that compare, contrast and encourage learning and sharing across systems. (Not to mention socializing.)
The week will start with 2 days of training for developers, designers, and integrators, which will be included in the conference registration fee. Attendees will be able to mix and match full day classes on theming and development in Plone and other Python web technologies, with shorter workshops on a wide variety of topics.
The next 3 days will start with a keynote where the whole community will come together, and then we’ll break into 3 simultaneous tracks of talks. (Choosing between them is always hard!) We will be inviting talks on specific topics to give clarity and shape to the conference’s agenda. The rest will come from an open call for talk proposals. We’ll be continuing the Bucharest tradition of encouraging new speakers to present – so start jotting down your ideas.
After the talks there will be 2 days of “sprints”, focused development sessions that everyone, regardless of skill level, can participate in. This can include everything from core Plone through documentation. We plan to include Pyramid and other Python Web sprint topics to make this an event that can be shared with members of the sizable Boston Python community.
So I hope to see you all there! The Plone Conference is like a family reunion – we all look forward to it every year. I’m really excited about sharing those good vibes with Boston.
Like the cobbler’s children who have no shoes, Jazkarta’s website was long overdue for some major work. We began working on a redesign last winter – some modest improvements that morphed into more major changes. When we were ready to move into development in the spring, the Plone 5 release was in beta, so we took the plunge and used this new and shiny Plone on our new website. We’re glad we did! We lived through some growing pains in the early months, but the software got more and more solid as the summer progressed. Plone 5 was officially released just weeks before our new website launched in October, so we have 2 things to celebrate.
Years in the making, this new version of “the ultimate open source CMS” has many, many improvements over its predecessors. A few high points:
- Out-of-the-box responsive and improved tools for custom theming, including LESS integration (a big win for us since responsiveness was a high priority)
- An improved content editing experience with a new toolbar, bulk editing, and TinyMCE 4
- A new templating engine (Chameleon) which gives improved performance
- Automatic CSRF (cross-site request forgery) protection
- Improved accessibility, as described in a previous post
- A new event type that supports all day, open ended, and recurring events
- A full transition to the new “Dexterity” content type framework including support for migration of old content – better for editors (through-the-web customization) and better for developers (reusable behaviors)
And of course it’s still 100% open source and developed by our favorite community of volunteers. You can read all the details at plone.com/5.
Starting with the very first version, Plone has been a leader in accessibility, allowing people with visual or motor impairments to use and navigate Plone sites. As I said in my previous post 6 Reasons Plone is Great for Higher Ed, Plone was the first CMS to be compliant with the W3C’s WAI-AA and the U.S. government’s Section 508 standards.
Before I published that post, I asked Paul Roeland (Chair of the Plone Foundation Board of Directors) to fact check the Accessibility section, since he has been a champion of Plone’s accessibility efforts for years. He replied that it was OK (“although a bit underselling it”) for Plone 4. However for Plone 5 he informed me that the situation has improved dramatically. Here are the accessibility features that are coming soon in the Plone 5 release:
- Support for WCAG 2.0 (level AA), WAI-ARIA, and even more exciting, ATAG 2.0 which is aimed at content creators, not just visitors of a website. Full support of all three is the goal. Some WCAG 2.0 guidelines are somewhat subjective, but we are doing our best to achieve full support.
- All new themes, widgets, and editors are strictly checked against those guidelines. That includes, for example, checks on contrast, color blindness, and widget and navigation support for the mobility-challenged and people using screen readers.
- The new version of Plone’s WYSIWYG editor has much improved accessibility for other-abled content editors, and it is also easy to include add-ons that will ensure the content in your site will remain accessible over time.
Content accessibility is technically outside the responsibility of Plone – it needs to be done by the organization’s content editors – but site administrators will have the option to configure the site to strictly enforce accessibility guidelines such as making sure all images have an “alt” tag. Plus language helper tools are available to help editors create clear content, which is also a guideline in WCAG.
In summary, while some guidelines are subjective and some can only be guaranteed by the content editors of the site, Plone will give you the best tools available to make, and more importantly keep, your site accessible. For both visitors and staff.
If you are interested in ensuring that your website is accessible, here are some tools that can help:
- The WAVE extension for Chrome which allows you to evaluate web content for accessibility issues from your browser.
- The A11y Command-line Tools provide web accessibility audits powered by the Chrome Accessibility Developer Tools.
In the end, however, no automated tool is a substitute for working with other-abled developers and users. And keep in mind that web accessibility is evolving – blind users use smartphones too! So staying at the forefront of accessibility is more about having it fully integrated in your thought process than about simply ticking boxes. Plone has taken that approach, and the result is that Plone 5 powered websites will offer a better experience for every user, regardless of abilities.