Can you link to where it says this in the docs? You can use Parse Dashboard to view your data. You'll need to set it up on your backend.

Transferred this as well as it's a docs issue. It should refer to Parse Dashboard - maybe with a link as well.

Thanks.

Keeping this open as the docs issue is not resolved.

Looks like this or similar is in lots of the guides - https://github.com/search?q=org%3Aparse-community+To+make+sure+the+data+was+saved%2C+you+can+look+at+the+Data+Browser+in+your+app+on+Parse.+You+should+see+something+like+this%3A&type=Code

I'm happy to work on this @TomWFox. Should Parse Dashboard have its own section in the docs, or should it just link to the Parse Dashboard github?

Not sure. It might be helpful to have a common Parse Dashboard doc that is present in all the guides (like we have for security etc).

Any thoughts? @mtrezza @davimacedo

It might be helpful to have a common Parse Dashboard doc that is present in all the guides (like we have for security etc).

What would be the benefit of having the same content as a section in every guide compared to having one Parse Dashboard guide and referring to it from other guides where necessary?

Generally, I am for avoiding duplication wherever possible, see also #756.

I don't think the Dashboard needs a separate guide. It wouldn't actually be duplicating the content as all the guides pull the same common docs - see here

And then in the guide config:

- "common/security.md"
- "common/performance.md"
- "common/errors.md"

Got it. What whould be the content of that common Parse Dashboard section?

I think that with increasingly complex functionality of Parse Dashboard, it could make sense at some point to add a Parse Dashboard guide. Just thinking about the new feature "Browse as user" that would benefit from an explanatory documentation. If that aspect is relevant for this current issue.

I was thinking simple intro to Parse Dashboard and maybe installation instructions but that would already start to duplicate on the GitHub readme. Did you have anything in mind @dblythy?

If we removed most of the content from the Github readme that could form a pretty good starting point for a guide. I have wanted to do that with the Parse Server readme & guide for awhile.

I was thinking something along the lines of:

Then with a detailed explanation of the dashboard, as "beginner friendly" as possible, as I think the dashboard could potentially be most users' early experience with Parse. It could be a good way to increase knowledge around CLPs, restricting classes, etc.

I agree with Manuel, there are increasing features, a few of which aren't necessary in the readme. Although it would increase the overall docs management workload, I personally think it could provide benefit.

Sorry for the lack of reply!

I like the idea of increasing knowledge around applying CLPs etc. I'm open to having a separate guide. I think before starting it would be good to consider the role of the guide vs the readme...

I have seen some repos that only have info about the repo & contribution in the readme and have all documentation in a separate guide. I quite like this and I think it helps to make it clear where information should go to prevent crossover (as we have with the Parse Server guide). What do you guys think?

Can we use this opportunity to try out a new doc cms? I think there are several shortcomings in the current CMS.

Happy to try out a different cms but I doubt it will be an easy decision to move to a new system so I'm not sure what the value is to tie that into this?