Web

As a Dash developer, I wanted a way to write clean, maintainable code without constantly switching between Python and JavaScript. Writing clientside logic inside a string felt clunky, and I knew there had to be a way to take advantage of quick clientside features of Dash without sacrificing the readability and syntax-highlighting of my code.

When building applications with Plotly Dash, it’s not that easy to adhere to Modular Web Design. One common challenge is managing component IDs. Typically, developers define an ID in one place and reference it in another, leading to scattered logic that can be difficult to maintain. Inspired by Dash’s All-in-One Components, I set out to create a more modular approach. This led to the development of dash-basecomponent, a Python package that simplifies component structuring while promoting modular web design.

For more than a year this blog used a Google Form for managing subscriptions, and relied on me to manually copy all the emails and write a newsletter to keep you all updated.

There has been an upgrade…

The world of web development can be insanely complex and overwhelming, however building a simple website doesn’t have to be difficult. Many people’s needs can be fulfilled simply by taking 30 minutes to set up a website on Github pages completely for free.

I am not endorsed in any way by Plaid to share this info, just helping others get a head start on using Plaid with Django.

Plaid is a plaform-as-a-service API which you can use to build your own financial apps. It has features such as easily linking to existing bank accounts, and also auto-categorization of transactions. Plaid’s API brings all the data from different financial sources into one place and one format so you can build apps with a holistic view of a user’s finances.

Ok. Now all praise of Plaid aside, I’m sure you are here because you want to build a Django app that uses Plaid to obtain users’ financial data. In all of Plaid’s tutorials shown in their quickstart github page, they have a tutorial for Python, but it’s using Flask for the backend rather than Django.

I’ve taken the time to translate their tutorial from Flask to Django. The main difference was Django’s requirement of having CSRF protection.