Widen has always strived to create functional and useful user interfaces to allow content strategists, marketers, and others to manage their digital content. We have always kept a close eye on technology that would enable us to do that even better.
Projects should not depend on internal Widen infrastructure. Making something that interacts with our public APIs and sites is fine, but a project that launches EC2 instances in our cloud is not.
So, our URI of “/proxy/http%3A%2F%2Fwiden.com%2Fcareers” is being expanded to “/proxy/http%3A//widen.com/careers” before it is routed to a matching endpoint handler. Of course, this endpoint is not accounted for, and our server rejects the request as a result.
While Widen/fullstack-react was designed to be simple to allow us to focus on the concepts needed to create and test a futuristic full-stack JavaScript web application, there are certainly areas where we can make improvements.
In fact, some of Widen’s emerging software products will make use of all of the new technologies discussed in this article. Next, I’ll document each notable new tool.
As part of Widen's commitment to contributing back to the open-source community, we have sponsored work to improve the CSS variables implementation in WebKit. Read on to learn more about CSS variables and how they're implemented in WebKit.
Welcome to another Widen engineering blog post! Today, we’re going to embark on a journey of optimization. We’ll compare and contrast multiple approaches to solving a simple performance problem, one of which being the web’s newest and shiniest addition, WebAssembly.
Many of the applications we develop at Widen utilize TypeScript for front-end development to provide a high level of type safety while also remaining familiar to developers who are used to JavaScript.
