What is the "correct" format for a contact page?

I use the tag contact for pages that are a single contact person or entity. I also use the alias feature for these pages as well. This has been great so far. But I wanted to start spicing things up a bit for some of the contacts and I noticed that on the home page of the Logseq website, it has a supposed screenshot of a “contact card” that, presumably, pops up when you hover over a name. How do I get that feature?

Specifically, what is the “correct” way I should write in a contact for Logseq to connect everything, including phone numbers, addresses, avatar, etc?

Sorry to bring the bad news, but the Logseq homepage is not fully in line with what’s in the app at this moment.

A large rewrite of the app is underway that makes what’s on the homepage easier to build. But a “contact” card will not be a default data type; you’ll have to set it up yourself using properties.

With a lot of effort you could build something like this in the current app, but I recommend waiting for Logseq DB that will makes this a lot easier.

Sorry for the false advertising, I’m also not happy what was brewed up on the homepage. But luckily we’re getting close to making what is on the homepage a reality for all.

1 Like

Thanks for the clarification.

I do look forward to the new DB version. I know y’all are working hard on it. The current version of the app is pretty dope, though, so give yourselves the time if you need it. I know there’s performance issues with the current version but they aren’t really that bad for 99% of use-cases so you probably don’t have to rush on the new DB version. Just be sure you feel good about it before release! Trust your instincts.

I’ll keep my current contact system then. It’s rudimentary but works very well and is something that has streamlined some things for me in my personal task management. It shows the power of Logseq as a “meta app” that allows me to shape into what I really need and is a big reason I don’t look to any other app anymore.

1 Like