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

Nuke redundant pages from docs/migrate firmware docs to MrChromebox's site #178

Open
sadlerm4 opened this issue Jul 5, 2024 · 7 comments · May be fixed by #200
Open

Nuke redundant pages from docs/migrate firmware docs to MrChromebox's site #178

sadlerm4 opened this issue Jul 5, 2024 · 7 comments · May be fixed by #200

Comments

@sadlerm4
Copy link
Contributor

sadlerm4 commented Jul 5, 2024

In light of MrChromebox's updated site, it might be a good opportunity to discuss the future direction and content of the docs in order not to unnecessarily duplicate effort.

I suggest that #159 can become a PR on MrChromebox's website repo instead, and perhaps #138 can as well.

In theory, the entire firmware, unbricking and reverting sections can be removed.

@ninelore
Copy link
Member

ninelore commented Jul 6, 2024

I dont see any reason why the redundancy is a ossue

@ethanaobrien
Copy link
Member

I dont see any reason why the redundancy is a ossue

it makes it more difficult to keep up to date when the data is in 2 different places. Nothing is preventing the user from reading the other website either

@sadlerm4
Copy link
Contributor Author

sadlerm4 commented Jul 7, 2024

I dont see any reason why the redundancy is a ossue

No one's going to read it if they can just get the information from https://docs.mrchromebox.tech

The opportunity is also there to overhaul the layout of the supported devices table since it does not really need to include firmware-related support info. It's also debatable whether it needs to include Windows support info either, when once again people aren't reading it when they can just go to https://coolstar.org/chromebook/windows.html

I would not be surprised if the docs are practically only seen by people who want to install Linux at this point.

@CoolPenguin27
Copy link
Contributor

Yeah I agree that it would be better to move the firmware pages to MrChromebox's website since they are needed more on the firmware dedicated website.

@sadlerm4
Copy link
Contributor Author

Closing as this is not the direction that the project is considering, which is perfectly fine. Here's to making the docs the best that they can be, and I appreciate all of you for what you do.

@death7654
Copy link
Contributor

death7654 commented Jul 10, 2024

Why dont we do this? MrChromebox actively maintains the firmware page and we dont have to worry about adding new devices. Not to mention, the users can know the features or upgrades they may get by upgrading

@death7654 death7654 reopened this Jul 10, 2024
@MrChromebox
Copy link
Collaborator

Closing as this is not the direction that the project is considering, which is perfectly fine. Here's to making the docs the best that they can be, and I appreciate all of you for what you do.

I'm not aware of any discussion on here or on Discord which would lead you to believe this

@sadlerm4 sadlerm4 linked a pull request Jul 17, 2024 that will close this issue
14 tasks
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 a pull request may close this issue.

6 participants