-
Notifications
You must be signed in to change notification settings - Fork 6
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
All posts should link to the official repo (e.g. GitHub) and official homepage for the respective projects #36
Comments
Yeah, the help is highly appreciated! It will be good to:
https://github.com/quicklisp/quicklisp-projects can be used to find out official repositories. |
Ok, I'll see what I can do. |
I don't really want to dig deep in this project, as I'm on a tight deadline. I'm willing to produce a machine-readable file like this, with one line per project:
or:
(Is there something more useful I should use for the first field instead of the project name?) I'll let you or someone else build the required infrastructure for integrating repo and homepage links in the sidebar. |
It should be enough. But it is better to create a lisp function which will receive the system name and return an home page URL. I'll use it during the page rendering step. It can take repository information from the https://github.com/quicklisp/quicklisp-projects. And project's site through GitHub's API for projects hosted there. |
Here are partial results, unfortunately this is the only thing I can afford to do for this at this time.
|
Great! Do you have a script which collected this information? |
No, I just used the JS console to scoop up the project names from your index page into a file, then used emacs keyboard macros to add the source information from quicklisp-projects, then did some manual cleanup. Crude, disgusting means. ;P |
Then probably I'll try to automate it and build into my static site generator. This way I'll don't have to do the same task for future posts. |
Seems like basic functionality. Promoting projects without linking to them seems a bit incoherent...
For instance, the with-output-to-stream page should link to the official GitHub repo and the official homepage.
(Do you need help to find all the official repos and homepages?)
The text was updated successfully, but these errors were encountered: