originprotocol / origin-website Goto Github PK

It just dawned on me I did not check to see how Celery retries. I'll take a look this week unless someone beats me to the punch and verifies this works as expected (retries job up to a reasonable number of times before failing for good).

We should always have created_at and updated_at fields on our database tables. Not sure how we missed this.

Would be easy fix, especially after we have Flask-Migrate in place:
#59

Now that we know how to do it, let's make the team page pretty too

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/zh_Hant/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

Causes showing of "help with translation" flash, and language drop-down has no text

Need the site in other languages.

Lets use Flask-Babel

Looks ugly right now

We need a new partners page. Aure has the design. Micah has begun to build.

See initial conversation here: #78

@ryana is on this.

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/he/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/pt/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

We should add a "build on Origin" form to our website to generate inbound interest from developers/projects that should be building on top of the Origin platform. Form submissions should trigger an email to our biz dev guys & be logged in a database table.

The code for the presale form should be an excellent starting point.

Copy:

Teams all over the world are building on Origin's protocols, but we're looking for more amazing people to join our mission.

Whether you're an existing blockchain company or a traditional marketplace thinking about the blockchain, we'd love to hear from you! Fill out the form below and we'll get back to you shortly.

Fields:

Name (required)
Company name (required)
Email (required)
Website
Note

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/it/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/ja/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

Especially on large monitors

On mobile safari iOS on iPad mini

Looks like we're going to have more database stuff than we initially thought. We're going to need to set up database migrations to make it more manageable when we need to make changes to the database.

Flask-Migrate is probably the best way to go here. We just need someone to set it up.

https://flask-migrate.readthedocs.io/en/latest/

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/ko/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/fr/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/zh_Hans/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/ar/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

All form elements should have consistent styles, preferably matching Aure's designs.

Good for seo, and needed to user tools like http://browsershots.org/

Right now we have to manually construct URL's for any page that is lanuage aware. E.g.
https://www.originprotocol.com/ko/presale is generated here
https://github.com/OriginProtocol/company-website/blob/master/templates/navbar.html#L33
as

<a class="nav-link" href="{{'/%s/presale'% CURRENT_LANGUAGE}}">{{gettext("Presale")}}</a>

Much better to use endpoints and url_for().
https://stackoverflow.com/a/19262349/59913

This happens when the buttons wrap on screens < 356px and 768px-991px.

Right now we're converting from dict to array, so ordering is undefined.

Key line of code: https://github.com/OriginProtocol/company-website/blob/master/views/web_views.py#L155

try:
        available_languages = dict((l,Locale(l).get_language_name(l).capitalize()) for l in constants.LANGUAGES)

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/nl/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

Requested by Aure via Slack #design.

There was some code in css for reversing the background vector graphics when in rtl languages, I'm guessing it got dropped/broken along the weay.

The translated docs are huge and take forever to download. Let's run these through https://smallpdf.com/compress-pdf or a similar tool. Be sure to double check the Craigslist screenshot to make sure the quality isn't degraded too much.

The card deck should be animated as directed by Aure.

We're getting to the point where it would be very useful for us to have our Telegram activity logged in a database. We'd like to have a history of all the messages, who joined when & make it easy to chart the grow of the community over time.

Our Telegram channel is http://t.me/originprotocol

As always, add a comment here before you get started to avoid duplicating efforts.

We don't have a license for this repo also.

Tons of whitespace at the bottom of the page

From @caner: https://originprotocol.slack.com/archives/C8UNGUVCN/p1516954965000042

The website is down when you choose french language.

https://www.originprotocol.com/fr

Aure designed a really pretty dot pattern with colorful geometric shapes for the header of our website that we haven't had time to implement in CSS (or maybe JavaScript) yet.

You can see the intended design here:
http://zpl.io/broroOe

Low priority, but would be a great first pull request for someone who wants to get more involved. Make sure your solution works well on mobile.

We should add references to other languages available in our header, per advice here:
https://moz.com/community/q/best-practice-for-url-language-country#reply_318293

 ... in the <head> tag in the HTML:
<link rel=”alternate” hreflang=”en” href=”http://www.example.com/english/” />
<link rel=”alternate” hreflang=”de” href=”http://www.example.com/deutsch/"/>

For anybody wishing to contribute to the translations:

https://github.com/OriginProtocol/company-website/blob/master/translations/th/LC_MESSAGES/messages.po

You add the translated-versions under msgstr ""

Example:

msgid "Hello"
msgstr "Bonjour"

See the German translation as an example:

https://github.com/OriginProtocol/company-website/blob/master/translations/de/LC_MESSAGES/messages.po

User's language is currently stored in session variable, but would be better to have it as par to the url, e.g.

http://originprotocol.com/en/team

There are several possible solutions online.

Under team, Daniel Von Fange

Currently goes to
https://www.leancoders.com/

But looks like Daniel is at:
https://leancoder.com/

Users should not leave the Origin site by clicking on links.

We will soon have our product brief available in some (not all) other languages. We need a way to link to these.

Here's my initial idea.

If your language is set to English or a language we don't support yet, the product brief link directs to the English version.

If your language is set to one of the available localized versions, we swap out the product brief link for a drop-down that offers both the local language and the English version.

The product brief link in the footer should be a drop-down that lists all available languages.

The product brief button should link to the localized version or fallback to English

Related to #74. See #75.