Are you tired of having to constantly update your CV, social media profiles, and other online platforms with your latest links and information? With links.dev, you can simplify your online presence and make it easier for potential employers, clients, and followers to find and access all your important links in one place.
You can find a video tutorial here
To register for links.dev, you need to do two things:
page.json
, which contains the content of your page.custom.css
, which allows you to customize the look of your page.That's it! Once you have created your "my-links" repository and opened your pull request, wait for it to be reviewed and approved. Once it is merged to the master branch, your page will be visible at: https://links.dev/username
:information_source: If you've already joined links.dev and want to contribute, take a look at the Contributing section.
page.json
sectionsTo display your website, your page.json
must have at least these sections:
name
)description
)image_url
)links
)The minimal version page.json
file may look like this:
{
"name": "Your name",
"description": "Your description",
"image_url": "url_to_your_image",
"links": [
{
"title": "Link title",
"url": "link_url"
}
]
}
restricted-usernames.yaml
file.Found an issue, want to suggest an improvement or request a new feature? Contributions are always welcome to the project
Get started opening a new Issue or Pull Request!
If you like this project and want to support it, you can do so by starring this repo and buying a coffee. The money will be used for domain registry fees, server costs, and monitoring tools costs. Any support is highly appreciated. Thank you!
You should invalidate the registry cache. Normally, it should be done automatically on the CI but sometimes, GitHub's own cache is not invalidated when links.dev's registry cache is invalidated. Click this link to invalidate registry cache. https://links.dev/fatih/?refresh-registry=1
You need to clear the cache with hitting your page refresh=1 query param. Example: https://links.dev/fatih?refresh=1 If you still don't see the update, it might be because you recently committed the changes to your repo. It takes a bit of time for GitHub to invalidate raw content caches. Try hitting your page with refresh=1 5 minutes later.
It depends. If you have a different theme than the default one, yes you can. Please keep in mind that, you have to have a known image hosting provider URL or Twitter, LinkedIn profile picture URL. Because its content is displayed on the home page, and it is susceptible to XSS. That's why I cannot accept your pull request if you are using a custom image URL.