-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Streamline and align the "Getting Started" docs to fit in the new structure #869
Comments
Thanks @priscilawebdev! After a first quick look into the guidelines, I think we're mostly good but we'll review further next week. |
@bitsandfoxes, @markushi and @kahest: can you read the "Getting Started" section in the docs concerning the guidelines? We follow the model, but I am already used to this, so a fresh set of eyes is helpful. We updated that section, particularly with user input, once or twice over the last year. |
ping @bitsandfoxes, @markushi, @kahest |
I just double checked and compared it side-by-side with Android, looks good to me! |
That's react-native, which is not related to native :) |
damn yes...you are right! so I checked also "native" (only) and "QT" and the documentation looks good to me! 😉 sorry for the false alarm |
haha no worries 👍 |
![]() |
Problem Statement
Solution Brainstorm
The task goals are as follows:
Please refer to the "Frontendend Handbook" guide in our "Sentry" main repository for assistance in adding and updating the getting started docs: Frontendend Handbook.
Project: getsentry/team-sdks#23
The text was updated successfully, but these errors were encountered: