OriginProtocol/origin-website

Developer landing page

Closed this issue ยท 19 comments

As discussed, we should have a page for developers that gives more guidance than Github's default page.

Basics to include:

  • Link to platform repo and explanation of origin.js
  • Link to demo-dapp repo and explanation
  • Link to bridge-server repo and explanation
  • Link to docs
  • Info on weekly engineering calls
  • CTA on joining #engineering on discord
  • Emphasize everything is MIT open-source

Bonus

  • Digram showing relation of repos/components (updated, simplified, and cleaned up version of this one)
    image
  • Show time of engineering call in user's local timezone.
  • Link to iCal event for engineering call

This graphic from slide deck may be good starting point for how we show the repos:
image


@matthewliu - You said you could take a first stab at copy/content?

As per Aure's request on 5/14, I took a copywriting pass on both V1 and V2 of the developer landing page mocks in Zeplin. Please let me know if there is anything else you need.

Thanks, @davecraige ๐Ÿ˜… We are going to try to get to this tomorrow.

A first pass at this has been deployed to https://originprotocol-com-micah.herokuapp.com/en/developers. @davecraige, feel free to offer critiques. ๐Ÿ™

Branch living here ๐ŸŽ‹

Great. Nice work Micah ๐Ÿ™Œ

Great colors on the tags. :)

screen shot 2018-06-22 at 1 54 33 pm

Did you mean to say "#engineering channel." (And I believe it is spelled "engineering.")

screen shot 2018-06-22 at 1 59 08 pm

I believe you said "create create" here.

screen shot 2018-06-22 at 1 54 52 pm

You may want to capitalize "Discord" here.

Good eye, @davecraige. I'm doing too many things at once.

@davecraige it actually looks like some of that stuff broke in a recent commit. Let me take a look.

Ok, made those changes. You should be able to find them here: #220

Thanks, @davecraige. I've linkify'd the repo names also: https://originprotocol-com-micah.herokuapp.com/en/developers Anything else you recommend?

screen shot 2018-06-22 at 2 44 02 pm

One small little formatting issue. I believe the buttons get a bit borked on mobile tablets set at 960 x 600. (Might be super low priority as I see you are busy with lots of projects.)

screen shot 2018-06-22 at 3 11 43 pm

Also from a copywriting perspective, there is a bit of lack of unity between these two sections of copy. At the bottom in our footer we speak of "rent seeking middlemen" but the copy at the top says "trusted intermediaries." Seems as though the tone is lacking cohesion and it might be better to update the copy at the top to a similar tone.

Here is another pass at that top paragraph copy:

"Origin is empowering developers to build decentralized marketplaces on the blockchain, which will allow buyers and sellers to meet and transact without requiring any middlemen. Achieving this ambitious goal requires contributions from a growing community of developers. We would love for you to join us in this mission."

Happy to jump in and update that copy if you like that version.


screen shot 2018-06-22 at 4 25 10 pm

(Also something we could possibly keep an eye on in the future is maybe linking the developers to our mission statement page. We could possibly link where it says "radical inclusion and transparency" to more information in the future. An example of this is how Moz is very clear about TAGFEE on their culture page. )

screen shot 2018-06-22 at 3 34 23 pm

Also, any thoughts on having this say "Add to Google Calendar" for more specificity? (Many people I know use Apple calendar and may appreciate the clarity.)

I was excited to find this package which lets the user select from all calendar services, then remembered our website is in python/flask. :( Couldn't find anything similar in my quick searching.

I think google-only is kinda okay for now, but we should get at minimum generic ical-event (which apple uses) soon.

I've updated the calendar link to use a Google icon for context.

Summary of ideas for future versions:

  • shift to target DApp developers
  • a short video tutorial
  • a code playground
  • the time zone map for the engineering call (at the risk of it being incorrect as time brings change)
  • a more elaborate design
  • a diagram of how our codebases interact
  • calendar support beyond Google

First version done via #222 โœ