-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Docs] Document Aptos Name Service in Aptos.dev #6077
Labels
Comments
clay-aptos
added
bug
Something isn't working
documentation
Improvements or additions to documentation
labels
Jan 5, 2023
Closed
I am pinging Max and Charles to see when we can publish the FAQ prepared for the support team. |
This issue is stale because it has been open 45 days with no activity. Remove the |
Let's get these contents in navigation and announced. |
Here we go: All, please take a look. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Aptos Documentation Issue
Location
What are the existing URLs containing the issue, if any?
https://aptos.dev/concepts/aptos-concepts
https://aptos.dev/concepts/accounts
Where should this information land if new? (Start Aptos, Build Apps, Run Nodes, Reference, etc.)
Under our Concepts and Guides.
Description
How would you describe the issue?
We now offer the Aptos Name Service (ANS):
https://www.aptosnames.com/
Yet we don't formally document it on Aptos.dev and have just a sparse set of instructions on the site above.
What needs changing?
We need to publish docs on Aptos.dev that can be linked from aptosnames.com.
What changes are needed to support this new feature or product? (A simple overview, detailed procedures?)
We added references to ANS from our Accounts concept in:
#5877
And @banool is adding legitimate conceptual and FAQ information in:
https://github.com/aptos-labs/aptos-core/pull/5941/files
And there is also an internally developed FAQ to be used by moderators we should integrate when ready. Adding Daniel and
The text was updated successfully, but these errors were encountered: