Python & JavaScript developer, from
David is a Python and JavaScript developer, database designer, and prolific core-contributor to the Plone CMS.
David is a developer emeritus (now working with Salesforce.org) who co-led our server-side development – managing code architecture, database design, and deployment. He has been building web-based software in Python and JavaScript for over a decade. A prolific contributor to the Plone web content management system, he enjoys learning new tools – most recently React, elasticsearch, and the Pyramid web framework. When he’s not coding, David can be found experimenting in the kitchen.
Automated style guides
Design systems streamline development, communication, and consistency – but often rely on dedicated teams and extended budgets. We wanted a tool that helps create and maintain living style guides & pattern libraries in an agile process, and on a budget. Herman helps you keep your development process simple – and your UX consistent – as you scale over time.
Integrated design-system management in Sass
OddBird’s Accoutrement tools help keep design tokens meaningful to both humans and machines – opening the door for automation, while improving readability. These tools also integrate with Herman, our automated pattern-library generator.
Unit-testing for Sass developers
True is the only full-featured unit-testing framework designed specifically for the Sass language. Write your tests in Sass, compile them with Sass, and then (optionally) pass the results to a Javascript test-runner for command-line control and reporting.
Enterprise Web Content Management System
Now is the time to begin experimenting with a long requested layout tool.
The @container query, that elusive feature developers have been requesting
and proposing for years, has finally made its debut in a browser. Well, sort
of. Here we’ll explain what container queries are, how they work, and what
other features they might come with once fully supported in browsers.
(None of them is the username)
The term “username” is ambiguous. When designing a user model there are several kinds of names that are useful to include.
Code documentation is ideally written as close to the actual code as possible, but compiled into a comprehensive set of documentation that includes code from all languages in use. Here’s how we intend to do that.
Integrating Pyramid, React, & Plone