-
Notifications
You must be signed in to change notification settings - Fork 0
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
Provide source of the website #1
Comments
@waldyrious polyformproject.org is on WordPress. Please feel free to open issues for any improvements you have in mind! |
That's what I assumed, from the polyform-wordpress-theme repo. For a static website, I'd say that GitHub pages is a better fit. (It would certainly easier to contribute to.) Anyway, I just wanted to suggest an improved styling for the table. Something like this: td { padding: 0.1em 0.2em; border: 1px solid LightGrey; }
table { border-collapse: collapse; } I would also suggest changing the cells in the first column from |
Would you like to make a PR to https://github.com/polyformproject/polyform-wordpress-theme? |
@kemitchell Sure. Would you mind first making the |
I agree and I could have sent a PR to fix this now. Not sure how to do it in a word-press-theme. @kemitchell, this issue should probably be transferred to (https://github.com/polyformproject/polyform-wordpress-theme). That will make it easier to find. |
I definitely floated GitHub pages early on. And a lot of people know their way around GitHub. But the decision at the time was that more of the folks liable to contribute, and who did in fact create the polyformproject.org you see now, would be self-sufficient on WordPress. |
It should be possible to submit improvements to the website itself. I'm not sure how it's hosted, but if using Github Pages is an option, then it could be either a separate repository, or a separate branch in this repo.
For reference, I was looking to propose a style change to improve the readability of "quick reference" table at https://polyformproject.org/licenses/.
The text was updated successfully, but these errors were encountered: