Before we get to my many questions and concerns below, can we take a step back? I tried to request to bring in specifics in one of my last replies.
Can you please include that when posting things like those screenshots? You basically just dropped two screenshots and expected us to understand what is going on. Your first one looks like you have something working but I am not familiar with the buttons on the side there? (But maybe there is a very new version of something I haven’t come across yet?) Can you describe what that is and what you followed to set it up?
This isn’t a route to active deployment that I know of. The app should serve the .ipynb file as an application at a URL. Voila and Voici make .ipynb files available as apps/dashboards. (Using the correct URL to serve derived file with an .html extension is though involved with Voici, but not inside in Jupyter in my experience.)
As I said in my reply just above your latest post, the sample repo should give you an idea of what types of files are involved and you’ll see that a .html is not one.
The kernel backing the active .ipynb is necessary. There’s no kernel tied to the .html as far as I know.
For your latest post:
I’d suggest that isn’t a ‘deployment’ in your second screenshot in your last post. It just looks like you opened the HTML inside Jupyter. Maybe I am misunderstanding?
Is that in Voici or Voila? In Voila when correctly installed & deployed alongside Jupyter, you can open the .ipynb file that will be the app/dashboard in Jupyter and get a preview of the app/dashboard rendering of the .ipynb file using the Voila icon.
Under my example Voila deployment here I have links of examples that will both open the .ipynb file in Jupyter in the session and go directly to the app/dashboard rendering. If you choose the .ipynb route, after it opens you should see the Voila icon that is a yellow wiggly line over a green one and you can choose that and see the app/dashboard rendering alongside the notebook in Jupyter.
However, you are on github.io in that first screenshot and so I assume probably you are using Voici? In my use, there are only .ipynb files. You can see the example repo content here. I have my own deployment here. You can see the app/dashboard rendering of mine using here and clicking through. You’ll note these do have .html extensions but you’ll also see they URL includes voici/render/ like in this example endpoint https://fomightez.github.io/voici-demotestMay24/voici/render/demo.html?. Your opening ofthat html in your second screenshot in your last post won’t have that type of URL and so I don’t expect it to work.
However, maybe I am misunderstanding Voici myself. I find iterating on developing in Voici to be slow because of no preview. Maybe you are suggesting there should be that possibility via the route in your second screenshot? I would imagine definitely need to trust the HTML which is something you haven’t done in that last screenshot.