Skip to content
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

[feature] add link (for e.g to documentation) #125

Open
trolologuy opened this issue Aug 31, 2020 · 7 comments · May be fixed by #798
Open

[feature] add link (for e.g to documentation) #125

trolologuy opened this issue Aug 31, 2020 · 7 comments · May be fixed by #798

Comments

@trolologuy
Copy link

It would be great to have the possibility to add an additional link per card.
Let's say you want to access a service but the documentation of said service is somewhere else.
So by the click on the icon, I would like to be redirected to that page.
This is especially helpful when not all the links / tools are straightforward to use and you share your dashboard with several users.

Here's how it could look like using font awesome's info circle:
example

@bastienwirtz
Copy link
Owner

Hey @trolologuy, sounds like a good idea, I add it to my todo list 👍

@taigrr
Copy link
Contributor

taigrr commented Oct 23, 2020

I'll see if I can take a look at this this weekend and put in a PR

@taigrr
Copy link
Contributor

taigrr commented Oct 26, 2020

@trolologuy enjoy :)

image
image

@trolologuy
Copy link
Author

@taigrr That looks awesome! Thanks a lot for the hard work !! Can't wait for that PR to be merged 😄

@rtzra
Copy link

rtzra commented May 19, 2021

@taigrr Can you resolve conflict in RP? 🙏

@taigrr
Copy link
Contributor

taigrr commented May 19, 2021

I'll take a look today

@taigrr
Copy link
Contributor

taigrr commented May 21, 2021

Looked into it. Got hit by a mountain of merge conflicts. I've never been a node guy, and I don't even have npm/yarn installed. I've been building and testing in docker at every small change.

I started stepping through them, but a lot of core stuff seems to have changed and these features would have to just be redone completely to fit in again.

If someone else wants to take this PR over, be my guest. I'm worried that by re-submitting my PRs after the merge I'll break a bunch of other features that weren't here before.

I may pick this up by creating a new PR later but I can't promise anything, for now I'll continue to just use my fork

@MD023 MD023 linked a pull request Jul 23, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants