-
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
[RFE] Create FAQ for common Q&A #5520
Comments
Adding @davidiw and @geekflyer as an FYI. |
Here is my plan of record:
|
Thanks to @banool , I am noting also the internal GDoc from @movekevin titled "Developer Problems (Discord/Telegram)" we should also consider. |
We have more fodder, now for app developers, in the form of a Studios Notes GDoc our engineers have compiled we should harvest for the FAQ and NFT tutorial improvements underway in: |
The team suggests we add these directly to Stack Overflow. |
I would love help! |
And now @davidiw says we should not use SO. Taking it up with the team to get an answer. |
I'd recommend Aptos.dev be the definitive site. Asking users to bounce between a site we maintain and a community forum is a bit jarring. |
Thanks, @davidiw . Please see the internal FAQ I highlighted in our weekly sync for a potential starting point. Would love your thoughts on that. |
I am working on an FAQ page under a new Contribute section amalgamating our internal FAQ and aforementioned partner doc: |
I am noting we met this week with the plan of record being some Q&A sessions to fuel this endeavor. Adding @gregnazario and @CapCap to keep me and @christian-aptos in the loop. Thanks! |
I am reopening as we pulled the FAQ from the Community section PR |
This issue is stale because it has been open 45 days with no activity. Remove the |
🐛 RFE
We at Aptos field numerous questions in Discord, Telegram, Slack and elsewhere. We need to form a persistent home for these answers to avoid repetition, inefficiency and fragmentation.
The goal is to get answers from those media in to the FAQ initially and then an even more permanent and findable home in the associated tech docs.
The text was updated successfully, but these errors were encountered: