awesome-godot VS Arrow

Some more listed here: https://github.com/godotengine/awesome-godot#projects

-A curated list of free resources for Godot -Heartbeast tutorial and channel

I just did some googling and and I found this: https://github.com/godotengine/awesome-godot

No, i don't really have a general advice for that..all depends on what you want to build. I'd say start simple but as it grows you have to make sure your architecture stays clean, otherwise the whole thing becomes unmanageable. If you want to look at other big open source applications done in Godot look at Pixelorama and MaterialMaker (this one even got an Epic Mega Grant). There is also this list with great apps/pluings etc: https://github.com/godotengine/awesome-godot

The Awesome Godot GitHub Repository has some Template content, some Demos, and some Games (some of which point to GitHub repositories with source code).

What kind of content goes in the list? Is it limited to just GDScript/C#/GDNative addons that can be downloaded from the Asset Library in the editor, or also projects that can be downloaded from the Asset Library in the project manager, or also modules that require recompiling the engine? Is this a general-purpose list like https://github.com/godotengine/awesome-godot is?

Here you go, that's the gold mine: https://github.com/godotengine/awesome-godot#tutorials

I would recommend you to look at this list of plugins and scripts. There are many nice plugins listed.

One way is to create your narrative in Arrow, then export and use it as a database for your runtime/interpreter. The official HTML-JS runtime is based on the same idea. Arrow uses this runtime to create playable exports (mainly for play-test and review). Yet it means you can use this runtime (with customization) to export text-adventures directly from the editor as well. Another way is to create multiple chapters, scenes, etc. and export them as assets for your game (e.g. each scene or branch as a dialog-tree for your RPG).

Source | Download | Web-App | Project's Wiki

JSON is just a text file with some specific conventions to be easily readable by other programs. Though, I took a look at the Inky's JSON export, and it's kinda convoluted. In your case Arrow might be a better fit. You can also consult with your programmer, since he'll be the person implementing your dialogue in game.

I use Arrow for dialogue/scene planning.

For others who are curious, here is the Arrow GitHub repository.

Arrow v1.0.1 is released and now has the textual save preference I promised.

New release of Arrow (v1.0.1) is out.