Our latest beta is out! (Web Publishing and Raycast Extension inside)

Hey Anytype Community! :wave:

Our latest beta version is ready, including one of our most awaited features: Web Publishing. You’ll finally be able to share your created pages and objects with a larger audience. Not only that, this beta also includes support for our Raycast Extension.

If you would like to try the newest beta, you can either switch to the Pre-release version of our app or you can download it here.

Web Publishing

This feature has been a long time in the making as rendering all Anytype blocks from scratch on our new publishing server was complex. We can’t wait for you to try the beta version and share any bugs with us so any major issues can be fixed before the public release.

Note: Not all blocks are currently supported by our renderer. Over the next few months we’ll be working on adding support for sets and collections (inline and full-page), featured relations and table of contents.

In the meantime, here’s what we’re already improving for the public release:

  • CSS fixes (paddings and styles)
  • Critical bug fixes (e.g. missing blocks)
  • Support for mobile layout

Our Builder and Co-creator members with an Any Name can publish on personalized domains. If you’d like to use your own domain, you can upgrade your membership in your vault settings in Anytype.

Raycast Extension

Anytype can now work with third-party apps for the first time. The Raycast Extension is our first implementation based on our Public API. You’ll need the beta version for it to work. You can install the Raycast Extension here.

As always, thank you for being part of our community.

P.S. We’ve also added experimental right-to-left language (RTL) support.

Thanks team for the hard work!! I know we all love seeing big updates like this.

Hi. Thanks for your efforts.

One of the pages shows an error when published.

panic: runtime error: invalid memory address or nil pointer dereference, stack: goroutine 214016 [running]: runtime/debug.Stack() /home/runner/go/pkg/mod/golang.org/[email protected]/src/runtime/debug/stack.go:26 +0x64 github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).Render.func1() /home/runner/go/pkg/mod/github.com/anyproto/[email protected]/renderer/renderer.go:230 +0x44 panic({0x1049000?, 0x209f1f0?}) /home/runner/go/pkg/mod/golang.org/[email protected]/src/runtime/panic.go:785 +0x124 github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).RenderBlock(0x40004ddcb0, 0x400061dc80) /home/runner/go/pkg/mod/github.com/anyproto/[email protected]/renderer/page.go:54 +0x5c github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).RenderLayout.LayoutTemplate.func1({{0x158a0c0?, 0x400080fda0?}, {0x156a720?, 0x4000b70bd0?}}) /home/runner/go/pkg/mod/github.com/anyproto/[email protected]/renderer/layout_templ.go:68 +0x51c github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).RenderLayout.LayoutTemplate.GeneratedTemplate.func2({0x158a0c0?, 0x400080fda0?}, {0x156a720?, 0x4000b70bd0?}) /home/runner/go/pkg/mod/github.com/a-h/[email protected]/runtime/runtime.go:19 +0x34 github.com/a-h/templ.ComponentFunc.Render(0x40004ddcb0?, {0x158a0c0?, 0x400080fda0?}, {0x156a720?, 0x4000b70bd0?}) /home/runner/go/pkg/mod/github.com/a-h/[email protected]/runtime.go:36 +0x44 github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).RenderPage.PageTemplate.func1({{0x1589fe0?, 0x210d160?}, {0x1568680?, 0x400038a380?}}) /home/runner/go/pkg/mod/github.com/anyproto/[email protected]/renderer/page_templ.go:176 +0xcfc github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).RenderPage.PageTemplate.GeneratedTemplate.func2({0x1589fe0?, 0x210d160?}, {0x1568680?, 0x400038a380?}) /home/runner/go/pkg/mod/github.com/a-h/[email protected]/runtime/runtime.go:19 +0x34 github.com/a-h/templ.ComponentFunc.Render(0x150?, {0x1589fe0?, 0x210d160?}, {0x1568680?, 0x400038a380?}) /home/runner/go/pkg/mod/github.com/a-h/[email protected]/runtime.go:36 +0x44 github.com/anyproto/anytype-publish-renderer/renderer.(*Renderer).Render(0x1158d40?, {0x1568680?, 0x400038a380?}) /home/runner/go/pkg/mod/github.com/anyproto/[email protected]/renderer/renderer.go:236 +0x78 github.com/anyproto/anytype-publish-server/gateway.(*gateway).renderPage(0x40004bb040, {0x158a0f8?, 0x4000a18230?}, {0x1572350, 0x400038a380}, {0x40005f8285?, 0x40003f0aa8?}, {0x40005f82b6?, 0x4000a06778?}, 0x0) /home/runner/work/anytype-publish-server/anytype-publish-server/gateway/gateway.go:132 +0x414 github.com/anyproto/anytype-publish-server/gateway.(*gateway).renderPageHandler(0x40004bb040, {0x1572350, 0x400038a380}, 0x4000370280) /home/runner/work/anytype-publish-server/anytype-publish-server/gateway/gateway.go:86 +0x194 net/http.HandlerFunc.ServeHTTP(0x400038a1c0?, {0x1572350?, 0x400038a380?}, 0x2a9964?) /home/runner/go/pkg/mod/golang.org/[email protected]/src/net/http/server.go:2220 +0x38 net/http.(*ServeMux).ServeHTTP(0x0?, {0x1572350, 0x400038a380}, 0x4000370280) /home/runner/go/pkg/mod/golang.org/[email protected]/src/net/http/server.go:2747 +0x1b4 net/http.serverHandler.ServeHTTP({0x4000675230?}, {0x1572350?, 0x400038a380?}, 0x6?) /home/runner/go/pkg/mod/golang.org/[email protected]/src/net/http/server.go:3210 +0xbc net/http.(*conn).serve(0x4000bc4120, {0x158a0c0, 0x40004cf4d0}) /home/runner/go/pkg/mod/golang.org/[email protected]/src/net/http/server.go:2092 +0x4fc created by net/http.(*Server).Serve in goroutine 105 /home/runner/go/pkg/mod/golang.org/[email protected]/src/net/http/server.go:3360 +0x3dc

hello! could you share the url of the page? here or in DM. Thanks!

On Raycast extension, along with all future extension and api, how do encryption and/or data sharing work with these services? Mainly concerning privacy, security and closed system. And this applies to web publishing as well, especially since Network setting per space had not been acknowledged yet.

It would be great if team can explain more, now or later before or with release. Until then I will stick with the current v.0.44.0. Thanks for all the works anyway. :pray:

thanks, I’m looking into!

No image at all, is it normal?

First try…

  • no image or other element, only texte?
  • please make shared pages more visible :
    – on the page itself
    – and have some by the list of shared objects

Congrats and thanks team for this awesome update !

Congratulations to all Anytype team!

Web publishing certainly brings Anytype to another level for many use cases

I’m very curious about the Public API. Can you share more details about it? I’ve tried the search, but didn’t find anything about the API spec, or how to get access to it to develop my own integrations for Anytype

Great update, thank you Anytype Team!
I definitely don’t miss the old navigation bar, and really appreciate the new positions for + and < !
I’m excited to see how web publishing will evolve in the near future.

At first I missed the bottom toolbar, but having search, back and graph view at the top is now easier to reach.

Brilliant idea to move the bottom toolbar, much cleaner interface for writing and viewing our assets.

Great job anytype team!

We plan on sharing all of this later on.

I tested the share to web feature all morning since it’s a core part of my workflow (and the main reason I’m still paying for Notion). Here are some thoughts and questions:

  • I would need to password protect a shared page; it’s a very important feature to reassure clients when sharing information.
  • A shared page object with linked pages inside will prompt the opening of the page objects in Anytype. Is this a bug, or are sub-pages part of unsupported objects?
  • Unless I missed it, I would like to be able to see all published pages in one place, ideally like the recently edited widget.
  • Ability to force dark mode for viewers.
  • Share to web button on mobile.

Thanks again for this awesome update.

Edit: Typos

all good request, please fill in proper Feature Request for each of them in the forum :wink:

  • Unless I missed it, I would like to be able to see all published pages in one place, ideally like the recently edited widget.

@Elias you can see all your published pages under Settings > Data Management > My Sites > Manage

Great, thank you @jannis ,I would have indeed never found it by myself there. :ok_hand:t2:

That’s good to know, but might be way more useful under a proper Published Widget :wink:

Please, can you share a list of what works and what doesn’t in the current version of web publishing?
Rather than opening up bugs when it’s just not implemented yet.

Yesterday, no image was displayed, today it’s fine.

Under the What’s new: