Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix docs page #932

Closed
mtrezza opened this issue Jun 11, 2023 · 6 comments · Fixed by #933
Closed

Fix docs page #932

mtrezza opened this issue Jun 11, 2023 · 6 comments · Fixed by #933

Comments

@mtrezza
Copy link
Member

mtrezza commented Jun 11, 2023

Issue

The docs page (https://docs.parseplatform.org) is an outdated version of the main page's section of docs (https://parseplatform.org). Both are maintained separately, which is difficult and causes one of them to be now outdated.

The outdated https://docs.parseplatform.org is visited more than the main page https://parseplatform.org, because for developers searching for docs online the https://docs.parseplatform.org has a higher ranking in search results.

Solution

De-duplicate both pages.

@mtrezza mtrezza added type:docs bounty:$10 Fix this issue and receive a bounty under the Parse Bounty Program. labels Jun 11, 2023
@mtrezza mtrezza pinned this issue Jun 11, 2023
@mtrezza mtrezza removed the bounty:$10 Fix this issue and receive a bounty under the Parse Bounty Program. label Jun 11, 2023
@mbfakourii
Copy link
Member

The problem is that both pages are in separate repositories!

@mtrezza
Copy link
Member Author

mtrezza commented Jun 11, 2023

Right, any idea how to solve this? If not, I suggest we remove the docs links from the front page (to make it more compact) and move everything to the docs page.

@mbfakourii
Copy link
Member

There are two suggestions
1=Transfer this repository to the doc repository or vice versa.
2=Remove the docs section from the main page's and the link to docs.parseplatform.org

My suggestion is the second option

@mtrezza
Copy link
Member Author

mtrezza commented Jun 11, 2023

I also think the 2nd option makes more sense.

@dblythy dblythy closed this as completed Jun 24, 2023
@dblythy
Copy link
Member

dblythy commented Jun 24, 2023

It has been completed by #933

@mtrezza
Copy link
Member Author

mtrezza commented Jun 24, 2023

We should add a PR template to this repo so PRs are liked to the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants