[Doc] Update documentation structure and content: add overview section, revise...

[Doc] Update documentation structure and content: add overview section, revise project name, and change theme to Furo (#39)

docs/conf.py

@@ -2,7 +2,7 @@
 import os
 import sys
 
-import tlcpack_sphinx_addon
+# import tlcpack_sphinx_addon
 
 # -- General configuration ------------------------------------------------
 
@@ -11,12 +11,13 @@ sys.path.insert(0, os.path.abspath("../"))
 autodoc_mock_imports = ["torch"]
 
 # General information about the project.
-project = "tilelang"
+project = "Tile Language <br>"
 author = "Tile Lang Contributors"
 copyright = "2025-2025, %s" % author
 
 # Version information.
 
+# TODO: use the version from project metadata
 version = "0.1.0"
 release = "0.1.0"
 
@@ -27,6 +28,8 @@ extensions = [
     "sphinx.ext.autodoc",
     "sphinx.ext.napoleon",
     "sphinx_reredirects",
+    "sphinx.ext.mathjax",
+    "sphinx.ext.autosummary",
 ]
 
 redirects = {"get_started/try_out": "../index.html#getting-started"}
@@ -46,23 +49,18 @@ todo_include_todos = False
 
 # -- Options for HTML output ----------------------------------------------
 
-# The theme is set by the make target
-import sphinx_rtd_theme
-
-html_theme = "sphinx_rtd_theme"
-html_theme_path = [sphinx_rtd_theme.get_html_theme_path()]
+html_theme = "furo"
 
 templates_path = []
 
-html_static_path = []
+html_static_path = ["_static"]
 
 footer_copyright = "© 2025-2025 Tile Language"
 footer_note = " "
 
-html_logo = "_static/img/logo-row.svg"
-
 html_theme_options = {
-    "logo_only": True,
+    "light_logo": "img/logo-row.svg",
+    "dark_logo": "img/logo-row.svg",
 }
 
 header_links = [
@@ -84,6 +82,6 @@ html_context = {
     # "version_selecter": "",
 }
 
-# add additional overrides
-templates_path += [tlcpack_sphinx_addon.get_templates_path()]
-html_static_path += [tlcpack_sphinx_addon.get_static_path()]
+# # add additional overrides
+# templates_path += [tlcpack_sphinx_addon.get_templates_path()]
+# html_static_path += [tlcpack_sphinx_addon.get_static_path()]

docs/get_started/overview.rst

+The Tile Language: A Brief Introduction
+===============================
+
+.. _sec-overview:
+
+Programming Interface
+---------------------
+
+The figure below depicts how **TileLang** programs are progressively lowered from a high-level description to hardware-specific executables. We provide three different programming interfaces—targeted at **Beginner**, **Developer**, and **Expert** users—that each reside at different levels in this lowering pipeline. The **Tile Language** also allows mixing these interfaces within the same kernel, enabling users to work at whichever level of abstraction best suits their needs.
+
+.. _fig-overview:
+
+.. figure:: ../_static/img/overview.png
+   :align: center
+   :width: 50%
+   :alt: Overview
+
+   High-level overview of the TileLang compilation flow.
+
+Programming Interfaces
+----------------------
+
+1. **Beginner Level (Hardware-Unaware)**
+   - Intended for users who need to write code that is independent of specific hardware details.  
+   - The goal is to let developers focus on the basic logic without worrying about memory hierarchies or hardware-specific optimizations.  
+   - *Note:* This interface is not yet fully implemented.
+
+2. **Developer Level (Hardware-Aware with Tile Library)**
+   - Designed for developers who have a basic understanding of GPU memory hierarchies and performance considerations.  
+   - Provides a **Tile Library**, containing predefined operations and patterns optimized for various hardware architectures.  
+   - Users at this level can leverage these ready-made primitives without diving into low-level threading details.
+
+3. **Expert Level (Hardware-Aware with Thread Primitives)**
+   - For highly experienced users who have an in-depth understanding of low-level hardware characteristics (e.g., threading models, memory coalescing).  
+   - Offers direct access to **thread primitives** and other low-level constructs, allowing for fine-grained control of performance-critical kernels.  
+   - This level grants maximum flexibility for specialized optimizations tailored to specific GPU or multi-core architectures.
+
+Compilation Flow
+----------------
+
+1. **Tile Program**  
+   A high-level specification of the computation. Depending on the user’s expertise, they may write a purely hardware-unaware tile program or incorporate constructs from the Tile Library or thread primitives.
+
+2. **Tile Program with Tile Library**  
+   When developers choose from the Tile Library, the original Tile Program is expanded with specialized library calls. These calls encapsulate efficient implementation patterns for different operations.
+
+3. **Tile Program with Thread Primitives**  
+   Expert-level developers can explicitly use low-level threading constructs to hand-optimize data layout, synchronization, and memory usage.
+
+4. **IRModule**  
+   After the program is composed with libraries or thread primitives, it is lowered to an intermediate representation (IR) that captures the necessary hardware details.
+
+5. **Source Code Generation (C/CUDA/HIP/LLVM/…)**  
+   From the IR, the system generates target-specific source code. This source code is tuned for the desired backends or GPU architectures (e.g., NVIDIA, AMD).
+
+6. **Hardware-Specific Executable/Runtime**  
+   Finally, the generated source is compiled into hardware-specific executables, ready to run on the corresponding devices. The pipeline supports multiple GPU backends and can be extended to additional architectures.
+
+
+.. _sec-tile_based_programming_model:
+
+Tile-based Programming Model
+----------------------------
+
+Figure :ref:`fig-matmul_example` provides a concise matrix multiplication (GEMM) example in ``TileLang``, 
+illustrating how developers can employ high-level constructs such as tiles, memory placement, pipelining, 
+and operator calls to manage data movement and computation with fine-grained control.
+In particular, this snippet (Figure :ref:`fig-matmul_example` (a)) demonstrates how multi-level tiling 
+leverages different memory hierarchies (global, shared, and registers) to optimize bandwidth utilization 
+and reduce latency.
+Overall, Figure :ref:`fig-matmul_example` (b) showcases how the Python-like syntax of ``TileLang`` 
+allows developers to reason about performance-critical optimizations within a user-friendly programming model.
+
+.. _fig-matmul_example:
+
+.. figure:: ../_static/img/MatmulExample.png
+   :align: center
+   :width: 100%
+   :alt: GEMM with Multi-Level Tiling on GPUs
+
+   Optimizing GEMM with Multi-Level Tiling on GPUs via ``TileLang``.
+
+Tile declarations
+~~~~~~~~~~~~~~~~~
+
+At the heart of our approach is the notion of *tiles* as first-class objects in the programming model.
+A tile represents a shaped portion of data, which can be owned and manipulated by a warp, thread block, 
+or equivalent parallel unit.
+In the ``Matmul`` example, the ``A`` and ``B`` buffers are read in tiled chunks (determined by ``block_M``, 
+``block_N``, ``block_K``) inside the kernel loop.
+With ``T.Kernel``, ``TileLang`` defines the execution context, which includes the thread block index (``bx`` 
+and ``by``) and the number of threads.
+These contexts can help compute the index for each thread block and make it easier for ``TileLang`` 
+to automatically infer and optimize memory access and computation.
+Additionally, these contexts allow users to manually control the behavior of each independent thread within 
+a thread block.
+
+Explicit Hardware Memory Allocation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A hallmark of ``TileLang`` is the ability to explicitly place these tile buffers in the hardware memory hierarchy.
+Rather than leaving it to a compiler's opaque optimization passes, ``TileLang`` exposes user-facing intrinsics 
+that map directly to physical memory spaces or accelerator-specific constructs.
+In particular:
+
+- ``T.alloc_shared``: Allocates memory in a fast, on-chip storage space, which corresponds to shared memory on NVIDIA GPUs.
+  Shared memory is ideal for caching intermediate data during computations, as it is significantly faster than global memory
+  and allows for efficient data sharing between threads in the same thread block.
+  For example, in matrix multiplication, tiles of matrices can be loaded into shared memory
+  to reduce global memory bandwidth demands and improve performance.
+
+- ``T.alloc_fragment``: Allocates accumulators in fragment memory, which corresponds to register files on NVIDIA GPUs.
+  By keeping inputs and partial sums in registers or hardware-level caches, latency is further minimized.
+  Note that in this tile program, each tile allocates the same local buffers as shared memory,
+  which might seem counterintuitive, as shared memory is generally faster but more abundant,
+  whereas register file space is limited.
+  This is because the allocation here refers to the register files for an entire thread block.
+  ``TileLang`` uses a Layout Inference Pass during compilation to derive a Layout object ``T.Fragment``,
+  which determines how to allocate the corresponding register files for each thread.
+  This process will be discussed in detail in subsequent sections.
+
+Data transfer between global memory and hardware-specific memory can be managed using ``T.copy``.
+Furthermore, hardware-specific buffers can be initialized using ``T.clear`` or ``T.fill``.
+For data assignments, operations can also be performed in parallel using ``T.Parallel``,
+as demonstrated in Layout Inference Pass in the following sections.
+
+
+.. _fig-layout_inference:
+
+.. figure:: ../_static/img/LayoutInference.png
+   :align: center
+   :width: 100%
+   :alt: GEMM with Multi-Level Tiling on GPUs

docs/index.rst

@@ -9,22 +9,25 @@ By employing a Pythonic syntax with an underlying compiler infrastructure on top
 tile-lang allows developers to focus on productivity without sacrificing the 
 low-level optimizations necessary for state-of-the-art performance.
 
+.. toctree::
+   :maxdepth: 2
+   :caption: GET STARTED
 
-
-
+   get_started/Installation.rst
+   get_started/overview.rst
 
 .. toctree::
    :maxdepth: 2
-   :caption: Get Started
-   :hidden:
+   :caption: LANGUAGE REFERENCE
 
-   get_started/Installation.rst
-   get_started/language_ref.rst
+   language_ref/ast.rst
+   language_ref/primitives.rst
+   language_ref/tilelibrary.rst
+   
 
 
 .. toctree::
    :maxdepth: 1
    :caption: Privacy
-   :hidden:
 
    privacy.rst

docs/language_ref/ast.rst

+Tile Language AST
+==================

docs/language_ref/primitives.rst

+Tile Language: Primitives
+=========================

docs/get_started/language_ref.rst → docs/language_ref/tilelibrary.rst

-Language reference
+Tile Language: TileLibrary
 =========================
 
 T.Kernel

docs/requirements.txt

@@ -2,10 +2,9 @@ fastapi
 pydantic
 sphinx == 5.2.3
 sphinx-reredirects==0.1.2
-sphinx-rtd-theme
 sphinx-tabs == 3.4.1
 sphinx-toolbox == 3.4.0
 sphinxcontrib-napoleon==0.7
 sphinxcontrib_httpdomain==1.8.1
-git+https://github.com/xwhzz/tlcpack-sphinx-addon.git
+furo
 uvicorn