Affects Version/s: None
Fix Version/s: None
I run my Django app in a Python env... I then activate that Python env in a Zeppelin notebook... giving my Zeppelin code complete access to my models and controller (MVC) of my app. AKA Zeppelin *is* already the front end (the ) for my app without the need for authentication or an API/SDK layer. I can rearrange the tiles in a responsive grid... show users tables of content... and render graphics.
... this is essentially full-stack Python. However, this is not limited to Python, it would work with any language for which a Zeppelin interpreter has been written e.g. Ruby on Rails, Elixir, Graphql-based frameworks. The emergence of R Shiny & Python Plotly Dash front end frameworks serve as validation of this need.
Although Zeppelin paragraphs can already be embedded. What is needed is logic layer support in the web-app frameworks like `djangorestframework's APIView` to bridge the gap between the V and the C in the MVC model. Something like `NotebookResponse` in addition to JsonResponse and TemplateResponse.
This would turn Zeppelin into an `Application Browser` competitor to the `Webpage Browser`. Aka... Zepl (change it back to ZeppelinHub or at least brand ZeplHub) would become the iTunes/AppStore/HTML of it's day.
Once this application building ecosystem takes off, introduce a Kafka-based OpenAPI network using OAuth2.0 authentication to enable applications to fluidly share data in an operating system manner... to become the new internet/ web-based OS that replaces layers 5-7 in the OSI model (everything above/ running on the HTTP protocol would be dictated by this realtime network).
Additionally, Zeppelin's integration with pyspark could make Spark the default execution engine for Django querysets aka backend.
I was surprised not to be able to change the Zeppelin window style (dark theme) from the 8080 UI. Making sure the ecosystem can customize this will be important for branding/ white labeling.
Although you could maintain %reactjs, %angularjs, %vuejs, %bootstrap... webcomponents they would eventually morph into one ui component system.