t-route (master branch) docs update

[mattw-nws]

Documentation update to go with #502

Additions

• Information specific to master branch, building and config differences specific to ngen

Removals

• Old info relevant only to previous t-route (ngen branch) version
• References to using extern/t-route, which is no longer recommended

Changes

• Removed some content and pointed back to t-route's page instead... this de-scoped documentation really needs to belong in the t-route repo and not in ngen, what is here is now largely specific to running t-route in/with ngen.

Testing

Screenshots

Notes

Todos

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist (automated report can be put here)

Target Environment support

• Linux

[aaraney]

Thanks for adding this @mattw-nws! Ive added a few minor edits that im happy to contribute to your branch if you would like me to do that?

[aaraney]

I would add "Note," to begin this paragraph as it does not affect all installations.

[mattw-nws]

I've sometimes abused > for this kind of thing (blockquote), do you happen to know some GHMD-fu for this use-case?

[aaraney]

I often bold NOTE at the beginning of the line, but that also not great. Im not aware of a more semantic way. I like you block quote approach though. The appearance is more like a text book or blog post.

[aaraney]

Not crucial, but you can use "json5" as the block language type instead of json which enables comment characters. This will fix the formatting of ....

// comment
// ...
[1, 2, 3]
// ...

[mattw-nws]

Neat... I have sometimes used Javascript instead but folks complained.

[mattw-nws]

of course.... ngen's JSON parser doesn't support comments... yet... so that might lead to consternation for some.

[aaraney]

That's a great point. Ill leave it as is!

[aaraney]

Also my Friday is now instantly better having read the work consternation. Excellent word choice!

[mattw-nws]

Thanks for adding this @mattw-nws! Ive added a few minor edits that im happy to contribute to your branch if you would like me to do that?

Please feel free

[aaraney]

Thanks for adding this @mattw-nws! Ive added a few minor edits that im happy to contribute to your branch if you would like me to do that?

Please feel free

Sorry, @mattw-nws, for whatever reason I didnt get a notification that you'd responded to this PR review. Sorry i've let it go a little dormant! Ill make the changes and push them to your branch now.

[aaraney]

@mattw-nws, just made the changes to your branch. If you are happy with the changes, I think we are good to merge.