Overall, I would keep the titles in the navigation bar short (further description can be given in their overview/intro page), and not too deeply nested (3 layers as a rule of thumb?).
Since this is the users' main navigation tool, it should be easy to skim.
More specifically, I suggest:
current features > features
custom schemas for new features > split it into customization and adding features
defining filters for searches > GUI queries
querying and performing Data Science > API queries? Maybe this can be combined with GUI queries under a common section queries? Maybe data science should also be preserved, but this would be more like examples...
uploading and publishing data > uploading & publishing
visualizing properties in the entry page > entries page
writing a parser plugin > contributing or plugins
If we have a system similar to Obsidian, we could also consider using hashtags to mark specific files or paragraphs, e.g. #GUI, #contributing, #template, etc.
Overall, I would keep the titles in the navigation bar short (further description can be given in their overview/intro page), and not too deeply nested (3 layers as a rule of thumb?). Since this is the users' main navigation tool, it should be easy to skim. More specifically, I suggest:
If we have a system similar to Obsidian, we could also consider using hashtags to mark specific files or paragraphs, e.g.
#GUI
,#contributing
,#template
, etc.