A few pieces of feedback for alexandria
Chrome Version 136.0.7103.113 (Official Build) (64-bit)
1. A CTA feels missing at the end of a chapter. Consider adding some CTA - maybe “Next Chapter”
2. Send button does not do anything while logged out. Consider using as a prompt to log in, or create keys.
3. Nice to see chapters as side nav. Clicking on chapters in side nav does not seem to do anything
4. Scientific paper authorship footnotes have an extra unneeded empty line
5. Poor contrast below image in image title. Dark mode
6. Make Equations Beautiful Again, please
7. Image is illegible. How might we allow for reader to 1) see, and/or 2) zoom in the image to see details
8. I created a test issue, but dont see it when I click on issues
9. While logged in publish arrow does not seem to publish / there is no feedback, nor error message
cc nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z
Yes, you are 💯 correct, on all points.
We don't yet have horizontal paging, so that's actually the end of the entire publication.
Mike is about to push a big ToC rewrite, so that should improve, soon. And then he tackles publishing and advanced parsing.
GitCitadel.com is being completely replaced. It's an old version of GitWorkshop and no longer compatible.
Yes making the ToC clickable is my top priority right now. That improvement is coming Soon™.
Making the publications one long scrollable document, rather than paginated, was an intentional design decision. A good CTA at the end of a publication might be links to related content. nostr:nprofile1qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qppamhxue69uhkumewwd68ytnrwgqs6amnwvaz7tmwdaejumr0dsq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvwwh27j what do you think?
The other notes are great feedback, and we'll add those to our backlog. Thanks!
Maybe I am not your target customer.
I prefer physical books, which have turnable pages, which sometimes turn to a new chapter.
Infinite scroll reminds me too much of social media apps, tiktok etc.
Chapters make longer reading more manageable, and to me, more rewarding.
Very bonus points: you could mimic a page turn, or new chapter animation.
Yes, similar readings, books people in your WOT read etc would be useful.
I don’t know that this belongs at the end of a book, or chapter, or where it belongs.
Discover books seems like a big enough thing for it’s own product page, or a stand alone product.
Well, we also display scientific papers and code and stuff. We're going to have a book view, as well, that will have a horizontal layout, but not in the MVP.
For science literature people also read / similar articles makes a great deal of sense
I'm definitely open to making the UI paginated! I want the experience to be more human than the average internet fare.
We denote different publication types via event tags. We could make books/novels show just a chapter at a time, while shorter publications show as a single page.
That would also make it easier to create shareable links, too. You could share a link to a chapter.
Nice!
Which customer are y’all serving?
That's an excellent question.
I think we have two main target groups in mind:
Business who want a collaborative, open-source wiki software. That will support things like code and product documentation, and can be used to power LLMs with useful, domain-specific context.
The other is consumers who want to read, write, and discuss blogs, papers, articles, and books.
We're building the core now, and as we add features we should be able to grow in both directions. Whether it will make sense to try to serve both groups at once is yet to be seen.
