Since such overhauls are relatively infrequent and set the stage for a web site for years to come, they are rare and vital opportunities to step back to basics. What should the site be? What should it express? Who is it for and what should it do for them?
MindBody is a web-based management system widely used by yoga studios. Using MindBody’s SOAP-based API, eeMindBody provides an easy way for a studio’s ExpressionEngine web site to access its MindBody data.
"Pika, a future without webpack.":https://www.pikapkg.com/blog/pika-web-a-future-without-webpack/ Looks good, back to sanity. While I'm greatly appreciative that the mass of work involved with compiling stuff gives us hot-loading on the client end and components on the dev end, hopefully the big process that makes that possible will be reduced.
"Mathieu Triay on his Marvin Visions":fhttps://www.readvisions.com/marvin, a reinterpretation of the 1969 font Marvin by Michael Chave.
I like it, I like it: "theorizing":https://blog.hichroma.com/the-crucial-tool-for-modern-frontend-engineers-fb849b06187a on "UI components":https://blog.hichroma.com/hidden-in-plain-site-the-levels-of-component-reuse-ee9b0d7b1bd2 by Dominic Nguyen.
"34 most popular GitHub JS repositories in March '19":https://dev.to/iriskatastic/34-most-popular-github-js-repositories-in-march19-4hkb by Iren Korkishko
Putting the ack! in acquihire: "Our Incredible Journey":https://ourincrediblejourney.tumblr.com/.
Jonathan Hoefler explores something that typeface designers have long known but that researchers have only now corroborated: "horizontal lines appear thicker than vertical ones":https://www.typography.com/blog/turning-type-sideways.
Important to consider: despite choice fatigue, "users do benefit from some symbolic choices":https://medium.com/s/story/the-ux-uncanny-valley-cf30df9fb45a, this piece argues.
"itshello.co":https://itshello.co/ — clientless, open-source video chat in the browser.
If the dataset is large it can be posted using a batch import.
he content may be created, the system architected, installed and configured, but we’re still missing a rather important ingredient: having the content within the system. This data can either be posted manually using the system’s control panel, or, if the dataset is large, by means of a batch import.
Engaging.net has much experience performing batch imports into ExpressionEngine. In fact we’re often hired for this step only, such as bringing in thousands of blog entries when converting from a previous content management system.
Among the issues to work out here can be how to maintain the integrity of old URLs.
The entire process, with dependencies