The share extension only saves a link to a webpage. It should import the webpage's contents to Capacities to be able to process.

Apart from the standard PKM, I use Capacities to "bookmark" webpages for reference or future reading. Sometimes a simple weblink is sufficient, but oftentimes it is more useful to file the actual content of the webpages.

I have started to use Markdownr for this purpose, and Markdownr works brilliantly - I get clean MD of the pages stripped down of nav and irritating ads. The stripped-down content can then be copied into a new page in Capacities.

However, this is yet another app on the phone and an extra step in the workflow, so the request is for you to consider implementing a similar functionality natively in Capacities.

NB1: sharing out of Markdownr and into Capacities would be an option but 1) currently, it does not work quite as expected (long content gets cut-off and Capacities does not reliably create new pages when sharing out of Markdownr - I have raised 2 separate tickets for this) and 2) the workflow depends on an open source app which may or may not continue to be maintained.

NB2: something like what I am after might be possible directly with Capacities using a desktop extension, but extensions are not available in mobile Chrome - mobile being a primary use case for me (and lots of others, I presume).

I believe the web extension can be 100x more useful.

Consider letting us save a webpage immediately to an Object Type other than 'Weblink'. This will allow me to frictionlessly gather things from around the internet. Right now, the process is painful. I have to add a webpage as a Weblink (which I personally find unhelpful), then open the Capacities app, then convert the Weblink into a different Object Type, then deal with complicated mapping.

I propose an elegant solution. For an Object Type, allow us to add a property called ‘Primary URL’ or ‘Primary Weblink’. This will be a special property that will allow us to add a ‘primary’ URL for an object.

Now imagine this new workflow. I’m on the web and find an artist’s website that I want to save. I have an Object Type called ‘Person’ that I want to save it to. Since I added the ‘Primary Weblink’ property to Person, I can choose ‘Person’ under a dropdown (Weblink can still be the first default option in the dropdown). I add the tag ‘Artist’ and hit ‘Save to Capacities’. I can now close the tab and feel calm wash over me.

This new concept / workflow would be incredible.

And if you implement this, there are two natural ways to evolve it. First, you would want the user to be able to change the Title of the Object they are adding. In the artist website example, I imagine the Title would default to the webpage title or ‘title tag’, which in this case might be ‘Lesley Frenz - Acrylic Painter’. Perhaps I want to rename this Object to simply 'Lesley Frenz’ before I save to Capacities. Second, if it’s not too big of an engineering lift, you can add another special property to an Object Type called ‘Secondary Weblinks’ or ‘Supporting Weblinks’. Imagine I stumble upon one of Lesley Frenz’s exhibitions some weeks later. When I use the Capacities web extension, I can add this webpage to an individual Object, which I can find through search. I search, find, and select my ‘Lesley Frenz’ Object, hit 'Save to Capacities', and the URL becomes a Secondary Weblink. Once again, I can close the tab and feel the calm.

With deep respect, this feels more powerful and potent than your current vision and planned features for the web extension. Some users find your Weblink concept helpful, but I imagine the majority of users will fall in love with this newly proposed workflow.

Replicate the web clipper of Evernote. When I save a weblink to Capacities, it should:

Without this, just saving an article to Capacities is pretty time consuming because of course, I want the actual of the article/webpage saved in Capacities, not just a link to it.

I see you are working on a deep integration of Readwise into Capacities. Given how expensive Readwise is, I would ask you consider a much simpler option. Could you just update the Capacities Browser extension to include the web page content? Then when a new Weblink object is created, the website content would be added to the text area of the object. I do this manually by copying the page content and then pasting it in the newly created object, but having this done automatically would be a huge benefit, especially on my phone. Any change on you giving the browser extension a little more love? Thanks.

John

Capacities web extensionis very poor collecting information. We want an extension like raindrop.io which not only save webpages but also download and add images + highlight texts. Add text highliting option in the extension and this will sync to my objects.

Sales Pitch / Key Differentiator

Considering the dynamic nature of web pages, which often undergo frequent modifications and removals in a short period, Capacities goes beyond the conventional Web Clippers. It introduces a unique feature called WebLink 2.0, which automatically saves a copy of each linked page.

By doing so, Capacities surpasses the need for a Web Clipper altogether through automated processes. This establishes Capacities as an advanced Personal Knowledge Management (PKM) tool, outperforming Evernote and Notion.

Moreover, this renders specialized applications like GetPocket and Instapaper obsolete and ineffective since they become unnecessary, wasting time and effort.

—

Preparing for the Future with AI

By implementing AI-powered content discovery, the database would contain two levels of information: the data chosen by the user to capture and all the remaining content from the page. This advancement would empower AI to significantly enhance the user's intelligence by identifying connections that might have eluded their comprehension.

Waiting on a robust web clipper that will capture an entire web page as a weblink not just the URL as capacities does now.