Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

add GitHub link on pages #11

Open
spdegabrielle opened this issue Oct 29, 2023 · 6 comments
Open

add GitHub link on pages #11

spdegabrielle opened this issue Oct 29, 2023 · 6 comments

Comments

@spdegabrielle
Copy link
Contributor

Just a suggestion - can we add a GitHub link on pages at scheme.org that link back to the respective repositories ?

My experience in contributing was that https://github.com/schemeorg-community/monorepo/ is not obvious
this was made doubly confusing by the repo for the front page being on an entirely different organisation:
https://www.scheme.org & https://github.com/schemeorg

@arthurgleckler
Copy link
Contributor

That's a good idea. I welcome pull requests. Otherwise, I'll put it on my backlog.

@spdegabrielle
Copy link
Contributor Author

PR for community #12

@arthurgleckler
Copy link
Contributor

Thanks! Merged and pushed.

@lassik
Copy link
Contributor

lassik commented Nov 25, 2023

Such links have been a TODO of mine for a long time, but I've been putting it off because it would be nice to automate it. We don't have a standard way to programmatically insert HTML onto pages.

(Some of our HTML comes from S-XML via Scheme, and it's easy to add new machine-generated parts to it, but it's not clear what to do about the .html files. We could convert to .md or .adoc but that just passes the buck - how do we then generate information into those?)

@arthurgleckler
Copy link
Contributor

On another project, I've had luck using Pandoc to convert HTML into JSON, then reading the JSON, manipulating it, and converting back to HTML. We could use that technique to put footer elements even on static HTML pages.

@spdegabrielle
Copy link
Contributor Author

I understand the urge to automate - but I believe it creates a barrier to contribution.

If I edit html I know it is going to work, if I use an automation someone else has put together - even common ones - you add the responsibility for me to locally implement your implementation to test my change has worked before posting the PR.

You also run the risk I am naughty and don't test my PR - then the repo owners get the additional work that comes with untested PR's failing more often than ones that have been tested.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants