-
Notifications
You must be signed in to change notification settings - Fork 84
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
Website (haskell.org/happy) is out of date #195
Comments
Slackware 15.0 (default full install) includes the happy webpage itself is HTML 3.2 code temporary location of a 4.01 Transitional update the User Guide files list generator as DocBook XSL Stylesheets for Debian 11.1 the following might be indicated docbook-xsl_1.79.2+dfsg-1_all.deb the configure script also makes a check for the presence of for Slackware 15.0 after installing dblatex-0.3.10.tar.bz2 you may want to run |
I don't see why the number of additional dependencies in an unsaid Linux distribution should be an argument in this discussion. By extension, let's all switch from Haskell to C, because some Linux distribution has a C compiler by default, but no GHC. The friction introduced by an ancient XML-based format like docbook is unthinkable by today's standards. Please, convert to something human-readable and editable, also having a modern UI, like readthedocs. |
I tried conversion with
(This is now fixed in the |
Thanks for taking this on @andreasabel ! Let me know if I can help in any way. |
happy.xml dollar alex.xml
lsquo |
Upon typing
haskell happy
into search engine, first hit for me is haskell.org/happy, however the page doesn't seem to have been updated since 2010. This gives an impression that project stopped in 2010, which doesn't seem to be the case as I see here on github repo that there are new releases, latest one from 2020. Also, there is no link on the webpage that points to the github repo.While I understand that updating all information on the webpage might be a big task, would it be possible to at least update the "News" section with new releases, fix couple of broken links, and mention somewhere at the top that source is currently available on the github? If nothing else, at least we could put a note mentioning that the webpage is out of date and link to github repo.
I could make a PR, however I haven't seen code of the webpage being present in this repo. What is the method that could be used to propose a patch for the webpage? Thanks!
The text was updated successfully, but these errors were encountered: