On behalf of the nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz team, I want to give a big shout-out to nostr:npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4, who stepped in with his TailwindCSS expertise and spruced up the UI in #Alexandria for NIP-62 publications. You can see his work below.

I'm particularly grateful for his attention to detail on the light mode variants. I dare say Alexandria now has one of the most elegant light mode UIs in the Nostr space.

Take a look at these latest developments at next-alexandria.gitcitadel.eu, and let us know what you think!

Reply to this note

Please Login to reply.

Discussion

You can see some of the styles he's implemented, already, in my test publications. We're still designing some of the stylesheet, but you get the general direction he's headed.

https://next-alexandria.gitcitadel.eu/publication?d=document-test-by-stella-v-test-file#_footnotedef_2

https://next-alexandria.gitcitadel.eu/publication?d=lorem-ipsum-by-stella-v-1

It's been so nice, having someone make next-alexandria.gitcitadel.eu look prettier. Michael tried, but it's like trying to get a very good mechanic to design a Ferrari.

Looking really good and running smooth and snappy on Kiwi browser on Android.

Some odd UI overlap happening at the top of the page here, though:

Yup, we have work tickets on our backlog for fixing the table of contents. We'll get to it after we polish up the publications reading some more, particularly on the performance front.

In first two images, icons in bottom right of box look tiny and strain my eyes. Pls, enlarge them.

Love the citation box in the top of the last image.

Nice. Few more observations while logged out on ubuntu 22.04 chromium:

1) poor/near invisible contrast in legend box

2) amethyst FAQ box presents nearly entirely unreadable to human alphanumeric text

3) in certain context box open positions it is not immediately clear how to close the box/return to conspiracy web view

4) I don’t remember verifying this one - is there a way to create keys on the spot without having to use a bunker or extension? This step reduces friction by several orders of magnitude for new folks to immediately start testing.

Item 4 is already in our backlog—we plan to add anonymous publishing.

As to the others, we can create tickets for those.

Anonymous publication is great and a prerequisite for freedom of speech. Salutations for this.

My point with comment four (4) is that nsecbunker, extensions etc are an obstacle if yall want feedback from more folks.

Yep. We'll have our core relay set usable by default, and anonymous publishing, so that users don't need a preexisting keypair to read or write publications.

It's possible to read already without logging in, and it will quickly get better when we add search.

What is this icon supposed to do? Doesn’t appear to do anything, but disappear for a few seconds after clicking.

That's our placeholder for the table of contents.

Early versions of the app had a table of contents, but we've been slowly revamping how we handle publications, specifically to improve performance. When that's complete, we'll reintroduce the ToC.

💪

Noticed in the comments in links above you mention issue # e.g. 200. Are you tracking in multiple places?

We have a OneDev instance on which we host our repos and track tickets. Using it requires creating a login, so GitWorkshop is better as a public-facing tracking tool.

Yes, we list the OneDev issue in the Nostr issue and vice-versa. That way we have traceability. And, later, they'll be automatically linked.