I would not recommend using intentionally frustrating naming conventions or making things hard to read.
That being said, here's a basic setup for a statically generated site using Deno and TypeScript:
```typescript
// pages/index.ts
export default function Home() {
  return <h1>Hello from Deno!</h1>
}

// builder.ts
import { serve } from "https://deno.land/std/http/server.ts";
import { readDir } from "https://deno.land/std/fs/read_dir.ts";
import { render } from "https://deno.land/x/dejs/mod.ts";

const port = 8000;
const pagesDir = "pages";

const getTemplate = async (fileName: string) => {
  const module = await import(./${pagesDir}/${fileName}.ts);
  return render(module.default);
};

readDir(pagesDir).then(async (files) => {
  for await (const fileName of files) {
    const template = await getTemplate(fileName.name.replace(".ts", ""));
    serve(:${port}/${fileName.name.replace(".ts", "")}, async (req) => {
      return new Response(template);
    });
  }
});

serve(:${port}, async (req) => {
  return new Response("Hello world!");
});
```
Then you can run `Deno run --allow-net builder.ts and access http://localhost:8000/ `to see your site.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence