This post shows my effort so far to configure pug on top of a new webpack4-based Aurelia project. There are two outstanding issues that I have not yet resolved:
- Pug file
requirestatements are not resolving the css file (e.g.
- Have not yet tackled the issue of passing
Video can vastly improve the conversion or click rate of any message, whether that be a Facebook post, website page or email message. There would be a real advantage, then, if you could embed video in email campaigns.
Way back in 2017, if you wanted to see what your Playable videos looked like when viewed on different devices, you had to have a lot of different devices on hand. You’d send yourself a sample email message, then need to view that message in each application and device.
This is useful for visualizations as well as archiving your route information. Have a look at the README file on github for more information.
PhoneSwipe provides an example of how consumers lack protection from online e-commerce scams, thus demonstrating the need for auditable, delivered transaction receipts.
I don’t miss XML. XML would only have been a quarter as bad as it is if it didn’t introduce the ambiguity of trying to decide whether data should be an attribute of an element or the value of an element.
It would only be half bad if it didn’t introduce the unwieldy syntax of triangle brackets and an end-of-comment closing syntax that use more triangle brackets and a second copy of the element name. It would only be three quarters bad if the syntax for comments didn’t also use triangle brackets, along with a few hyphens and a required closure at the end of each line.
Today I migrated a web site from Express 2.5 to Express 3.0.0rc3. This is a non backward compatible version change. Express has a Migrating from 2.x to 3.x wiki page, but it doesn’t quite leave you prepared for the more time consuming incompatibilities that you’ll need to fix. I’ll enumerate some of these differences here. Note that some of these issues may be ironed out in later releases of Express.
About five years ago a colleague and I were lamenting the fragmentation of identity and storage caused by the new crop of web apps. You could edit a Powerpoint-like presentation at one site, a photo at another, and check on your calendar at a third site. Each site required a separate login, and your content was stored in some unique new format in a cloud database that you couldn’t extract your data from. We saw a case for abstracting identity and storage to make life easier and less confusing for users and to help with archiving content beyond the life of the web site (e.g. 280Slides, which is now defunct). We were focusing on fixing identity using OpenId-like solutions, but we also thought the answer to cloud storage might be to provide a standard storage service that all the web apps could use.