This is an enhancement of the Links feature in WordPress, which has been disabled by default for a decade now. The database table for this still remains, though I’ve extended it with a separate metadata table, which uses the WordPress metadata API.
The fun of this project was trying to add all of the features to the Links feature that WordPress might have added if they’d continued the feature. So, all the enhancements made to comments, posts, etc. That means an improved interface(the admin list didn’t even have pagination), as well as a REST API endpoint, and more.
I’ve hooked it up to an Android app, which allows me to share URLs to it via the REST API and save them.
The original feature was designed as a blogroll…this is designed as a bookmark store. It has a built-in read later indicator, and various other pieces of metadata. I also added an import and export option just to cover myself.
For sharing with others, in the admin, there is an option to publish a single post as a bookmark post or multiple bookmarks in list form as a post.
There is a lot more I would like to do with it, but I’d love to see people using and suggesting input.
This is great if you find it useful BUT it seems a poor technical choice. The link functionality has been deprecated. Even WordPress core does not use the links table for links and it may be removed in the future.
Everything you built can (and probably should) have been developed using cpts. You would not have had to reinvent the wheel on caching etc and it would also be essentially future proof
If it ends up removed, I’d switch to a custom table, which would solve the 255 character limit on URL length, which I may consider in future anyway. I looked into CPTs, but I have 40,000 bookmarks in Pinboard. It would really insanely expand the Posts table to store a single string and its metadata.
This is useful.
My site is a newsy blog mainly about New Zealand telecommunications and technology. It’s part time, I can’t cover all the bases, but I’ve been looking for a way to point readers at relevant stories appearing elsewhere.
When I have some time I’ll look at integrating this, my only concern is how well it works with the theme I’m using: Autonomie. Will report back on how things work out.
It doesn’t have a front end display. It converts link lists into posts.
40,000 records is not a lot. Certainly no reason not to do things the WordPress way
A custom table would be even worse btw. For instance one might want to query all indieweb post types. Ideally they would all have their own custom post type and custom ui built. Using the posts table would enable them to all be queried easily, and would also enable easy filtering for from end display (and 10s of other features that come with using the standard api)
A custom table not do so much.
As I said I’m sure your solution is great for you but it seems a real pity you’ve taken an approach that means others would be silly to use it as anything other than a standalone tool.
When I post a bookmark to my site, it creates a fully searchable bookmark post. But I understand the other point of view.