I was referring to @Shampra’s feature request, as I thought that was what they were referring to, although I may have misunderstood them.
Since this thread is about table of contents - is there any perspective for implementation any time soon?
We do not have an ETA for this feature request at the moment.
Sorry @Filip but this response is pretty unsatisfying.
If your comment represents the Anytype team’s position on that basic feature request with 93 votes after a two year long thread with 43 posts, then that’s simply discouraging.
Especially because this feature that is requested here is absolutely nothing exotic, but basically essential for every article that exceeds the height of a window on the screen.
May I ask you, how do you actually work with Anytype within your team? Do you avoid longer articles altogether, or do you just take your time and scroll and scroll and scroll until you find the right place?
If you work internally with Anytype, what would you recommend as best practice for longer articles? Except for avoiding them in the first place?
Considering that it’s not even on the roadmap on github, it’s not going to happen any time soon.
I imagine that @Filip isn’t the one making the decisions at Anytype, not least because he’s the one who answers the community’s questions the most and knows what the majority of users want.
But you can be sure that the Anytype team is working hard to bring incredible new features that nobody asked for, such as chat, which has 0 votes in the feature request
Don’t forget that it’s 20 other requests that have (much) more votes (not to give my opinion 
).
And IA…
Yes, it is to be feared that these new “big” and “unavoidable” features will be implemented, which users have not asked for, and which will bring new bugs with them, while the old shortcomings (bugs and missing features on desktop and mobile) will have not even been fixed yet.
And if development continues at the current rate, it will probably be many years before Anytype leaves beta status.
Trust me, Anytype’s outline/table of content would come, but in 3 years time. Meanwhile I could have wrote a whole alternative application myself. I’m seriously considering this now.
Affine is almost perfect, just the bug is annoying. Copying and pasting destroys the formatting. Outline app is almost perfect but it’s too basic. Still Anytype is very close to perfect, but I can’t wait lol. Been a alpha user since its started and I think its about time I move on.
While we are spiraling away from the original topic (table of content) I do agree with the overal sentiment and I find it baffeling that high requested (and simple) feature requests have not been implemented after years!
The current roadmap doesn’t give me much trust that this will change. TOC is not even on there!
The 2025S2 is full of chat, multiplayer and membership “features” while the backlog is full of usefull and basic functionality that should have been added years ago, like Any toggle, tags as an object, OR filters in sets and collection/set UX improvements.
I don’t think it makes sense to compare Anytype with Affine. The differences are too big. But yes, Affine offers a well-functioning table of contents.
By the way, for me, the best implementation of a table of contents function has Lark.
Im also trying Capacities and Affine, but as you probably already know: Capacities doesnt have the properties concept implemented and Affine Pro doesnt even have the Types concept, Capacities app is great (with media player integrated) and Affine doesnt have an app yet. How do you work without those features? (if you already tried both apps)
I’m just discovering the codebase, but I’ve already added a prototype sidebar ToC. I don’t know about Anytype’s process for PRs, but I’ll try to get it approved.
EDIT: After I’ve done some work on the styles. 
Very nice!
The PR is up and about! 
That’s probably a bit outside my aim. ^^ I’ve done this in a day because I was surprised that it wasn’t in Anytype yet. But I likely cannot invest the time to do such an advanced feature. I will check if I can one day do something like this
We will discuss it internally, it definitely needs a product and design review but I was thinking something similar regarding this feature. Parts of your code would still be used for right panel page switching for example even if the functionality itself would be changed somehow.
Please don’t forget the modal window!
I’ve updated the pull request with your suggestions. There is only one question left about the old focus behaviour. Thank you again for taking the time to review my changes! 
How would I contact the product and design team? Or do I not do anything and just wait?