-
Notifications
You must be signed in to change notification settings - Fork 191
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
Organize README a bit better #33
Comments
Related issue: #18 |
Helloooo - so move API endpoints and expanded installation directions (getting started guide) from original README to new README file? How detailed do you want to get when it comes to installation directions, include actual code or more high level info? |
We added more details since I created this issue, and I feel like it's already at a pretty good state - what do you think? I think the API endpoints should be in a separate file, but everything else can stay in README. |
README looks good now with Custom Instructions too can update as time goes on - confused users can consult Discord for help. Stick API endpoints in new README in 'Pages' directory is what I would try. You can assign me here if all good. |
I'm not sure what you mean here exactly? |
You mentioned 'I think the API endpoints should be in a separate file, but everything else can stay in README' above so my point was to remove that section from README and create a new README within 'pages' directory of repo where api stuff is located. Maybe I'm confused here. |
No actually that makes sense! Appreciate the clarification |
Final decision to leave API endpoints in README, or move to another file in 'Pages' directory? Feel free to assign me if you want to move forward on this. |
I think moving it to the pages directory makes sense |
Move the API endpoints section into a separate file and add more details about how to get started with Kaguya - install it as a ChatGPT plugin and move all files you want ChatGPT to have access to, to the FILES directory.
The text was updated successfully, but these errors were encountered: