-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manifest.json robots.txt #125
Manifest.json robots.txt #125
Conversation
freelancing-solutions
commented
Feb 15, 2021
- Added og:properties & twitter:cards
- Added manifest.json + icons
- Added service worker
- Added sitemap + robots.txt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also a zip file in the commit that seems to be a leftover. Please keep the changes focused on your actual goal :)
<meta content="width=device-width, initial-scale=1.0" name="viewport"> | ||
|
||
|
||
<meta content="Getting Started with Dogecoin is as easy as 1, 2, 3! It's simple, easy to set up, and free." name="description"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That change is not needed.
index.html
Outdated
@@ -13,11 +13,36 @@ | |||
--> | |||
|
|||
<!-- Meta --> | |||
<title>Dogecoin</title> | |||
<title>Dogecoin - #dogecoin - #doge</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can keep the webiste universal and don't need to add hashtags here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
<meta name="twitter:description" content="Dogecoin is an open source peer-to-peer digital currency, favored by Shiba Inus worldwide." /> | ||
<meta name="twitter:domain" content='https://dogecoin.com' /> | ||
<meta name="twitter:image" content="/imgs/doge-ogimage.png" /> | ||
<meta name="twitter:image:alt" contect="dogecoin.com Shiba Inu" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A lot of these twitter attributes are duplicated and as far as I'm aware Twitter will work fine with most of them in the og namespace. So these should be reduced to only the missing ones.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is not apparent to me and i am not sure of the route twitter will take however i find that twitter
does indeed performs better with its own tags...the og: properties works best with Facebook and other platforms
the way things changes this days i would advice to keep both
index.html
Outdated
<meta name="twitter:image" content="/imgs/doge-ogimage.png" /> | ||
<meta name="twitter:image:alt" contect="dogecoin.com Shiba Inu" /> | ||
<!--- favicon --> | ||
<link rel="shortcut icon" href="../imgs/avatar.png" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason for this using a relative path contrary to all the others?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its wrong my mistake..
fixed relative path
@@ -551,6 +578,13 @@ <h4 class="mobile-learn-padding" data-i18n="dgc-windows-wallet-modal-getting-sta | |||
); | |||
</script> | |||
<script src="/js/dogecoin.min.js"></script> | |||
<script> | |||
if('serviceWorker' in navigator) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reasoning behind a service worker? I'm not a webdev but for a simple static page it seems overkill?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i am with the thought pattern that i can and will support adding more futures on dogecoin , such as forums and a blog
i already have code from other projects in python but i can not commit all the changes at the same time
however for now it seems you are right let me remove or comment out the service worker.
Commented out until needed,
This was my rationale
I have created a proposal which if successfull would mean we can upgrade dogecoin.com to using modern frameworks example react.js
see here -> #126
if this proposal ends up with support from others , we would eventually need a service worker, in order to support the added functionality
{ | ||
var sParameterName = sURLVariables[i].split('='); | ||
if (sParameterName[0] == sParam) | ||
if (sParameterName[0] == sParam) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes in this file are note necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there was no changes , could have been an auto formated that line..
however its ok.
already implemented except there is a dire need for robots.txt as this site wont appear |