Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-06.
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.
Vincent Dardel (@vdardel) on GitLab, 2018-10-11.
Hi, is it normal that it doesn't appear to be a link from the website to this page ? (is it an hidden page for now ?) Same for the list of libraries.
Vincent Dardel (@vdardel) on GitLab, 2018-10-11.
I can fix the sublist with a four spaces indentation in the markdown: https://gitlab.common-lisp.net/vdardel/cl-site/commit/049ce796f9f66855be6d581e14787069ba7fa158 (see https://github.com/jgm/pandoc/issues/2575)
but my generated html isn't as good as it should be, I messed up with the TOC in the sidebar, etc. I fear you manually edited the html.
Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-11.
@vdardel hmm. would it be an idea to - like the news page - to use markdown.cl to transform the markdown instead of using pandoc?
Vincent Dardel (@vdardel) on GitLab, 2018-10-14.
sounds better indeed.
(or at least with an uiop:run-program, as suggested in https://gitlab.common-lisp.net/vdardel/cl-site/commit/049ce796f9f66855be6d581e14787069ba7fa158#note_4071)
Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-14.
Hmm. But there it says that more steps are involved. Is that something you can contribute code for (either the markdown.cl transformation or the pandoc+followup-steps)?
Vincent Dardel (@vdardel) on GitLab, 2018-10-18.
(btw I'll keep an eye on your other markdown-related changes, but I don't promise anything for this)
Dave Cooper (@dcooper) on GitLab, 2026-10-01.
The site is no longer built by the old pandoc/generator pipeline. Every page is
now rendered by the clnet system, and /lisp-companies/ is drawn from the same
Markdown with the new stylesheet. The company/description association
discussed here is a styling question that the rewrite settled. Closing; if a
particular entry still renders badly, a new issue with a screenshot would be
welcome.
Sign in to comment.