blu-react 0.0.2__tar.gz → 0.0.3__tar.gz

blu_react-0.0.3/CHANGELOG.md

@@ -0,0 +1,18 @@
+# Changelog
+
+## v0.0.3 - 2026-10-12
+
+_Blu now uses MicroPython by default and no longer uses PyScript. If you are upgrading from v0.0.2, add `INTERPRETER = 'pyodide'` to your `__settings__.py` and remove any references to the `pyscript`._
+
+### Added
+
+- Add support for MicroPython in client-side code.
+
+### Changed
+
+- **Breaking** Use `*` instead of `/` to separate route parameters and query parameters in route handlers.
+- **Breaking** Make MicroPython the default client-side Python interpreter (use previous default interpreter by adding `INTERPRETER = 'pyodide'` to `__settings__.py`).
+
+### Removed
+
+- **Breaking** Remove support for async callbacks in `blu.use_effect()`.

{blu_react-0.0.2 → blu_react-0.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: blu-react
-Version: 0.0.2
+Version: 0.0.3
 Summary: A full stack React framework for Python
 Project-URL: Homepage, https://github.com/johnlarson/blu
 Project-URL: Documentation, https://blu-react.readthedocs.io
@@ -11,7 +11,6 @@ License-File: LICENSE
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.14
-Requires-Dist: aiofiles
 Requires-Dist: uvicorn
 Description-Content-Type: text/markdown
 

{blu_react-0.0.2 → blu_react-0.0.3}/docs/_includes/client-element-children.rst

@@ -51,7 +51,7 @@ A child of an HTML element can be any of the following types:
 - A :py:class:`int`. This renders as a text node whose text is the :py:class:`str` representation of the integer.
 - A :py:class:`float`. This renders as a text node whose text is the :py:class:`str` representation of the float.
 - An :py:class:`Iterable <collections.abc.Iterable>` of valid children. This renders as all the child nodes contained in the :py:class:`Iterable <collections.abc.Iterable>`.
-- A :class:`blu.ClientElement` (see :ref:`Client-Side Rendering`).
+- A :class:`blu.ClientElement` (see :ref:`user-guide/client-side-rendering:Client-Side Rendering`).
 - A :class:`blu.Key`.
 
 .. code-block:: python

{blu_react-0.0.2 → blu_react-0.0.3}/docs/_includes/client-side-rendering-notes.rst

@@ -41,6 +41,17 @@
             return p['Hello, World!']
 
 
+.. note::
+
+    By default, Python code that runs on the client is run by the MicroPython interpreter. This means some features of Python are unavailable to modules that are used client-side. You can choose to use a more fully-featured but slower-loading Python interpreter called Pyodide by adding the following to ``app/__settings__.py``:
+
+    .. code-block:: python
+        :caption: app/__settings__.py
+
+        INTERPRETER = 'pyodide'
+
+    For more information, see :doc:`/appendices/choosing-an-interpreter`
+
 .. note::
 
     Client-side code runs in a different environment than server-side code. If your client-side code uses an external library, make sure it is installed in the client environment by adding it to the list of client dependencies in ``app/__settings__.py`` (if the ``__settings__.py`` doesn't exist, create it)::
@@ -52,7 +63,7 @@
     .. code-block:: python
         :caption: app/__index__.py
 
-        import arrr
+        import base64
         from blu import client
 
         __client__ = True
@@ -64,15 +75,16 @@
 
         @client
         def MyClientElement():
-            return p[
-                arrr.translate('Hello there. How are you?')
+            return div[
+                p['Message: Hello, World!'],
+                p['Base64-encoded:', base64.encode('Hello, World!')],
             ]
 
 
     .. code-block:: python
         :caption: app/__settings__.py
 
-        CLIENT_REQUIREMENTS = ['arrr']
+        CLIENT_REQUIREMENTS = ['base64']
 
 
 .. note::
@@ -86,7 +98,7 @@
         from blu import client
         from blu.html import button
         
-        from pyscript import window
+        from js import window
 
         __client__ = True
 
@@ -111,7 +123,7 @@
         from blu.html import button
         
         if is_client:
-            from pyscript import window
+            from js import window
 
         __client__ = True
 

{blu_react-0.0.2 → blu_react-0.0.3}/docs/_includes/iterables-must-use-keys-note.rst

@@ -56,4 +56,4 @@
         # Right.
         div['Hello, Ana! Hello, Bill! Hello, Charlotte!']
 
-    The rationale here is that, in :ref:`client-side rendering <Client-Side Rendering>`, items in a sequence may be moved around in response to user interaction. Giving keys to these items allows React to maintain state and render efficiently even when an item's position in a sequence changes.
+    The rationale here is that, in :ref:`client-side rendering <user-guide/client-side-rendering:Client-Side Rendering>`, items in a sequence may be moved around in response to user interaction. Giving keys to these items allows React to maintain state and render efficiently even when an item's position in a sequence changes.

{blu_react-0.0.2 → blu_react-0.0.3}/docs/api-reference/blu.html.rst

@@ -1,4 +1,5 @@
 ``blu.html``
 ============
 .. automodule:: blu.html
-    :special-members: __getattr__
+    
+    .. autofunction:: blu.html.__getattr__

{blu_react-0.0.2 → blu_react-0.0.3}/docs/api-reference/cli.rst

@@ -15,4 +15,4 @@ The deveopment server will automatically find an available port to run on, and o
 
   INFO:     Uvicorn running on http://127.0.0.1:50227 (Press CTRL+C to quit)
 
-Don't run the development server in production. See :ref:`Deploying Your App` for details on how to deploy an app to a production environment.
+Don't run the development server in production. See :ref:`user-guide/deploying-your-app:Deploying Your App` for details on how to deploy an app to a production environment.

{blu_react-0.0.2 → blu_react-0.0.3}/docs/api-reference/file-conventions.rst

@@ -1,11 +1,11 @@
 File Conventions
 ================
 
-A Blu app is defined by the :ref:`special files <Special Files>` under its ``app/`` directory. The ``app/`` directory should be placed in the project root (this is the working directory where you run the development server using the ``blu`` command).
+A Blu app is defined by the :ref:`special files <api-reference/file-conventions:Special Files>` under its ``app/`` directory. The ``app/`` directory should be placed in the project root (this is the working directory where you run the development server using the ``blu`` command).
 
-Note that some special files' behavior is influenced by :ref:`the directories in their paths <Directories>`, relative to the ``app/`` directory.
+Note that some special files' behavior is influenced by :ref:`the directories in their paths <api-reference/file-conventions:Directories>`, relative to the ``app/`` directory.
 
-You can also put :ref:`static files <Static Files>` in the ``app/`` directory.
+You can also put :ref:`static files <api-reference/file-conventions:Static Files>` in the ``app/`` directory.
 
 
 Directories
@@ -92,10 +92,10 @@ Handles a request whose full URL matches all directories in the path to this fil
     /foo/some/other/path
     /foo/bar/extra/segments
 
-Top-level functions
-^^^^^^^^^^^^^^^^^^^
+An __index__.py file should have the following top-level function:
 
 .. py:function:: __page__(***url) -> blu.Node | blu.Response
+    :no-index:
 
     Handle a request whose URL path is matched by this file.
 
@@ -105,7 +105,7 @@ Top-level functions
         from blu.html import p
 
         
-        def __page__(slug, /, q):
+        def __page__(slug, *, q):
             return (
                 p['The slug value is: ', slug],
                 p['The query param value is: ', q],
@@ -148,11 +148,10 @@ Handles a request for which the directories in the path to this file from the ``
     /
     /hello
 
-Top-level functions
-^^^^^^^^^^^^^^^^^^^
-
+A __default__.py file should have the following top-level function:
 
 .. py:function:: __page__(***url) -> blu.Node | blu.Response
+    :no-index:
 
     Handle a request whose URL path is matched by this file.
     
@@ -162,7 +161,7 @@ Top-level functions
         from blu.html import p
 
         
-        def __page__(slug, path__, /, q):
+        def __page__(slug, path__, *, q):
             return (
                 p['The slug value is: ', slug],
                 p['The remaining path is: ', path],
@@ -189,14 +188,14 @@ __settings__.py
 
 Configuration for your Blu app.
 
-Should be placed in the root of the ``app/`` directory, i.e. the app directory should be the immediate parent of __settings__.py.
-
 .. code-block:: python
     :caption: app/__settings__.py
 
+    INTERPRETER = 'pyodide'
+
     CLIENT_REQUIREMENTS = ['arrr', 'aiohttp']
 
-You can configure your Blu app by creating a __settings__.py file and assigning configuration values at the top level of the file. For example, the __settings__.py file above sets the ``CLIENT_REQUIREMENTS`` configuration property to ``['arrr', 'aiohttp']``.
+Must be placed in the root of the ``app/`` directory, i.e. the app directory must be the immediate parent of __settings__.py.
 
 A __settings__.py file is not required, and an app without a __settings__.py file will be treated the same as an app whose __settings__.py is empty.
 
@@ -205,16 +204,36 @@ A __settings__.py file can have any of the following settings:
 .. data:: CLIENT_REQUIREMENTS
     :type: list[str]
     :value: []
+
+    The Python libraries that Blu should install in the client environment.
     
     .. code-block:: python
 
-        CLIENT_REQUIREMENTS = ['arrr', 'aiohttp']
+        CLIENT_REQUIREMENTS = ['abc', 'io']
+
+    If using the default Python interpreter, ``CLIENT_REQUIREMENTS`` can include any packages from the `micropython-lib repository <https://github.com/micropython/micropython-lib>`_, under the ``python-stdlib/``, ``python-ecosys/``, ``micropython/``, or ``unix-ffi/`` directories.
+
+    .. code-block:: python
+
+        CLIENT_REQUIREMENTS = ['bluetooth', 'io']
+
+    If :doc:`opting in to Pyodide </appendices/choosing-an-interpreter>`, ``CLIENT_REQUIREMENTS`` can include any values that can be passed in as requirements to Pyodide's `micropip.install() <https://micropip.pyodide.org/en/stable/project/api.html#micropip.install>`_ function.
+
+    .. code-block:: python
+
+        CLIENT_REQUIREMENTS = ['arrr', 'emoji']
+
+.. data:: INTERPRETER
+    :type: typing.Literal['micropython', 'pyodide']
+    :value: 'micropython'
 
-    The Python libraries that Blu should install in the client environment. For example, if you have code running client-side that uses `aiohttp <https://pypi.org/project/aiohttp/>`_, you must add aiohttp to the client-side requirements:
+    The Python interpreter to use for client-side code.
 
     .. code-block:: python
 
-        CLIENT_REQUIREMENTS = ['aiohttp']
+        INTERPRETER = 'pyodide'
+    
+    See :doc:`/appendices/choosing-an-interpreter` for more details.
 
 
 .. _file-conventions/files/what-does-triple-star-url-mean:
@@ -251,16 +270,16 @@ You can capture route parameters from dynamic route segments by passing them in
 Capturing query parameters
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Any arguments specified after ``/`` in your call signature will capture query parameters instead of route parameters:
+Any arguments specified after ``*`` in your call signature will capture query parameters instead of route parameters:
 
 .. code-block:: python
     :caption: app/_id_/__index__.py
 
     from blu.html import p
 
-    def __page__(id, /, foo):
+    def __page__(id, *, foo):
         return (
-            p['ID: ', id],
+            p['ID:', id],
             p['foo:', foo],
         )
 
@@ -271,7 +290,7 @@ Any arguments specified after ``/`` in your call signature will capture query pa
     <p>foo: 3</p>
 
 
-Python doesn't allow a ``/`` at the beginning of the call signature, so use ``_`` (single underscore) before the ``/`` if there are no route parameters:
+You can capture query parameters without route parameters:
 
 .. code-block:: python
     :caption: app/greet_me/__index__.py
@@ -279,7 +298,7 @@ Python doesn't allow a ``/`` at the beginning of the call signature, so use ``_`
     from blu.html import p
 
 
-    def __page__(_, /, my_name):
+    def __page__(*, my_name):
         return p['Hello ', my_name, '!']
 
 .. code-block:: html
@@ -295,7 +314,7 @@ You can set default values for query parameters:
     from blu.html import p
 
 
-    def __page__(_, /, my_name='World'):
+    def __page__(*, my_name='World'):
         return p['Hello ', my_name, '!']
 
 .. code-block:: html
@@ -311,7 +330,57 @@ You can also use ``**kwargs`` for query parameters:
     from blu.html import p
 
 
-    def __page__(_, /, my_name, **kwargs):
+    def __page__(**kwargs):
+        greeting = kwargs.get('greeting', 'Hello')
+        return p[greeting, '!']
+
+.. code-block:: html
+    :caption: GET /greet_me?greeting=Hi
+
+    <p>Hi!</p>
+
+.. note::
+
+    If you capture query parameters using ``**kwargs`` while also capturing route paramaters, use ``/`` to avoid name collisions:
+
+    .. code-block:: python
+        :caption: app/show_params/__index__.py
+
+        from blu.html import p
+
+
+        def __page__(x, /, **kwargs):
+            return p[
+                div['x: ', x],
+                div['**kwargs:'],
+                ul[
+                    li[f'{k}: ', v] for k, v in **kwargs
+                ],
+            ]
+
+.. code-block:: html
+    :caption: GET /show_params/A?x=1&y=2&z=3
+
+    <p>
+        <div>x: A</div>
+        <div>**kwargs:</div>
+        <ul>
+            <li>x: 1</li>
+            <li>y: 2</li>
+            <li>z: 3</li>
+        </ul>
+    </p>
+
+
+This can also be paired with non-``**kwarg`` query parameters:
+
+.. code-block:: python
+    :caption: app/greet_me/__index__.py
+
+    from blu.html import p
+
+
+    def __page__(*, my_name, **kwargs):
         greeting = kwargs.get('greeting', 'Hello')
         return p[greeting, ' ', my_name, '!']
 
@@ -339,18 +408,18 @@ Since a call to a ``__page__`` handler in a ``__default__.py`` file usually resu
 
     <p>Remaining path: bar/baz</p>
 
-This can be used alongside route parameters and query parameters. In this case, it should come before the ``/``:
+This can be used alongside route parameters and query parameters. In this case, it should come before the ``*``:
 
 .. code-block:: python
     :caption: app/_id_/__default__.py
 
     from blu.html import p
 
-    def __page__(id, path__, /, baz):
+    def __page__(id, path__, *, baz):
         return (
             p['ID: ', id],
-            p['Remaining path:', __],
-            p['baz:', baz],
+            p['Remaining path: ', path__],
+            p['baz: ', baz],
         )
 
 .. code-block:: html

{blu_react-0.0.2 → blu_react-0.0.3}/docs/api-reference/index.rst

@@ -8,6 +8,6 @@ API Reference
    blu
    blu.html
    js
-   pyscript
+   pyodide
    file-conventions
    cli

blu_react-0.0.3/docs/api-reference/js.rst

@@ -0,0 +1,35 @@
+``js`` (client-only)
+====================
+
+The JavaScript global scope is available in the client-side Python environment through the ``js`` module:
+
+.. code-block:: python
+
+    from blu import is_client
+
+    __client__ = True
+
+
+    if is_client:
+        from js import Promise, addEventListener, alert, document
+
+
+.. note::
+
+    ``js`` can only be imported in a client context.
+
+    .. code-block:: python
+
+        from blu import is_client
+
+        # Wrong!
+        from js import document
+
+        # Right.
+        if is_client:
+            from js import document
+
+
+By default, Blu runs Python on the client using the MicroPython interpreter. You can view MicroPython's documentation on `in-browser type conversions <https://github.com/micropython/micropython/blob/master/ports/webassembly/README.md#proxying>`_ to learn how JavaScript types are converted into Python.
+
+If you :doc:`opt in to using Pyodide </appendices/choosing-an-interpreter>` as your client-side Python interpreter, you can learn about Pyodide's type conversions `here <https://pyodide.org/en/stable/usage/type-conversions.html>`_.

blu_react-0.0.3/docs/api-reference/pyodide.rst

@@ -0,0 +1,36 @@
+.. _pyscript:
+
+``pyodide`` (opt-in)
+====================
+
+By default, Blu uses MicroPython as its client-side Python interpreter. However, you can also :doc:`opt in to using Pyodide </appendices/choosing-an-interpreter>` as your Python interpreter.
+
+Pyodide provides an additional client-side package called ``pyodide``, which provides utilities for using Python in the browser.
+
+.. code-block:: python
+
+    from blu import is_client
+
+    if is_client:
+        from pyodide.http import pyfetch
+    
+    response = await pyfetch('https://www.example.com/api/v2/data')
+    print(await response.json())
+
+.. note::
+
+    The ``pyodide`` package can only be imported in a client context.
+
+    .. code-block:: python
+
+        from blu import is_client
+
+        # Wrong!
+        from pyodide.http import pyfetch
+
+        # Right.
+        if is_client:
+            from pyodide.http import pyfetch
+
+
+For more information on the ``pyodide`` package, see the package's official `API reference <https://pyodide.org/en/stable/usage/api/python-api.html>`_.

blu_react-0.0.3/docs/appendices/choosing-an-interpreter.rst

@@ -0,0 +1,28 @@
+.. _choosing-an-interpreter:
+
+Choosing an Interpreter
+=======================
+
+The two most popular in-browser Python interpreters are Pyodide and MicroPython. Blu supports both, but uses MicroPython by default. To use Pyodide, set the interpreter in ``__settings__.py``:
+
+.. code-block:: python
+    :caption: app/__settings__.py
+
+    INTERPRETER = 'pyodide'
+
+
+Pyodide is CPython compiled to WebAssembly and has almost all the features available in other CPython distributions. MicroPython is a slim partial implementation of Python mainly used in microcontrollers. The main trade-offs are shown below:
+
+.. list-table::
+    :header-rows: 1
+
+    * - Pyodide
+      - MicroPython
+    * - Implements almost all features of the Python language.
+      - Implements Python 3.10, with a few additional features from later versions.
+    * - Includes almost the entire Python standard library.
+      - Includes a small subset of the Python standard library, with some standard library packages available to be installed.
+    * - Provides Python APIs for interacting with the browser environment, as well as access to the JavaScript global scope.
+      - Only provides access to the JavaScript global scope.
+    * - Can have slow initial loads.
+      - Initial page load is almost instant.

blu_react-0.0.3/docs/appendices/index.rst

@@ -0,0 +1,10 @@
+.. _appendices:
+
+Appendices
+==========
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Contents:
+
+   choosing-an-interpreter

{blu_react-0.0.2 → blu_react-0.0.3}/docs/conf.py

@@ -49,6 +49,8 @@ html_css_files = ["styles.css"]
 
 todo_include_todos = True
 
+autosectionlabel_prefix_document = True
+
 # autodoc
 
 autoclass_content = "both"

{blu_react-0.0.2 → blu_react-0.0.3}/docs/contributing.rst

@@ -10,13 +10,15 @@ Setup
 
 3. Ensure `uv <https://docs.astral.sh/uv/>`_ is installed.
 
+
+
 4. Run tests with ``uv run pytest``. If the tests pass, you have successfully set up your development environment and are ready to make a change to the codebase.
 
 
 Making Changes
 --------------
 
-1. Update the :ref:`API Reference` (and :ref:`User Guide`, if appropriate) to reflect intended changes.
+1. Update the :ref:`api-reference/index:API Reference` (and :ref:`user-guide/index:User Guide`, if appropriate) to reflect intended changes.
 
 2. Write tests or update existing ones to test the feature or bug fix you are implementing.
 
@@ -29,4 +31,4 @@ Making Changes
 Make a Pull Request Early
 -------------------------
 
-You don't have to wait until your changes are ready to merge to make a pull request. In fact, making a pull request early allows you to get early feedback, preventing you from doing significant work that is later rejected. For example, a pull request with just proposed documentation changes allows revisions to be made before anything is implemented, and a pull request with initial work allows revisions to be made to the implementation stategy before more work has been put into the implementation.
+You don't have to wait until your changes are ready to merge to make a pull request. In fact, making a pull request early allows you to get early feedback, preventing you from doing significant work that is later rejected. For example, a pull request with only proposed documentation changes allows revisions to be made before anything is implemented, and a pull request with initial work allows revisions to be made to the implementation stategy before more work has been put into the implementation.

{blu_react-0.0.2 → blu_react-0.0.3}/docs/index.rst

@@ -16,4 +16,5 @@ Welcome Blu's documentation.
    quickstart
    user-guide/index
    api-reference/index
+   appendices/index
    contributing

{blu_react-0.0.2 → blu_react-0.0.3}/docs/install.rst

@@ -1,5 +1,3 @@
-.. _install:
-
 Install
 =======
 

{blu_react-0.0.2 → blu_react-0.0.3}/docs/quickstart.rst

@@ -1,7 +1,7 @@
 Quickstart
 ==========
 
-If you haven't already, :ref:`install Blu <install>`.
+If you haven't already, :ref:`install Blu <install:Install>`.
 
 Next, create a directory called ``app``. Inside this directory, create a file called ``__index__.py`` with the following content:
 
@@ -39,4 +39,4 @@ This will start up the app and output a url where you can access it (``http://12
 
 If it works, you've created a simple web app using Blu.
 
-To learn how make more complex pages in Blu, see :ref:`Creating Pages`.
+To learn how make more complex pages in Blu, see :ref:`user-guide/creating-pages:Creating Pages`.

blu_react-0.0.3/docs/requirements.txt

@@ -0,0 +1,2 @@
+sphinx-copybutton>=0.5.2
+aiofiles~=25.1.0

{blu_react-0.0.2 → blu_react-0.0.3}/docs/user-guide/client-side-rendering.rst

@@ -224,7 +224,7 @@ What's going on here is:
 7. React sets the state value to 1, and then calls *MyClientElement*'s render function again. This time, the current value is 1, so *click_count* is 1, so the button will say "Click Count: 1".
 8. If the user clicks the button again, the current value will again be incremented, and the render function will be called again, resulting in a button that says "Click Count: 2".
 
-.. note:: :func:`use_state <blu.use_state>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`Hooks` for more details.
+.. note:: :func:`use_state <blu.use_state>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`user-guide/client-side-rendering:Hooks` for more details.
 
 
 Directly Manipulating Rendered Elements
@@ -272,7 +272,7 @@ What's happening here is:
     1. Gets the current value of *input_ref* using ``[:]`` (remember that the current value is the rendered input element).
     2. Calls the *focus()* method on that value. Because the current value is a rendered HTML input element, calling its *focus()* method causes the input element to receive the browser's focus.
 
-.. note:: :func:`use_ref <blu.use_ref>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`Hooks` for more details.
+.. note:: :func:`use_ref <blu.use_ref>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`user-guide/client-side-rendering:Hooks` for more details.
 
 
 Performing an Action Immediately After Rendering
@@ -316,7 +316,7 @@ What's happening here:
 7. This causes an alert modal to pop up in front of the page with the provided message.
 8. The user can then dismiss the alert modal.
 
-.. note:: :func:`use_effect <blu.use_effect>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`Hooks` for more details.
+.. note:: :func:`use_effect <blu.use_effect>` is a special type of function used in React called a *hook*. There are specific rules you have to follow when using hooks. See :ref:`user-guide/client-side-rendering:Hooks` for more details.
 
 .. note::
 
@@ -355,7 +355,7 @@ What's happening here:
 Accessing Server-Side Resources from the Client
 -----------------------------------------------
 
-Sometimes you'll need to access server-side resources after a page has loaded, usually in response to user input. You can do using the :func:`@blu.server` decorator, which exposes a server-side function to be called client-side.
+Sometimes you'll need to access server-side resources after a page has loaded, usually in response to user input. You can do so using the :func:`@blu.server` decorator, which exposes a server-side function to be called client-side.
 
 .. code-block:: python
     :caption: app/hello_module.py

{blu_react-0.0.2 → blu_react-0.0.3}/docs/user-guide/creating-pages.rst

@@ -3,7 +3,7 @@
 Creating Pages
 ==============
 
-The :ref:`Quickstart` guide shows how to make a simple page using Blu.
+The :ref:`quickstart:Quickstart` guide shows how to make a simple page using Blu.
 
 This section goes into greater depth on how to generate user interfaces using Blu.
 
@@ -11,7 +11,7 @@ This section goes into greater depth on how to generate user interfaces using Bl
 HTML Elements
 -------------
 
-The :ref:`Quickstart` guide shows how to make a simple page with html, head, and body elements:
+The :ref:`quickstart:Quickstart` guide shows how to make a simple page with html, head, and body elements:
 
 .. code-block:: python
 
@@ -140,7 +140,7 @@ You can set the HTML attributes of an element by calling it as a function:
 
 .. note::
 
-    Event-handling attributes like "onClick" are only supported in client-side rendering (see :ref:`Client-Side Rendering` for more details).
+    Event-handling attributes like "onClick" are only supported in client-side rendering (see :ref:`user-guide/client-side-rendering:Client-Side Rendering` for more details).
 
     .. code-block:: python
 

{blu_react-0.0.2 → blu_react-0.0.3}/docs/user-guide/deploying-your-app.rst

@@ -5,7 +5,7 @@ Blu is an ASGI framework, meaning it doesn't include tools for running a product
 
 If you're familiar with ASGI frameworks, you may be wondering, "Where is the ASGI app?" The app you'll use to deploy is :data:`blu.app`.
 
-For example, to deploy your app using `Uvicorn <uvicorn.org>`_, run the following from your ``app/`` directory's parent directory (not the ``app/`` directory itself):
+For example, to deploy your app using `Uvicorn <https://uvicorn.dev>`_, run the following from your ``app/`` directory's parent directory (not the ``app/`` directory itself):
 
 .. code-block:: console