Most of the words in sample text should be in dictionary entries. Link the ones that are easy enough to find, makes the sample section more interesting for those who cant understand the language as-is.

See stscoundrel/cleasby-vigfusson-next#375

Like in couple of sibling projects, runes alone may provide little context to casual reader. Might want to mention runes were used to write Norse languages in Scandinavia from x to y centuries.

Keeping it relevant to Old Norwegian, something among the lines of:
Medieval Runes were used in Norway from 11th to 15th centuries.

Should provide alternative avenue for building all ISR pages.

Current problem: many more pages that can be build & deployed to Vercel. There is hard limit of 16 00 files. Once the project is deployed, it can generate as many more as it needs. But it has to happen after deployment.
Current solution: use ISR to generate pages as users open them. Downside is that the first load can then be slow. Other approach is to use Gangleri, a tool to walk sitemaps, therefore triggering rebuilds. However, that is slow as it makes separate request for each and can be spammy.

New solution:

• Add API endpoint
• Protect with env secret. Important as hell, as this could potentially cause a lot of processing spam.
• Trigger revalidate of either all pages, or a subset based on some param. See how long rebuild takes etc.

Could be portion of "Gammelnorsk homiliebok" or "Kongespeilet", whatever manuscript has clear enough Old Norwegian text.

Possibly from one of these:

• https://no.wikipedia.org/wiki/Gammelnorsk_homiliebok#/media/Fil:Gammelnorsk_homiliebok.jpg
• https://upload.wikimedia.org/wikipedia/commons/9/90/Kongespeilet.jpg

Preferably parsed so that it contains links to entries in this dictionary.

Current search loads whole available dictionary. While it does make consequent searches fast, it makes initial load slower and affects other pages which may prefetch the search page.

Taking a page from Old Swedish dictionarys book:

• Add search endpoint to API routes
• Alter the search form to query that for results.
• Consider simple memory cache -> be it on client or API end.

Will end up making more requests to the cloud function, but overall payloads moved around will be definitely smaller. The full dictionary json is around 6MB, no need to accidentally prefech it by opening the frontpage.

Word definition contain automatically generated younger futhark rune transcription. However, runes used in times of old norwegian would be medieval futhork, not the earlier younger futhark,

Switch library that is used, should be drop-in replacement as interface is the same.

Letter "ö" did not really see use in Old Norwegian, but it has probably been picked to this book through to modern Icelandic usage. Or simply due to difficulties of printing the original character in 1800s.

In short, whenever "ö" appears the dictionary should provide older form with letter "ǫ", o caudata.

So for headword like "völlr", alternative elder form of "vǫllr" should be provided.

Same feature already exists in Cleasby & Vigfusson ON dictionary.

Using scandinavian-dictionary-crosslinker

Currently uses long branch runes (danish), while short twig (norwegian / swedish) might make more sense. Switch the dialect.

Disable prefech on links. Currently majority of links in the site are prefetched on background. While it is generally a very nice behavior, changes in Vercel infra pricing make this uneconomical. Therefore:

• Either use prefetch={false} in links to only fetch them on hover
• Or replace them with plain old a links. Prefetch is pretty much the only advantage of next/link.

Tests still use old react-dom. Update.& refactor

The written norwegian in the dictionary is not bokmål or nynorsk, but older variant from before current standards. Might make sense to mention it. Check what the written dano-norwegian text was called, if anything.

Sisters projects of this dictionary have "what is x language" section in frontpage. Seems reasonable to add one here, currently only has notes of the written language.

Word pages do not mention that definitions are in norwegian. For example:

Meaning of Old Norwegian word "resignera"

could be

Meaning of Old Norwegian word "resignera" in Norwegian (of late 19th century?).

While you're at it, also add Medieval Futhork runes link to footer

Seems some entries are not in correct alphabetical order. For example, see bœna in letter b

Currently only has section on Old Norse. While the "About" section touches on old norwegian, why not add a proper section for it

Check Lighthouse. Probably jumps from H2 to H4. Use proper heading & class instead.