Add what to expect section in landing page

Fix nbsphinx syntax highlighting for code cell

Author: jaladh-singhal

docs/_static/firefly-in-python-flow.png

@@ -72,5 +72,8 @@
 # Allow build to continue even if some notebooks error (useful for demos).
 nbsphinx_allow_errors = True
 
+# Ensure Pygments syntax highlighting for Jupyter code cells.
+nbsphinx_codecell_lexer = 'ipython'
+
 # Remove the .txt suffix that gets added to source files
 html_sourcelink_suffix = ''

docs/conf.py

@@ -28,6 +28,40 @@ with details about the server location, and how to use the instance
 to upload and display astronomical images, tables and charts.
 
 
+What to expect
+==============
+
+.. raw:: html
+
+    <div style="margin-bottom: 1.15rem;">
+
+.. image:: _static/firefly-in-python-flow.png
+    :alt: Firefly in Python Flow Diagram
+    :align: center
+
+.. raw:: html
+
+    </div>
+
+It's important to note that Firefly visualization in Python notebooks is 
+**NOT a per-cell chart or widget**, unlike common plotting libraries 
+such as Plotly or Bokeh.
+
+Under the hood, Firefly is a dedicated web application running at a specific 
+URL, rather than a plot produced as a notebook cell output. 
+Your notebook's Python session connects to a Firefly server, either a publicly 
+hosted instance (such as the `IRSA Viewer`_) or a local server running via Docker_. 
+Using a server enables advanced, compute-intensive interactivity that is 
+difficult to support directly within a notebook's UI.
+
+Multiple notebook cells can then send commands to the same Firefly instance, 
+which manages linked views of images, charts, and tables, similar to an 
+**interactive dashboard**.
+
+.. _IRSA Viewer: https://irsa.ipac.caltech.edu/irsaviewer/
+.. _Docker: https://hub.docker.com/r/ipac/firefly
+
+
 .. _firefly_client-using:
 
 Using firefly_client