Repository navigation
0.0.2 - Frontend is here, again
On the backend...
- Changed LLM output and DB to support new frontend approach
- Changed format of bullet point output to JSON
- Created a Supabase table for tagging
- Set up LLM to output tags and scores, in JSON, which push to that table. The tagging and scoring is absolutely awful, but that's expected, I just needed it to be in a consistent format - will make it good later
- Added 'productionready' bool for frontend to know when a row is ready to be used, set by completion of tagging
- Adjusted the logic of the Claude fallback summarizing llm script to fire not just if summarized is false, but also if any of the intro, bullet points or concluding paragraphs are empty to counteract the bug where llama just repeats tokens and doesn't give complete output
On the frontend...
- Completely removed Wordpress install, and setup next.js app instead
- Set up connection with Supabase, set up realtime fetching from there upon page render
- Built an article component (zero styling) to render our articles
- Shows 20 articles initially with pagination for more. Renders titles on a feed, titles are href to original article. Expand opens accordion which shows intro paragraph, bullet points formatted as such, and concluding paragraph. Users can close accordion
- Set up pages.tsx to render that component and nothing else so we can see
- Zero styling, but functionally it does what it is intended to do
- Added posthoq component (analytics) and added that to header of all pages
- Hosted site on Vercel, pointing jamiecostello.net to master branch, and staging.jamiecostello.net to staging branch
