Open laurencmendoza opened 1 year ago
While there were no specific code snippets for review these stretch goals / dev priorities seem to be on track for quick additions after graduations:
Since most of your goals focus on dynamic data injection into your style you might have some success creating dynamic textContent in a style block partial following the strategies employed here - css injection
Client side rendering is what React does - many react libraries exist that allow you to use JS to write css - Styled components is such a library - styled-components docs. We will be learning about React quite a bit during unit 3 - perhaps a refactor of your app to a MERN stack would be a nice ‘stretch’ / portfolio project for your team to work on after graduation.
If you would like to limit the number of OpenAI requests made from a particular site perhaps you can look into creating an API endpoint that throttles the number of requests made to your ‘api query’ endpoint. A simple example walkthrough can be found here -express-limiter library. Perhaps with a bit of careful study of the problem, you could apply your limiter at the route level, preventing certain routes from being accessed without impacting the performance of your whole site (browsing existing themes/categories).
We want to put the show page style injection (listed in Glow snippet) into a partial and pass in the different state depending on the page state.
We also want to expand the properties for our styleset Schema to include images that can be used in an application, maybe for a background.
Learning how to use client side render for applying styles to the theme (we are not 100% sure what this means yet)
Add more explicit instructions in the home page, or maybe an animation/gif so users can see what they need to do
Limit the number of OpenAI requests
In the future, export the styles into a css format for users to use for their application