Dedicated Keyboard Download Page
Opened this issue · 18 comments
@dadepo I'll suggest we create a dedicated page for the keyboard, a page like YorubaName.com/Keyboard. It's easy to remember and to tell people. It will also be easy to access. Since we've released two keyboard versions so far, the page will also be a place to clearly label each download (without the blog posts), and let users decide which ones they want.
Having to search for the announcement blog post each time is tedious.
Subsequent release blogposts will just point back to this "Keyboard" page where we'd have put the new updates.
If you can provide the copy for the dedicate page, that would be good so that anyone who is interested in helping with this issue can easily pick it up and implement
@dadepo Okay.
Hi @hardcorekancil would you be able to help write a copy? I can take a final look at it when you're done. Then we can upload it here in wait.
Also, will you be able to create the American/British style keyboards we talked about for both Mac and PC? This is not a prerequisite to the above. It can just be a future update. (Of course if you can do it side-by-side so that we launch this page with the update, that would be fantastic).
Dedicated page for the keyboard layouts: awesome idea.
I can write something tomorrow (kind of a tight schedule today).
As for the US and UK differentiation, I should be able to attend to this at the weekend; then it would have to be tested.
Now thinking about it, I think we should make this a page on the blog and not include this in the codebase. (As information about the keyboard is somewhat absorbed from what the codebase)
With Wordpress we can create a static page and have the information there.
Another advantage is that, this way, we do not have to redeploy the whole application when we only need to edit the page about the keyboards.
I think the reason for this dedicated page is to be able to handily refer people to it rather than keep saying "go to the blog". We can just say go to Yorubaname.com/Keyboard, which is easier to remember.
It could be blog.yorubaname.com/keyboard
But I agree with Kọ́lá that having this static page on the website would
give it more visibility esp if it appears as a tab on the homepage for
instance.
2016-07-22 11:42 GMT+03:00 kolatubosun notifications@github.com:
I think the reason for this dedicated page is to be able to handily refer
people to it rather than keep saying "go to the blog". We can just say go
to Yorubaname.com/Keyboard, which is easier to remember.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARngpxPua8VD1047iSJtCd4lgWxRqhJXks5qYIJhgaJpZM4JQKAx
.
[image: --]
Marie-Laure Le Guen
[image: https://]about.me/marielaure.leguen
https://about.me/marielaure.leguen?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links
It could be blog.yorubaname.com/keyboard
Something like this is what I have in mind. It is a static page and does not have the long url's you have with posts.
...and on the website we can just have a link that links to this page (just as we have a link that links to the blog).
This way, we still have the visibility of having the link on the website, but we also have the flexibility of being able to edit the content from the blog without having to redeploy the application for the changes to be reflected.
Okay. This makes sense, as long as the link on the homepage is in a prominent place.
Yup, we would put it in a prominent place. It could even be part of the top level links we have at at the top of the website
That sounds like a very good solution @dadepo
FYI
for this to be done, the page on the blog needs to be added first. So basically this issue is waiting for that to be done.
Hi Dadepo,
I'm not sure what is required. Is this something I can do from the WP
dashboard?
On Aug 9, 2016 8:23 p.m., "dadepo" notifications@github.com wrote:
FYI
for this to be done, the page on the blog needs to be added first. So
basically this issue is waiting for that to be done.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARngp0JGoL9Pb9PC3-zo6j2rikeyUKFbks5qeLedgaJpZM4JQKAx
.
@hardcorekancil if you can catch @esteedqueen, she might be able to help with this. But yes, it has to be done via WP dashboard. What we want to do is to create a page, add the content about the keyboard to it. When this is done, then the dictionary can be updated with the link to the created page.
Ok I'll try to do it myself this week and if I can't find a way I'll call
on @esteedqueen
2016-08-09 21:48 GMT+03:00 dadepo notifications@github.com:
@hardcorekancil https://github.com/hardcorekancil if you can catch
@esteedqueen https://github.com/esteedqueen, she might be able to help
with this. But yes, it has to be done via WP dashboard. What we want to do
is to create a page, add the content about the keyboard to it. When this is
done, then the dictionary can be updated with the link to the created page.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARngpzpl3iVv25v6Zweh3RnvHWhXgNfaks5qeMtugaJpZM4JQKAx
.
[image: --]
Marie-Laure Le Guen
[image: https://]about.me/marielaure.leguen
https://about.me/marielaure.leguen?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links
Yup. It does help. I'll close the ticket once I add the link. Thanks
So, all we need for this issue to be gone is for a "Keyboard" link to be added on the homepage, after "blog" and before "contact us". cc: @netblaiz
cc: @rebirthtobi