Add tests for contentModel/helpers

Author: scriptype

AGENTS.md

@@ -2,6 +2,8 @@
 - Avoid semicolons unless it's absolutely necessary
 - Always use block statements even if it could be a one-liner
 - Always use curly braces {} for control structures (if, for, while, etc.), even if the body is a single statement
+- Keep lines shorter than 80 columns
+- For multiple expressions with logical operators (&&, ||), break lines after each operator
 
 ## Test Assertions Formatting
 - Assertion function call on one line (e.g., `t.ok(`, `t.equal(`, `t.notOk(`)
@@ -10,5 +12,10 @@
 - Add blank line between consecutive assertions
 - Only use `t.plan()` for async or non-deterministic tests where assertions might be skipped; omit for sync tests
 
+## Test File Naming
+- Create test files with the same name and casing as the module being tested, with `.spec.js` appended
+- Example: `FileSystemParser.js` → `FileSystemParser.spec.js`
+- Test files use the glob pattern `src/**/*.spec.js`
+
 ## Test File Operations
 - Use `Promise.all()` to parallelize independent async file operations (mkdir, writeFile, etc.) instead of awaiting them serially

src/compiler/contentModel/helpers.js

@@ -33,17 +33,17 @@ const makeDateSlug = (date) => {
 }
 
 const _sortableValue = (value) => {
-  return typeof value === 'string' ? value.charCodeAt(0) * -1 : value
+  return typeof value === 'string' ? value.toLowerCase().charCodeAt(0) : value
 }
 
 const sort = (items, sortBy, sortOrder) => {
   items.sort((a, b) => {
     const sortableA = _sortableValue(a[sortBy])
     const sortableB = _sortableValue(b[sortBy])
     if (sortOrder === -1) {
-      return sortableA - sortableB
+      return sortableB - sortableA
     }
-    return sortableB - sortableA
+    return sortableA - sortableB
   })
 }
 
@@ -98,4 +98,4 @@ module.exports = {
   sort,
   Markdown,
   safeStringify
-}
+}