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

refactor RA 'getting started' entries in TOC #301

Merged
merged 2 commits into from Mar 22, 2019
Merged

refactor RA 'getting started' entries in TOC #301

merged 2 commits into from Mar 22, 2019

Conversation

markwkidd
Copy link
Contributor

@markwkidd markwkidd commented Mar 21, 2019

This PR is submitted in the spirit of the PR #26: the "For Users" section should be orgainsed in order of something like a guide

The idea is that as a new RetroArch user moves down through the TOC they are seeing the most relevant information first.

@markwkidd
Copy link
Contributor Author

Screenshot 2019-03-21 11 11 31

@hizzlekizzle
Copy link
Contributor

that's essentially just moving the getting started guide around, correct? not deleting anything? It looked that way, i just wanted to make sure before merging.

@markwkidd
Copy link
Contributor Author

Correct, no content is deleted, things are just being moved around and in one case consolidated.

@thatman84
Copy link
Contributor

Great stuff, I think this will work out well moving forward.

Of course i have to make a suggestion lol !

I was just reviewing the pages and thinking about my next contribution.

IMO
Retroarch User Guides/ Directory Configuration should be promoted above
File Browser

File Browser docs references changing directories and the changing of directories is a 1st port of call on some platforms or at least should be.

I know RetroArch does a good job of default directories these days but feel it should be highlighted to new users as a fully updated base install will top 1gb easy.

@markwkidd
Copy link
Contributor Author

markwkidd commented Mar 21, 2019 via email

@inactive123
Copy link
Contributor

OK, I will await the changes before merging then.

@markwkidd
Copy link
Contributor Author

I have made the change, thanks!

@hizzlekizzle hizzlekizzle merged commit 19c998f into libretro:master Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants