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

[BUG] outdated documentation urls #1386

Open
master3395 opened this issue Dec 27, 2024 · 0 comments
Open

[BUG] outdated documentation urls #1386

master3395 opened this issue Dec 27, 2024 · 0 comments

Comments

@master3395
Copy link
Contributor

Hello,

Could we standardize the documentation links across the panel to ensure consistency and ease of maintenance? Currently, it seems the KnowledgeBase serves as the most up-to-date documentation, but multiple URLs are used across various pages, many of which are outdated or invalid.

Would it be feasible to centralize all documentation URLs into a single reference file? This approach would allow a single update to automatically propagate across all relevant pages, eliminating the need for manual edits on individual sub-pages. While I understand this would be a significant update, it would streamline future maintenance and greatly improve the user experience.

Here are the documentation links currently in use:

https://cyberpanel.net/KnowledgeBase/
http://go.cyberpanel.net/
https://docs.cyberpanel.net/doku.php
https://docs.cyberpanel.net/
In addition, several pages currently lack documentation links or contain broken ones:

Version Management
Design
Reseller Center
Create New ACL
API Access
Create WordPress
Create Docker App
Create Website
Create Package
Create a Database (e.g., phpMyAdmin documentation)
List FTP Accounts
Backup Website (Broken URL)
Create V2 Backup (Broken URL)
Manage Images
LiteSpeed Tuning
PHP Tuning
Package Manager (Needs better clarity on update consequences)
Install PHP Extensions / Manage Apache Extensions
Add/Delete Firewall Rules
Addressing this issue would significantly enhance the panel's usability and reflect a more professional approach to managing documentation.

Looking forward to your feedback and thoughts on implementing this change.

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

No branches or pull requests

1 participant