Skip to content
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

feat: Implement Onboarding Flow functionality #116

Closed
Tracked by #68
chadstewart opened this issue Jul 28, 2022 · 5 comments · Fixed by #369
Closed
Tracked by #68

feat: Implement Onboarding Flow functionality #116

chadstewart opened this issue Jul 28, 2022 · 5 comments · Fixed by #369

Comments

@chadstewart
Copy link
Contributor

For the Onboarding Flow issue described in issue #68, this issue is meant to be a follow up to issue #115. With the previous issue completed, the Onboarding Flow UI would be completed but there would be minimal functionality implemented mainly for testing the UI.

This issue is meant to implement the functionality so that it is working as described in issue #68.

@chadstewart chadstewart self-assigned this Jul 28, 2022
@chadstewart chadstewart changed the title feat: Implement Onboarding UI functionality feat: Implement Onboarding Flow functionality Aug 1, 2022
@chadstewart
Copy link
Contributor Author

@bdougie, looking back at this issue, I was wondering if we would be using the code for following repos as in the main open-sauced app? I'm not 100% sure how this would work.

@bdougie
Copy link
Member

bdougie commented Aug 1, 2022

At the moment, I have not thought of that. We could use the UI, but the logic. In order to do that we would need to do the following.

  1. Switch the app.opensauced.pizza to Supabase auth
  2. Connect the api.opensauced.pizza to store data instead of the github repo.

TBH, it would be easier to keep the logic in this app and move the features (saving repos) and viewing meta data to insights app and sunset app.opensauced.pizza.

@chadstewart
Copy link
Contributor Author

At the moment, I have not thought of that. We could use the UI, but the logic. In order to do that we would need to do the following.

  1. Switch the app.opensauced.pizza to Supabase auth
  2. Connect the api.opensauced.pizza to store data instead of the github repo.

TBH, it would be easier to keep the logic in this app and move the features (saving repos) and viewing meta data to insights app and sunset app.opensauced.pizza.

So I spoke to @0-vortex about it and came to the conclusion that we'd do the same thing we were going to do with PATs, which is just create a table and put the data there. Sounds like a good solution to me.

@github-actions
Copy link

🎉 This issue has been resolved in version 1.6.0-beta.13 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue Sep 16, 2022
## [1.6.0](v1.5.0...v1.6.0) (2022-09-16)

### 🧑‍💻 Code Refactoring

* created a new select component ([#346](#346)) ([37a836b](37a836b)), closes [#318](#318)

### 🐛 Bug Fixes

* Making adjustments to dashboard echart to more closely fit design ([#378](#378)) ([f9ebfaf](f9ebfaf))
* Replaced stately's logo with freeCodeCamp and replaced name ([#380](#380)) ([da45398](da45398)), closes [#376](#376)
* Resolve 'Show Bots', 'Show Outside Contributors' and repo table mobile responsiveness bug. ([#368](#368)) ([0beda90](0beda90))

### 🍕 Features

* Add contributors data from repo to validate designed components ([#314](#314)) ([cbccd8e](cbccd8e))
* add One week data on scatter chart(mobile devices) ([#381](#381)) ([04af186](04af186)), closes [#379](#379)
* Added the avatars to the dashboard and to the contributors page. ([#371](#371)) ([108152d](108152d))
* Adding social media preview to project. ([#353](#353)) ([e652ffc](e652ffc))
* create `<PaginationResult/>` component  ([#360](#360)) ([4bfb96d](4bfb96d)), closes [#325](#325)
* Create `<RepositoriesTable>` component ([#364](#364)) ([ef93890](ef93890)), closes [#321](#321) [#326](#326) [#327](#327)
* create `PaginationGotoPage` component  ([#357](#357)) ([f88fa98](f88fa98)), closes [#324](#324)
* Implement `<TableRepositoryName>` component ([#354](#354)) ([ede7f61](ede7f61))
* Implement footer component ([#347](#347)) ([349a6b8](349a6b8)), closes [#316](#316)
* Implement Loading Screen design ([#335](#335)) ([a3526dd](a3526dd))
* implement onboarding flow ([#369](#369)) ([ef3adee](ef3adee)), closes [#116](#116)
* Implement the `Pagination` component  ([#343](#343)) ([263f463](263f463)), closes [#323](#323)
* **build:** Install Nivo charts and implement `<Sparkline>` component ([#361](#361)) ([d37f0fb](d37f0fb))
@github-actions
Copy link

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

ElpisHelle added a commit to ElpisHelle/next.js-tailwindcss that referenced this issue Aug 17, 2023
## [1.6.0-beta.13](open-sauced/app@v1.6.0-beta.12...v1.6.0-beta.13) (2022-09-16)

### 🍕 Features

* implement onboarding flow ([#369](open-sauced/app#369)) ([ef3adee](open-sauced/app@ef3adee)), closes [#116](open-sauced/app#116)
ElpisHelle added a commit to ElpisHelle/next.js-tailwindcss that referenced this issue Aug 17, 2023
## [1.6.0](open-sauced/app@v1.5.0...v1.6.0) (2022-09-16)

### 🧑‍💻 Code Refactoring

* created a new select component ([#346](open-sauced/app#346)) ([37a836b](open-sauced/app@37a836b)), closes [#318](open-sauced/app#318)

### 🐛 Bug Fixes

* Making adjustments to dashboard echart to more closely fit design ([#378](open-sauced/app#378)) ([f9ebfaf](open-sauced/app@f9ebfaf))
* Replaced stately's logo with freeCodeCamp and replaced name ([#380](open-sauced/app#380)) ([da45398](open-sauced/app@da45398)), closes [#376](open-sauced/app#376)
* Resolve 'Show Bots', 'Show Outside Contributors' and repo table mobile responsiveness bug. ([#368](open-sauced/app#368)) ([0beda90](open-sauced/app@0beda90))

### 🍕 Features

* Add contributors data from repo to validate designed components ([#314](open-sauced/app#314)) ([cbccd8e](open-sauced/app@cbccd8e))
* add One week data on scatter chart(mobile devices) ([#381](open-sauced/app#381)) ([04af186](open-sauced/app@04af186)), closes [#379](open-sauced/app#379)
* Added the avatars to the dashboard and to the contributors page. ([#371](open-sauced/app#371)) ([108152d](open-sauced/app@108152d))
* Adding social media preview to project. ([#353](open-sauced/app#353)) ([e652ffc](open-sauced/app@e652ffc))
* create `<PaginationResult/>` component  ([#360](open-sauced/app#360)) ([4bfb96d](open-sauced/app@4bfb96d)), closes [#325](open-sauced/app#325)
* Create `<RepositoriesTable>` component ([#364](open-sauced/app#364)) ([ef93890](open-sauced/app@ef93890)), closes [#321](open-sauced/app#321) [#326](open-sauced/app#326) [#327](open-sauced/app#327)
* create `PaginationGotoPage` component  ([#357](open-sauced/app#357)) ([f88fa98](open-sauced/app@f88fa98)), closes [#324](open-sauced/app#324)
* Implement `<TableRepositoryName>` component ([#354](open-sauced/app#354)) ([ede7f61](open-sauced/app@ede7f61))
* Implement footer component ([#347](open-sauced/app#347)) ([349a6b8](open-sauced/app@349a6b8)), closes [#316](open-sauced/app#316)
* Implement Loading Screen design ([#335](open-sauced/app#335)) ([a3526dd](open-sauced/app@a3526dd))
* implement onboarding flow ([#369](open-sauced/app#369)) ([ef3adee](open-sauced/app@ef3adee)), closes [#116](open-sauced/app#116)
* Implement the `Pagination` component  ([#343](open-sauced/app#343)) ([263f463](open-sauced/app@263f463)), closes [#323](open-sauced/app#323)
* **build:** Install Nivo charts and implement `<Sparkline>` component ([#361](open-sauced/app#361)) ([d37f0fb](open-sauced/app@d37f0fb))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment