Website docs problem

[PavelsDenisovs]

Here and here docs are most likely outdated.

• dashboard_output configuration property doesn't exist.
• Based on the current filesystem layout, it seems the correct path would be $OUTPUT_PATH/$ORG_NAME/dashboards/$GRAFANA_FOLDER_NAME instead of $OUTPUT_PATH/dashboards/$GRAFANA_FOLDER_NAME should be a correct path.
• dashboards/dashboards/Example doesn't exist.
• $OUTPUT_PATH is actually a path for all the data of Grafana gdg stores, so I would even call it $LOCAL_REPO, for example. This variable is also about importing dashboards, so "output" is no more correct?
• org_main-org folder is never mentioned.

Since this is in Getting Started, I think it affects first-time understanding of gdg and its filesystem model.

I wanted to raise this first before attempting any changes. If you think it makes sense for me to help clarify or update this section, I'm happy to do so.

[safaci2000]

This is great. Thanks for calling this out. I get blinders looking at the same code/docs I don't always catch all these discrepancies.

Feel free to do a PR when you have time.

to address the points you raised.

1. 100% that went away a while ago when I started using conventions rather than a path. You can define the output_path which defines where the data is written to but it uses the name of the resources relative to that. The path will vary based on the entity if it's scoped per folder or Org level etc.
2. Correct, that is the current convention.
3. Yup, that should be updated. The file tree right below it shows the path but feel free to update that.
4. But it's not necessarily local. It is exactly what it was named. If the output is an S3 bucket it will still use that path if I'm not mistaken. Even if it's not used by S3, output sounds better to me. It's the output aka destination where files are saved. LocalRepo is a lot less intuitive IMO. I also prefer not to change existing configs unless we absolutely have to. 0.9.x had a bunch of breaking changes but it was all due to new features or behavioral changes. If there in no functional change let's leave the names as they are.
5. You can add that in, though I would also mention that it's a default. That value is based on what you set your organization_name to. The default on a clean grafana install is: Main Org. which once it's turned into a slug with the org prefix becomes: org_main-org. So if the value is missing, it'll default to org_main-org, otherwise it'll use whatever the user sets.

[safaci2000]

I would add one more action item if you want to pick this up. https://software.es.net/gdg/docs/tutorials/working-with-nested-folders/ is now deprecated. Nested folders are the default behavior in both grafana and GDG. You can either re-write it to reflect that (If it has any value ) or delete the corresponding file.