[Draft] Homepage refresh

[vakila]

Edit the homepage copy, and add additional content including:

• Links to research
• User logos
• Video embed
• Recent blog posts
• Community CTAs

All of this is very WIP, just intended to be a starting point for further iteration.

TODO:

• Live code sample
• ...?

Screenshot [light mode]

[vakila]

@alexjg 👋 Here's that first draft! Looking forward to hearing your thoughts, everything is still WIP but hopefully this is at least a starting point.

[ept]

Very nice! A few suggestions:

• could drop "connection-oriented" for simplicity
• I'm a bit uncomfortable with "conflicts are obsolete" since I don't think that's true – conflict cases still exist and we could do a better job of handling them. Rather than emphasising conflicts, maybe we should emphasise multi-device sync and/or multi-user collaboration
• All the platforms listed under "cross-platform" except for iOS are web platforms. Could we make it clearer that Automerge really is cross-platform?
• Adding a video is good, but that particular video is quite old. Can we make a new video, perhaps showing off some recent features such as rich text, spreadsheet, and tldraw integration? Or even include an interactive demo directly in the landing page?
• "Merge with the community" is nice :)

[vakila]

@ept Awesome feedback thank you! All great points, totally make sense.

• Video: Yes I forgot to mention that the video is a placeholder but was the best example I could find of a short & practical one, I think it would be a fabulous idea to make a new one.
• Interactive demo is also still on the to-add list, so I would love to know if you have a particular code sample in mind - otherwise I will see what I can come up with from digging through the docs.
• Cross-platform: Absolutely, what other platforms would be good to call out? Meanwhile I'll take a stab at phrasing it more generically to make that point better

I'll take a pass at editing the other copy as well per your comments, and try to get some revisions up this afternoon if I can, failing that early next week.

Thanks again, and if anyone else has feedback please keep it coming! cc @alexjg @pvh

[ept]

• re. interactive demo, maybe @alexjg's demo at the Berlin expo day could be a starting point? Athough perhaps it should focussed more on real-time collaboration than version control, since that's probably what more users will be looking for at the moment.
• Rather than platforms (OSes and browsers) perhaps we could focus on the languages for which we have good bindings? TypeScript (browser+node), Rust, Swift, Java/Android, C, [Python, Go – not sure how well maintained they are?]. If we do mention iOS, we should probably also mention Android for symmetry.

[vakila]

Still working on integrating the live code examples (the docusaurus webpack solution is proving a little difficult for WASM), but here is some updated copy in the meantime