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

Make haskell.org/alex redirect to haskell-alex.readthedocs.io ? #215

Closed
2 tasks done
andreasabel opened this issue Apr 5, 2022 · 6 comments
Closed
2 tasks done

Comments

@andreasabel
Copy link
Member

andreasabel commented Apr 5, 2022

I have updated https://haskell.org/alex (fixing #128), but I wonder whether we should simply make it a redirect to https://haskell-alex.readthedocs.io and maintain all information there?

  • @gbaz, can https://haskell.org/alex be simply made a redirect (and how)?
  • There is currently old stuff at webhost.haskell.org:alex that should be deleted:
    sftp> ls
    _darcs                    alex-2.1.0rc.tar.gz       dist                      doc                       
    index.html                index.html-darcs-backup0  
    
    After haskell.org/alex is out of date #128, only index.html is used, the rest is not connected (and badly outdated).
    [dist contains some old packings of alex-2, and doc the old rendered docbook manual.]
    I am going to delete all of this, unless some screams.
@tomjaguarpaw
Copy link
Member

The Haddock maintainers chose to host their documentation on readthedocs. If you want to do the same then @gbaz or another member of the haskell-infra team can set up a redirect for you.

On the other hand, you are welcome to just integrate the page into the www.haskell.org repo.

@andreasabel
Copy link
Member Author

On the other hand, you are welcome to just integrate the page into the www.haskell.org repo.

How would that work? Would it be a .markdown file under site/? Or where would I put the .html file (for the simplest solution)?

@tomjaguarpaw
Copy link
Member

Would it be a .markdown file under site/?

That would work, and I think you can also put the HTML contents into the .markdown file because Markdown should allow embedding of HTML.

@ghost
Copy link

ghost commented Apr 6, 2022

isn't Markdown problematic with colour use

Ericson2314 added a commit that referenced this issue Nov 14, 2022
The idea is that the docs should the source of truth, and be able to
replace the website (#215).

Information from the read-me is also moved to the docs.

The `CONTRIBUTING.rst` symlink is intended to do a thing on GitHub (see
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors),
but I am not sure how to confirm it will short of merging this PR.
@Ericson2314
Copy link
Collaborator

The docs are update, and we are ready to do this.

Ericson2314 added a commit to Ericson2314/www.haskell.org that referenced this issue Nov 27, 2022
(Plan from haskell/alex#215, for example.)

The old websites in addition to being in this repo's history are in
`old-www` branches in both projects' repos. That should be enough
redundancy.

That actual adding of the redirects is done out of band, so this just
removes the data and updates the read-me.
Ericson2314 added a commit to Ericson2314/www.haskell.org that referenced this issue Nov 27, 2022
(Plan from haskell/alex#215, for example.)

The old websites in addition to being in this repo's history are in
`old-www` branches in both projects' repos. That should be enough
redundancy.

That actual adding of the redirects is done out of band, so this does
the other steps.
Ericson2314 added a commit to Ericson2314/www.haskell.org that referenced this issue Nov 27, 2022
(Plan from haskell/alex#215, for example.)

The old websites in addition to being in this repo's history are in
`old-www` branches in both projects' repos. That should be enough
redundancy.

That actual adding of the redirects is done out of band, so this does
the other steps.
Ericson2314 added a commit to Ericson2314/www.haskell.org that referenced this issue Nov 27, 2022
(Plan from haskell/alex#215, for example.)

The old websites in addition to being in this repo's history are in
`old-www` branches in both projects' repos. That should be enough
redundancy.

That actual adding of the redirects is done out of band, so this does
the other steps.
TikhonJelvis pushed a commit to haskell-infra/www.haskell.org that referenced this issue Dec 8, 2022
(Plan from haskell/alex#215, for example.)

The old websites in addition to being in this repo's history are in
`old-www` branches in both projects' repos. That should be enough
redundancy.

That actual adding of the redirects is done out of band, so this does
the other steps.
@Ericson2314
Copy link
Collaborator

This is done!

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

3 participants