-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Migrate materials from ethdocs.org #5731
Comments
Amazing, thanks for taking the time to investigate this & put this proposal together! Overall I think this is a solid plan of action 🤩. In terms of your specific proposals...
What material on ethdocs are you referring to? I couldn't find much, except a few bits on these pages:
Overall I'm on board with expanding the info we offer on e.org. For context, we previously did list methods, which I'd be in favor of re-adding (context on that here: #3553). One advantage of listing methods directly on e.org is having them available in our site search. I believe the main reason we removed them was fear of maintenance but I don't think this will change all that much - it seems manageable for us to provide.
I'm on board with this in terms of expanding info we provide about storage options on https://ethereum.org/en/developers/docs/storage/#related-tools
I support this. We discussed doing something similar in #2919
I support this 👍
Interesting idea. Where might you see this page living? Perhaps we should consider a dedicated section for protocol developers. I like the idea but it feels fairly advanced & not relevant to a dapp dev.
I'm open to this idea but I'd rather incorporate this Q&As into the relevant pages/topics that we cover on the site rather than create a generic FAQ page that serves as a catch-all for these. Perhaps we could list out the FAQs you're thinking of bringing over & we could try to find a home for them within existing e.org content?
👍 - I think in addition to adding redirects at the DNS level on ethdocs.org, there'd be a few other final steps, including marking the ethdocs GH repo (https://github.com/ethereum/homestead-guide) as "archived" & updating that README to explain it covered the Homestead release & where to find updated documentation (e.g. currently it mentions https://github.com/ethereum/wiki/wiki which has already been archived). |
Looking at this a bit more in detail, there's a few recommendations I'd change. Connecting to clientshttps://ethdocs.org/en/latest/connecting-to-clients/index.html https://ethdocs.org/en/latest/connecting-to-clients/web3.js/index.html I think the other language-specific subpages you suggested make sense Contracts and transactionshttps://ethdocs.org/en/latest/contracts-and-transactions/developer-tools.html
Ethereum clientsAs you pointed out, many of these projects have been deprecated. I think we should:
|
Thanks for the pointers, @samajammin.
Yes, this is the information I'm referring to. The bulk of the json-rpc information to be migrated over to ethereum.org is actually on the wiki rather than ethdocs. However, I intend to cross reference the information on both sites to make sure nothing useful gets missed. One thing to note about the json-rpc information is that it might require another round of updates in the not too distant future - the merge readiness checklist shows "update execution-apis" as an as-yet incomplete task. We may also want to include RPC interfaces to consensus clients soon. (I'm considering this as out-of-scope for this issue, but something to remember later).
ok, this was the consensus from the team call too.
done
new "networking layer" page with subpages created under developer/docs. Definitely happy to discuss a more suitable home for it as you are right it is not so useful for dapp devs, but very important for protocol devs.
ok, makes sense.
ok, will come back to you to confirm arrangements for this later. The suggested redirects in the more recent comment have all been updated in the "suggestions" section of the original proposal and an additional PR added for expanding the deprecated software page on ethereum.org. |
updated table with specific redirects for each page, taking into account migration PRs |
Progress update: Redirect targets for every ethdocs page have been added to internal EF spreadsheet. Awaiting review for individual PRs before implementing redirects. Otherwise ready to go. |
This issue is stale because it has been open 45 days with no activity. |
This is complete! Content is migrated & redirects are in place. Thank you @jmcook1186 & others for all the hard work! |
Background
The homestead guide at ethdocs.org is now a historical archive. While it is full of interesting information it is now very out of date and users can easily be confused by contradictory information provided there compared to newer resources such as ethereum.org. Therefore, this issue is to suggest selective migration of material from ethdocs.org to ethereum.org such that the latter is becomes the go-to resource.
This has been discussed previously, e.g. on the ethdocs github here, but no action has yet been taken. Here, I have done a page-by-page audit of ethdocs.org and identified pages that can simply be deprecated using 301 redirects to the equivalent information on etheruem.org and which pages contain relevant material not currently included on ethereum.org that should be migrated across.
Note that there is crossover with another issue #5690 that suggests similar actions for the ethwiki. There, I suggested several new pages for ethereum.org that can also include material from ethdocs.org.
Below is a page-by-page audit for ethdocs with recommendations. Below are specific PRs that would address the suggested actions.
Proposed Actions
These are the suggested actions for migrating information and sunsetting obselete pages from ethdocs.org. Each task, if agreed by the ethereum.org team, can be a separate PR to ethereum.org (apart from 6) which will be a PR to ethdocs.org).
Expand the json-rpc sections on ethereum.org using updated versions of the material on ethdocs. Currently ethereum.org has a short very high level description and a link to the json-rpc spec, which is not super helpful as an on-ramp. UPDATE: Addressed by PR: Migrate json-rpc information from ethdocs/eth.wiki #5922
Build out the Ethereum history page on ethereum.org using details in ethdocs history page. UPDATE: Addressed by PR: migrate Ethereum history page from ethdocs.org #5935
Combine mining information from ethdocs with similar material from the wiki and use to bulk out /developers/docs/pow/mining page on ethereum.org UPDATE: addressed by PR: migrate info on pow-mining from ethdocs and eth.wiki #5897
Create new "networking layer" page on ethereum.org (as proposed in Migrate materials from eth.wiki #5690) and migrate materials from ethdocs and wiki. UPDATE: Addressed by PR: Add Networking Layer materials to /developers/docs #5838
Migrate updated answers to the still-relevant questions in the FAQs on ethdocs and eth.wiki to relevant locations on ethereum.org. UPDATE: now consider this nullified by previous PRs
Add deprecated projects from "ethereum-clients" section to ethereum.org/deprecated-software. UPDATE: Addressed by PR: Add deprecated software to "deprecated software" page #5971
After PRs 1-5, add 301 redirects to link ethdocs pages to their ethereum.org equivalents as per table above.
Also: The homestead guide github repository also includes an archive of even older material. Do we want to archive it somewhere?
Linked issues
The text was updated successfully, but these errors were encountered: