This has to be exposed to the browser still.

It looks like moving the server to the root does the trick.

It's better to re-enable this after highlighting is exposed to the
window.

This has to be self-contained and run in-browser.

There's still something weird going on with parsing.

The code parser needs more logic still.

Likely the best thing to do is to handle link checking during runtime as
we have the info then f...

Now it's async. The caveat is that the Node server needs to run for this
to work.

The idea is that Deno will use this for now until a better way exists.

Likely the setup can be improved still but this allows some of the
content to be defined within ...

The individual pages need more definition and some rendering logic
still.

Given the design is async, these could come from a backend. This is
still missing a bit of logic.

It looks like allowing it breaks tests.

This isn't needed anymore.

The idea is that all external dependencies will go to deps.ts.

This needs better tests. It looks like the code has to be wrapped with a
module node.

This should go to a module of its own.

It looks like the current problem is figuring out how to parse jsx with
swc.

Likely the internals can be cleaned up but this is enough for simple
purposes.

This needs selector logic still for queries.

Now it should be easier to test and port to deno.

This needs more work but it's the right direction.

This needs a bit more work as currently it's broken.

This portion needs more code still. The idea is to declare urls within
indices so that they can ...

Likely this can be done better.

This needs a check against text color still but it's already a bit
better.

This is handy if they have to resolve some data in an async manner. Here
the use case is dynamic...

This can be refined further but it's a bit better now.

A lot has to be restored still.

It looks like the cool thing about the approach is that it's possible to
mix sync with async cod...