clo issueshttps://gitlab.common-lisp.net/groups/clo/-/issues2021-07-23T02:37:21Zhttps://gitlab.common-lisp.net/clo/cl-site/-/issues/39Verify built-in webservers are working2021-07-23T02:37:21ZDave CooperVerify built-in webservers are workingThe site is set up to be built then served locally by several CL webservers. Some of them are stubbed out. Make sure at least the ones which are not stubbed out are working properly.The site is set up to be built then served locally by several CL webservers. Some of them are stubbed out. Make sure at least the ones which are not stubbed out are working properly.Dave CooperDave Cooperhttps://gitlab.common-lisp.net/clo/cl-site/-/issues/38Resurrect paste.lisp.org2019-03-06T07:58:40ZPhilipp MarekResurrect paste.lisp.orgCurrently no new pastes are allowed, for spam reasons.
How about having one (or more) of these authentication methods?
1. An existing gitlab cookie (paste.gitlab.common-lisp.net?)
1. An SSH account (so basically accepting new pastes ...Currently no new pastes are allowed, for spam reasons.
How about having one (or more) of these authentication methods?
1. An existing gitlab cookie (paste.gitlab.common-lisp.net?)
1. An SSH account (so basically accepting new pastes from localhost only, via SSH port forwarding and/or some CLI utility?)
1. 2FA as 1FA (no passwords, just user + time-based value) via existing gitlab secrets and/or a separate listhttps://gitlab.common-lisp.net/clo/cl-site/-/issues/37The CL logo is slightly off centre2019-02-13T20:54:02Z Hayley PattonThe CL logo is slightly off centreThe Common Lisp logo is positioned slightly lower than it should be to be centred in the white circle it resides in.
Both Safari and Firefox render the relevant part of the header as:
![Screen_Shot_2019-02-14_at_7.51.47_am](/uploads/d...The Common Lisp logo is positioned slightly lower than it should be to be centred in the white circle it resides in.
Both Safari and Firefox render the relevant part of the header as:
![Screen_Shot_2019-02-14_at_7.51.47_am](/uploads/d8bf21926e281ac044a0683655b22e90/Screen_Shot_2019-02-14_at_7.51.47_am.png)https://gitlab.common-lisp.net/clo/cl-site/-/issues/28FAQ index page generator2018-11-11T09:30:41ZAdministratorFAQ index page generatorCurrently, there is a `faq/index.html` page. This page contains a manually maintained index into the other `faq/*.*` files. This issue is about replacing the manually maintained index page with an aggregator which compiles the index (and...Currently, there is a `faq/index.html` page. This page contains a manually maintained index into the other `faq/*.*` files. This issue is about replacing the manually maintained index page with an aggregator which compiles the index (and summaries) into the current `faq/index.html` file.
I'm thinking that each of the FAQ files either holds a `summary` YAML element in the "metadata" section, or that we add "<summary>" tags (which will be hidden through CSS).December 2018https://gitlab.common-lisp.net/clo/cl-site/-/issues/33CODE tags (discovered by using backticks in Markdown) show their content in m...2018-11-09T11:23:27ZErik HuelsmannCODE tags (discovered by using backticks in Markdown) show their content in magenta (which doesn't fit our color scheme)There are actually 2 issues with backticks:
1. tripple backticks don't render as a preformatted block
2. backticks (as described above) render in the color magenta which doesn't fit a darkgrey+red color schemeThere are actually 2 issues with backticks:
1. tripple backticks don't render as a preformatted block
2. backticks (as described above) render in the color magenta which doesn't fit a darkgrey+red color schemehttps://gitlab.common-lisp.net/clo/cl-site/-/issues/13Add LispWorks and other implementations2018-11-04T17:10:38ZDave CooperAdd LispWorks and other implementationsAlthough Franz should retain sole status as "sponsored link" for now, other prominent implementations and vendors (notably LW and CLISP) should be added to the /downloads and/or /implementations pages.Although Franz should retain sole status as "sponsored link" for now, other prominent implementations and vendors (notably LW and CLISP) should be added to the /downloads and/or /implementations pages.October 2018https://gitlab.common-lisp.net/clo/cl-site/-/issues/31Review and link to the tutorial on our site2018-10-28T20:54:31ZErik HuelsmannReview and link to the tutorial on our siteThe tutorial in https://common-lisp.net/tutorial/1.html through [9.html](https://common-lisp.net/tutorial/1.html) isn't linked from our site.The tutorial in https://common-lisp.net/tutorial/1.html through [9.html](https://common-lisp.net/tutorial/1.html) isn't linked from our site.https://gitlab.common-lisp.net/clo/cl-site/-/issues/14Refine the styling/formatting2018-10-28T20:48:48ZDave CooperRefine the styling/formattingThe thick red menubar has received a certain amount of negative feedback at HN and reddit, e.g.
https://news.ycombinator.com/item?id=18195043
Would someone like to experiment with tweaking the layout_2018.css for perhaps a more welc...The thick red menubar has received a certain amount of negative feedback at HN and reddit, e.g.
https://news.ycombinator.com/item?id=18195043
Would someone like to experiment with tweaking the layout_2018.css for perhaps a more welcoming color scheme and thinner menu bar (and maybe bump the font sizes a bit -- see
https://news.ycombinator.com/item?id=18193073
)https://gitlab.common-lisp.net/clo/cl-site/-/issues/16Link news items from the news box to anchors on the news page2018-10-28T20:37:55ZErik HuelsmannLink news items from the news box to anchors on the news pageIt would be nice to have a `Read more...` link under each cut-off news item in the front-page's newsbox.
Or have the title be a link.It would be nice to have a `Read more...` link under each cut-off news item in the front-page's newsbox.
Or have the title be a link.December 2018https://gitlab.common-lisp.net/clo/cl-site/-/issues/17Links in lisp.reddit.com point to back to our site2018-10-28T20:37:55ZErik HuelsmannLinks in lisp.reddit.com point to back to our siteInstead of pointing to reddit's articles/discussions, the links point back to our own site.Instead of pointing to reddit's articles/discussions, the links point back to our own site.December 2018https://gitlab.common-lisp.net/clo/cl-site/-/issues/26Add more CL implementations to our pipeline2018-10-22T07:08:11ZDave CooperAdd more CL implementations to our pipelineShort of hosting a full-blown CL Continuous Integration setup, I think we should at least add a handful of CL implementations to our default build pipeline, to avoid nasty surprises like what happened earlier today, where something passe...Short of hosting a full-blown CL Continuous Integration setup, I think we should at least add a handful of CL implementations to our default build pipeline, to avoid nasty surprises like what happened earlier today, where something passes our default pipeline with the single implementation currently there, then proceeds to fail almost everywhere else. This does not give a nice feeling to anyone who might happen to clone our repo and try building the site locally. Even if they try it once just for fun, if such a thing is their first experience, then that may be the last time they even try.
Does anyone know if there a way we can leverage some other efforts for achieving this, such as [cl-travis](https://github.com/luismbo/cl-travis)? (I have to admit knowing next to nothing about Travis and CL-Travis so far...)https://gitlab.common-lisp.net/clo/cl-site/-/issues/12Change /lisp-companies from an unordered list2018-10-18T13:50:09ZErik HuelsmannChange /lisp-companies from an unordered listThe unordered list that's currently on `/lisp-companies` holds an entry for the company name and an entry for the company description. This is a confusing UX. Ideally, we replace the current setup with something that clearly shows the as...The unordered list that's currently on `/lisp-companies` holds an entry for the company name and an entry for the company description. This is a confusing UX. Ideally, we replace the current setup with something that clearly shows the association between company and description; making the enumeration of companies clearly stand out.https://gitlab.common-lisp.net/clo/cl-site/-/issues/4Adding a showcase of Lisp companies2018-10-14T16:54:55ZVincent DardelAdding a showcase of Lisp companiesSome people of the community is attempting to create a list of active companies using CL in production: https://github.com/azzamsa/awesome-lisp-companies
That may be an easier job for people behind this site, and anyway good propaganda ...Some people of the community is attempting to create a list of active companies using CL in production: https://github.com/azzamsa/awesome-lisp-companies
That may be an easier job for people behind this site, and anyway good propaganda information to add into it.https://gitlab.common-lisp.net/clo/cl-site/-/issues/19Discuss whether the JSCL playground should be included2018-10-12T20:22:47ZDave CooperDiscuss whether the JSCL playground should be includedThe next Reddit complaint/controversy is around the embedded JSCL repl:
https://www.reddit.com/r/lisp/comments/9n8650/a_new_version_of_commonlispnet_has_been_launched/e7mh4mz/
My opinion is that it can stay, but the caveat that "This...The next Reddit complaint/controversy is around the embedded JSCL repl:
https://www.reddit.com/r/lisp/comments/9n8650/a_new_version_of_commonlispnet_has_been_launched/e7mh4mz/
My opinion is that it can stay, but the caveat that "This is not a complete Common Lisp implementation" should be made a lot more conspicuous.
And we should be on the lookout for better options for online true CL playground environments as better alternatives.https://gitlab.common-lisp.net/clo/cl-site/-/issues/10Update hosting proposition to list GitLab as the preferred solution (and Trac...2018-10-12T18:31:52ZErik HuelsmannUpdate hosting proposition to list GitLab as the preferred solution (and Trac as a secondary)Also note that the mailing lists projects receive are no longer acurate.Also note that the mailing lists projects receive are no longer acurate.November 2018https://gitlab.common-lisp.net/clo/cl-site/-/issues/18Add an "about CLF" page2018-10-12T18:31:43ZDave CooperAdd an "about CLF" pageAdd a page within clnet summarizing the CLF, and point the cl-foundation.org at that page. Decommission the old cl-foundation.org site.Add a page within clnet summarizing the CLF, and point the cl-foundation.org at that page. Decommission the old cl-foundation.org site.November 2018Dave CooperDave Cooperhttps://gitlab.common-lisp.net/clo/cl-site/-/issues/11Create site/project user manual2018-10-06T15:02:36ZErik HuelsmannCreate site/project user manualWe want to help users get started on our site and provide prospective users with information on what it would take to get started on our site (as well as what they'd "get").We want to help users get started on our site and provide prospective users with information on what it would take to get started on our site (as well as what they'd "get").