-
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
Delete /enterprise/private-ethereum/ and the menu link to it #13640
Comments
Hi @tasdienes, can I work on this ? |
Certainly! No objections from me! Though I don't know if the site maintainers prefer to manage the menus directly? |
Alright. Let me get their attention. |
Hello @wackerow, can I quickly on work this ? |
This issue is stale because it has been open 30 days with no activity. |
Bump @wackerow |
@Signor1 sorry for our delay! let me know if you'd still up to work on this issue |
Yes, I can work on it. |
Hey @isabelladebrito, I just created a PR #14062 . You can check it out |
Fixed with #14062 |
Is your feature request related to a problem? Please describe.
In the early years, "Enterprise Ethereum" generally meant private chains. Since then the landscape has evolved, and private chains have mostly become irrelevant while the enterprise focus is now mainly on Mainnet and L2s.
Though I split up the public and private chain sections of ethereum.org/enterprise into separate pages about 5 years ago, I now believe it is time to retire the private chains related content entirely. I have given up on maintaining https://ethereum.org/en/enterprise/private-ethereum and it has become increasingly obsolete and irrelevant. I recently removed references to it from the /enterprise page.
Describe the solution you'd like
Please retire /enterprise/private-ethereum, and remove the menu item Build > Enterprise > Private Ethereum that links to it.
Build > Enterprise can link directly to /enterprise
I would have created a PR for this, but mucking with menus is a bit over my head :)
Describe alternatives you've considered
NA
Additional context
No response
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: