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

Deprocate publicsuffix.org legacy website #2197

Open
dnsguru opened this issue Oct 4, 2024 · 3 comments
Open

Deprocate publicsuffix.org legacy website #2197

dnsguru opened this issue Oct 4, 2024 · 3 comments

Comments

@dnsguru
Copy link
Member

dnsguru commented Oct 4, 2024

Aside from preserving the CDN link for downloading the DAT file, the old publicsuffix.org website should be deprocated, having the domain name redirect to the wiki or the main page on the github repository.

@wdhdev
Copy link
Contributor

wdhdev commented Oct 4, 2024

I've been thinking of this for a while. I think it would be good, especially as most of the website's information is all on the wiki now.

Also, one thing I would like to point out is that we should use GitHub Pages for it as it is free and static, not requiring a backend or server.

We can simply create a repo called "publicsuffix.github.io", create an index.html file redirecting to wherever we need it to, and then publishing it to publicsuffix.org. We can then publish this repo (list) to GH Pages as well, that way the dat file is accessible in the same location as before, and is now automatically updated everytime a new commit is pushed. The GitHub Pages docs can help with this if needed, or I can.

@simon-friedberger
Copy link
Contributor

I think, maybe we should go the opposite direction and move the wiki to the website? That would make it easier for volunteers to create PRs for documentation fixes.

@wdhdev
Copy link
Contributor

wdhdev commented Oct 29, 2024

That could work too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants