v1.15: String comparison filter (#3256)

Author: guimachiavelli

learn/filtering_and_sorting/filter_expression_reference.mdx

@@ -69,14 +69,20 @@ genres != action
 
 ### Comparison (`>`, `<`, `>=`, `<=`)
 
-The comparison operators (`>`, `<`, `>=`, `<=`) select documents satisfying a comparison. Comparison operators only apply only to numerical values.
+The comparison operators (`>`, `<`, `>=`, `<=`) select documents satisfying a comparison. Comparison operators apply to both numerical and string values.
 
 The expression below returns all documents with a user rating above 85:
 
 ```
 rating.users > 85
 ```
 
+String comparisons resolve in lexicographic order: symbols followed by numbers followed by letters in alphabetic order. The expression below returns all documents released after the first day of 2004:
+
+```
+release_date > 2004-01-01
+```
+
 ### `TO`
 
 `TO` is equivalent to `>= AND <=`. The following expression returns all documents with a rating of 80 or above but below 90:

learn/filtering_and_sorting/working_with_dates.mdx

@@ -14,7 +14,7 @@ In this guide, you will learn about Meilisearch's approach to date and time valu
 
 ## Preparing your documents
 
-To filter and sort search results chronologically, your documents must have at least one numeric field containing a [UNIX timestamp](https://kb.narrative.io/what-is-unix-time).
+To filter and sort search results chronologically, your documents must have at least one field containing a [UNIX timestamp](https://kb.narrative.io/what-is-unix-time). You may also use a string with a date in a format that can be sorted lexicographically, such as `"2025-01-13"`.
 
 As an example, consider a database of video games. In this dataset, the release year is formatted as a timestamp:
 
@@ -41,39 +41,11 @@ As an example, consider a database of video games. In this dataset, the release
 ]
 ```
 
-If your date field is expressed in a format other than a numeric timestamp, like [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html), you must convert it before indexing it with Meilisearch.
-
-Most programming languages have built-in tools to help you with this process. The JavaScript example below converts a game's release date, `"2018-10-18"`, to a numeric timestamp:
-
-```js
-let game = {
-  "id": 0,
-  "title": "Return of the Obra Dinn",
-  "genre": "adventure",
-  "release_date": "2018-10-18T00:00Z"
-};
-
-const timestampInMilliseconds = Date.parse(game.release_date); // Date.parse returns the timestamp in milliseconds
-const timestamp = timestampInMilliseconds / 1000; // UNIX timestamps must be in seconds
-
-game = {
-  "id": 0,
-  "title": "Return of the Obra Dinn",
-  "genre": "adventure",
-  "release_date": "2018-10-18T00:00Z",
-  "release_timestamp": timestamp
-};
-```
-
-<Tip>
-When preparing your dataset, it can be useful to leave the original date and time fields in your documents intact. In the example above, we keep the `release_date` field because it is more readable than the raw `release_timestamp`.
-</Tip>
-
-After adding a numeric timestamp to all documents, [index your data](/reference/api/documents#add-or-replace-documents) as usual. The example below adds a <a id="downloadVideogames" href="/assets/datasets/videogames.json" download="videogames.json">videogame dataset</a> to a `games` index:
+Once all documents in your dataset have a date field, [index your data](/reference/api/documents#add-or-replace-documents) as usual. The example below adds a <a id="downloadVideogames" href="/assets/datasets/videogames.json" download="videogames.json">videogame dataset</a> to a `games` index:
 
 <CodeSamplesDateGuideIndex1 />
 
-## Filtering by timestamp
+## Filtering by date
 
 To filter search results based on their timestamp, add your document's timestamp field to the list of [`filterableAttributes`](/reference/api/settings#update-filterable-attributes):
 
@@ -83,7 +55,7 @@ Once you have configured `filterableAttributes`, you can filter search results b
 
 <CodeSamplesDateGuideFilter1 />
 
-## Sorting by timestamp
+## Sorting by date
 
 To sort search results chronologically, add your document's timestamp field to the list of [`sortableAttributes`](/reference/api/settings#update-sortable-attributes):