update documentation

Author: lovasoa

CHANGELOG.md

@@ -6,6 +6,10 @@
 - Fix a bug where the table component would not add the right css classes to table cells.
 - Better error messages when a CSV import fails (using a `copy` statement and a file upload).
 - Fix a bug where subsequent requests would fail after a failed CSV import on postgres (https://github.com/sqlpage/SQLPage/issues/788)
+- Complete rewrite of the request routing system.
+  - Add support for *"clean URLs"*: Access the file `page.sql` using `https://example.com/page` instead of `https://example.com/page.sql`.
+  - The previous behavior is preserved (the `.sql` suffix is now optional), so this is a new feature, not a breaking change.
+  - Big thanks to @guspower who made big contributions to this feature.
 
 ## 0.32.1 (2025-01-03)
 

examples/official-site/index-old.sql

@@ -9,7 +9,7 @@ SELECT 'hero' as component,
     'From database to data app, fast.' as title,
     '**SQLPage** lets you build data-driven applications in a few SQL queries.
 
-It’s free, [open-source](https://github.com/sqlpage/SQLPage), lightweight, and easy to use.
+It's free, [open-source](https://github.com/sqlpage/SQLPage), lightweight, and easy to use.
     ' as description_md,
     'sqlpage_cover_image.webp' as image,
     TRUE as rounded,
@@ -93,12 +93,10 @@ write an `index.sql`, and in five minutes you turned your database into a websit
 We made all the [optimizations](performance.sql), wrote all of the HTTP request handling code and rendering logic,
 implemented all of the security features, so that you can think about your data, and nothing else.
 
-When SQLPage receives a request with a URL ending in `.sql`, it finds the corresponding
-SQL file, runs it on the database, passing it information from the web request as SQL statement parameters
-[in a safe manner](safety.sql).
+When SQLPage receives a request, it finds the corresponding SQL file (with or without the .sql extension), runs it on the database, passing it information from the web request as SQL statement parameters [in a safe manner](safety.sql).
 When the database starts returning rows for the query,
 SQLPage maps each piece of information in the row to a parameter in the template of a pre-defined component,
-and streams the result back to the user''s browser.
+and streams the result back to the user's browser.
 ' as description_md,
     'server' as icon,
     'purple' as color;

examples/official-site/sqlpage/migrations/47_link.sql

@@ -16,16 +16,17 @@ VALUES
 
 Let''s say you have a database of products, and you want the main page (`index.sql`) to link to the page of each product (`product.sql`) with the product name as a parameter.
 
-In `index.sql`, you can use the `link` function to generate the URL of the product page for each product:
+In `index.sql`, you can use the `link` function to generate the URL of the product page for each product.
 
 ```sql
 select ''list'' as component;
 select
     name as title,
-    sqlpage.link(''product.sql'', json_object(''product_name'', name)) as link;
+    sqlpage.link(''product'', json_object(''product_name'', name)) as link;
 ```
 
-Using `sqlpage.link` is better than manually constructing the URL with `CONCAT(''product.sql?product_name='', name)`, because it ensures that the URL is properly encoded.
+Using `sqlpage.link` is better than manually constructing the URL with `CONCAT(''product?product_name='', name)`,
+because it ensures that the URL is properly encoded.
 The former works when the product name contains special characters like `&`, while the latter would break the URL.
 
 In `product.sql`, you can then use `$product_name` to get the name of the product from the URL parameter:

examples/official-site/your-first-sql-website/custom_urls.sql

@@ -13,7 +13,7 @@ select 'text' as component, '
 
 By default, SQLPage serves the file that matches the URL requested by the client.
 If your users enter `https://example.com/about`, SQLPage will serve the file `about/index.sql` in your project.
-If you create a file named `about.sql`, SQLPage will serve it when the user requests `https://example.com/about.sql`.
+If you create a file named `about.sql`, SQLPage will serve it when the user requests either `https://example.com/about.sql` or `https://example.com/about` (since v0.33, the `.sql` suffix is optional).
 
 But what if you want to handle URLs that don''t match any file in your project ?
 For example, what if you have a blog, and you want nice urls like `example.com/blog/my-trip-to-rome`,

examples/official-site/your-first-sql-website/tutorial.md

@@ -15,7 +15,7 @@ You can open your website locally by visiting [`http://localhost:8080`](http://l
 
 SQLPage should have automatically created a folder called `sqlpage` with a SQLite database file named `sqlpage.db`. This is your website's default database - don't worry, we'll learn how to connect to other databases like PostgreSQL, MySQL, or SQL Server later!
 
-# Your website’s first SQL file
+# Your website's first SQL file
 
 In the root folder of your SQLPage website, create a new SQL file called `index.sql`.
 Open it in a text editor that supports SQL syntax highlighting (I recommend [VSCode](https://code.visualstudio.com/)).
@@ -105,7 +105,7 @@ For more information about the properties that can be set in sqlpage.json, see [
 
 ### Displaying a form
 
-Let’s create a form to let our users insert data into our database. Add the following code to your `index.sql` file:
+Let's create a form to let our users insert data into our database. Add the following code to your `index.sql` file:
 
 ```sql
 SELECT 'form' AS component, 'Add a user' AS title;
@@ -117,7 +117,7 @@ The second SELECT statement adds a field to the form. Since we do not specify a
 
 ### Handling form submission
 
-Nothing happens when you submit the form at the moment. Let’s fix that.
+Nothing happens when you submit the form at the moment. Let's fix that.
 Add the following below the previous code:
 
 ```sql
@@ -136,7 +136,7 @@ from the text field when the user submits the form.
 
 There are two types of parameters you can use in your SQL queries:
 
-- **URL parameters** like **`$ParameterName`**. If you add `?x=1&y=2` to the end of the URL of your page, `$x` will be set to the string `'1'` and `$y` will be set to the string `'2'`. This is useful to create links with parameters. For instance, if you have a database of products, you can create a link to a product page with the URL `product.sql?product_id=12`. Then, in the `product.sql` file, you can use the `$product_id` variable to get the product with the corresponding ID from your database. URL parameters are also sometimes called *query parameters*, or *GET parameters*.
+- **URL parameters** like **`$ParameterName`**. If you add `?x=1&y=2` to the end of the URL of your page, `$x` will be set to the string `'1'` and `$y` will be set to the string `'2'`. This is useful to create links with parameters. For instance, if you have a database of products, you can create a link to a product page with the URL `product?product_id=12` (or `product.sql?product_id=12` - both work). Then, in the `product.sql` file, you can use the `$product_id` variable to get the product with the corresponding ID from your database. URL parameters are also sometimes called *query parameters*, or *GET parameters*.
 - **Form parameters** like **`:ParameterName`**. They refer to the value of the field with the corresponding `name` entered by the user in a [form](/component.sql?component=form). If no form was submitted, it is set to `NULL`. Form parameters are also sometimes called *POST parameters*.
 
 > Note: Currently, if a `$parameter` is not present in the URL, it is first looked for in the form parameters. If it is not found there either, it is set to `NULL`. Please do not rely on this behavior, as it may change in the future.
@@ -152,8 +152,8 @@ INSERT INTO users (name) VALUES ($Username);
 
 ### Displaying data from our database
 
-Now, users are present in our database, but we can’t see them.
-Let’s see how to use data from our database to populate a [list](/component.sql?component=list) component, in order to display the list of users.
+Now, users are present in our database, but we can't see them.
+Let's see how to use data from our database to populate a [list](/component.sql?component=list) component, in order to display the list of users.
 
 Add the following code to your `index.sql` file: