Flockingbird @flockingbird@fosstodon.org

@0 In any case: Thanks a lot for the input. It confirms what I needed and gives some food for thought.

And just in case: we're building already. Nothing shippable or even usable yet: mostly PoCs/research and demos.

If you're curious: current PoC is to find out how AP will integrate in an eventsourced architecture (like Pleroma): https://github.com/Flockingbird/roost/

@0 An Open Source project should leverage the community. Some choices can be made better with imput from others.

But that advice is neither taken as dicate, nor asked on all choices.

E.g. when someone explains to me how to do SEO in 2020, I'll nod, take a note and go with my own choices made on that matter already ;).

And indeed! "getting stuff out" (shipping) is by far the most important. All questions asked are to ensure were shipping the right product and shipping as fast as possible.

@zens I've been using semantic-UI for some courses and love it so far. Thanks for confirming!

Don't know the other two, but'll give them a spin next week. Thanks for your time, also!

@zens I'm a big fan on DHH and his approaches.
Been doing Rails development since before 1.0 :).

Yet for flockingbird I'm using Sinatra: ActiveRecord is just too unfit for our event-sourced (reactive?) use of ActivityPub.

And indeed, JS would be "sprinkled on top of the HTML+CSS" to make it work just a tad smoother or dynamic. Vanilla JS or even jQuery is probably more than enough.

@zens I'm familiar with react, but don't particularly like it. I love redux, though. Also familiar with angular 1; onfortunately.

Haven't used svelte or vue. But all of those are, for this, I guess, overprovisioned. Maybe in some future when we can afford to hire dedicated frontend-devs it will fit.

But even then, serverside rendered HTML will remain of paramount importance; as outlined in previous toot about SEO.

@zens Our most important requirement is not visible: SEO. If privacy preferences allow, we want peoples' profiles to be indexed and ranked high.

That means serverside rendered HTML (with microformatting) is almost a hard requirement. Added benefit is that this makes the app fast, compatible and accessible.

This requirement is so important, that if forms and interactions are too complex to achieve with plain-ol'-HTML forms and a sprinke of JS, i'd prefer redesigning it, so it fits that need.

@zens The goal is to build our entire web-app, but that is far away; and I don't mind switching to something else along the route (react, native, wasm, some other CSS framework).

For now, the direct aim is to build a Proof of Concept and maybe even the MVP. Screens for the far-away goal are on figma: https://www.figma.com/file/CgDIaLgjwVLPzw1ggmrZzy/Flockingbird (work in progress!)