litecoin-project / old-litecoin-org Goto Github PK

There is a problem on the website just before the download button, the text is missing on all language except english.

I did not found the text in the YML file in locales enven in english.

You can see it on the picture attached

• Credits - list each Litecoin project and thank contributors
• How to Contribute - including links to source repositories, contribution policies, etc.
• Disclaimers - explain the P2P nature of Litecoin, warn about the dangers of web wallets and how each user is responsible for the security of their own keys/wallets.

Any other pages we need?

https://github.com/litecoin-project/litecoin.org/blob/master/locales/en.yml

    select-lang: "<li><span class=\"selected-lang\">English</span></li>
                  <li><a href=\"/fr\">Français</a></li>
                  <li><a href=\"/es\">Español</a></li>
                  <li><a href=\"/pt\">Português</a></li>
                  <li><a href=\"/it\">Italiano</a></li>
                  <li><a href=\"/de\">Deutsch</a></li>
                  <li><a href=\"/nl\">Nederlands</a></li>
                  <li><a href=\"/el\">Ελληνικά</a></li>
                  <li><a href=\"/ru\">Русский</a></li>
                  <li><a href=\"/zh_CN\">中文</a></li>
                  <li><a href=\"/zh_TW\">繁體中文</a></li>
                  <li><a href=\"/ja\">日本語</a></li>"

When Transifex exports the translated *.yml files it reformats the multi-line into a single line. This is not a problem per-se as the imported YAML files work in middleman without any visible change to the end-user. Just generally it would be a good idea to move away from the use of multi-line strings.

It seems like this repository is deprecated in favor of https://github.com/litecoin-project/litecoin-dot-org. It would be nice to change the description field of the repository here on GitHub, which currently says simply

Litecoin.org Project website 

...to include a deprecation notice and a link to the current repo.

Such a change can only be done in the repository settings, by repository owners or organization members. A README with this information would be nice as well, and unlike the description field, can be contributed by anyone. I can send a PR adding one if there's interest.

At the Resources page, this important link is not found:
http://ltc.block-explorer.com/charts

Unaware users might think a blockchain with a non-functioning Block explorer is not a good one.

litecoin.org's introductory paragraphs are stale and will eventually become untrue. They need updating to reflect the current situation and also mention positives about Litecoin that are not currently mentioned.

• Litecoin's approach to discourage non-economically small transactions is one of the key improvements that makes is it different from Bitcoin.
• Litecoin has a track record of testing concepts quickly and helping to improve the upstream Bitcoin software.

What are the other benefits?

getting a 502 bad gateway error when clicking the download link to the android wallet on the main site, litecoin.org

https://twitter.com/litecoinproject
Our social media feed has useful content that would be very effective on the home page. This task is to create a way to automatically integrate the top news updates into the home page.

The simplest way to do this might be javascript to show the Twitter Favorites of @litecoinproject, however this might too easily fail for NoScript users. So perhaps we want the static site generator to handle this so it works for all visitors?

issuing commnad according to https://wiki.archlinux.org/index.php/Default_applications
$ update-desktop-database ~/.local/share/applications

gives following output
Could not parse file "/home/me/.local/share/applications/Litecoin wallet.desktop": Invalid key name: ;Path[$e]

As a result of a lot of images, a lot of HTTP requests exist to load the page.
Since we now also target mobile users (responsive design), we should minimize these requests to decrease page load times.
My sugguestions:

HTTP REQUESTS
Put all images in one or more CSS sprites to reduce HTTP requests.
Or, use DATA URIs.
Also, less important, combine the CSS files and put them at the bottom of the page.

IMAGES
The images themselves are quite large. They can be easily compressed by 50%, while maintaining the quality of the images.

CACHING
Images are not cached, nor other static sources such as the Javascript or CSS files.
Use page caching to cache these for (for example) 2 weeks. If a visitors visits the page again later, the page will not have to load these static sources any more.

eg. : instant-e