added changed suggested by meaz in #610 issue ticket #5
meaz
Loading…
Reference in New Issue
No description provided.
Delete Branch "610"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -20,3 +20,3 @@As you can see you can decide to either save the exported public key to a file or "Copy" the key to your Clipboard. You can do either one, but if you don't plan on uploading your public key directly, it's better to export to a file.Exported public key can be then uploaded to Lacre.Exported public key can be then uploaded to Lacre Keyserver."Lacre Keyserver" should be a link to key server website (at least, that is what is done for other sections)
Indeed it is linking everywhere. It shouldn't.
I think there is an issue we need to decide what to do with it. Tutorials linking to lacre.io can cause issue where users who dont know what they're doing, will just follow the tutorial and upload their keys to lacre.io instead their instance (eg. disroot.org). Tutorials should not point anywhere therefore but at the same time be helpful and clear for users. I think there are two options:
Check if it's possible for the links/domain to be turn into variable so it's easy to adjust all the links per instance.
Tutorials should not have any links inside and be universal for any instance.
Solution 1. means every lacre instance needs to deploy their own howto grav site. But, texts will have all that advantage that except for the information also point to the right page.
Solution 2. Means that a lacre isntance only needs to point to the tutorials at learn.lacre.io and doesn't need to deploy grav site. But the will be no links so texts should be clear enough what to do.
What do you think @meaz @antilopa @pfm @fede @avg_joe ?
I would go for the second option and make sure to always use the same terms to describe a certain location (e.g. "key server portal"). On top of the tutorials we could list those needed variables and point the reader to make sure they have required url's of their instance. Those should be easy to find through the home page of each instance.
I agree. I would not put any variables on top unless I understood you wrong. Variables cannot be easily changed. Unless you mean explanation of what "Key server portal" is. What I should make sure is that on webgate (the frontend), link to howto in the menu opens it in new tab.
If we agree to this aproach, we should then write down all those decriptions (eg "key server" etc) and adjust all tutorials.
Yes, second option seems a better approach.
agree two on second option
is there any reason why this is not merged?