We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. Add a note about author rights of community shields.
Describe the solution you'd like Like it's done in angular logos (see note at header and footer). I think we could include it at the footer.
The text was updated successfully, but these errors were encountered:
I can pick this up!
Does the team just want it copied verbatim?
"All logos on this site are the property of their respective owners. Please clear any copyright issues with the owners before using the logos."
Not sure if we have a UI style doc anywhere, so any details on styling would also help.
Sorry, something went wrong.
Hey @juanri0s, thanks :-)
I think All logos on this site are the property of their respective owners. is enough.
All logos on this site are the property of their respective owners.
We haven't a styling guidelines by the moment... 😢
Design has changed recently and we haven't strictly a footer now... so, maybe we could put it above search 🤔
Or in FAQ, not to disrupt too the design, wdyt @NyaGarcia and @Caballerog?
This could be a question on the FAQ page, right now @NyaGarcia is working on this issue in this #63
@Caballerog @tonivj5 Did we decide where we want to place this item? If it is the FAQ page then I guess wait until that PR is merged in?
Yeah, I think we should wait until #59 is merged, then we'll decide where place the author rigths 👍
Thanks for your involvement @juanri0s :-)
No branches or pull requests
Is your feature request related to a problem? Please describe.
Add a note about author rights of community shields.
Describe the solution you'd like
Like it's done in angular logos (see note at header and footer). I think we could include it at the footer.
The text was updated successfully, but these errors were encountered: