Continued Documentation site tasks that done and are no longer a big haul because of Nextra’s one click to deploy framework:
Page Legend/Internal Page Nav Bar
Syncing previous and next pages
Button to update docs
Links to GitHub issues or discussions where people can submit issues and things can be modified
Dates documents were last modified
Light Mode Dark Mode
Header / Footer
Side bar on Nextra site
Still working on:
Dain’s advice: use the current version of DAO utils to start the MDX writing.
Having issue with my project repo building to Vercel. Something about the Next JS on my computer.
Illustrating the DAO utils re-release with creative assets (see figjam)
“Built by PA” tag can be so prominent
Extra page general copywriting
Talked briefly about “a cover page” or “hero page” to the docs being a hybrid of a “development marketing funnel.”
Page thumbnails, descriptions, and favicon
Documentation conventions, Code conventions, and contribution guidelines
Action steps for the weekend:
Start writing markdown files documentation for the latest update on the DAO utils site itself, with continued maintenance of the package
Joey: “Based off of a decent look at the Figma I feel like we need 4 videos on DAO utils.”:
Intro to DAO Utils
Intro to components,
Intro to hooks,
Intro to custom theming…
Beginning the Story boarding process
“…within those like components sections, let’s say the auction modules, we can figure out exactly what combination of code snippets, gifs, screenshots, and diagrams that I can kind of help like make and I streamline so they are all within the same aesthetic for every single smaller subtopic”
and a preview or screen recording of what individual things within those smaller subsections.
The vibe is mental preparation notes for the docs. Less than 2 minute videos, formulaic.
Holding accountable: Putting some comments on the Figma, Initial for creative assets concept brainstorm.
I am not sure about custom themes to the site just yet, like for a different color schemes.
I’m not sure what we’re gonna call this domain or if the Dao-utils.public—assembly link on the PA Vercel will be transferred, because this necessarily public assembly docs anymore.
Had an extensive conversation with Salief ideating on what the final product for Flex DAO Interfaces could look like in the future. Then worked backwards to figure out the best ways we can start building structure that will support that vision,
Some messy notes on what lies ahead for the sprint on my end :
UI Designs for the Auction and Proposal components. Potentially multiple layouts for the Auction component if its within scope.
Develop a Figma Design Library that is 1:1 with the CSS Stylesheet for Flex DAO Interfaces
More globally, take this opp to create the beginning of the “PA Design System” that will be used in all future product builds. This is the heaviest lift to initialize, but will have the greatest benefit long-term.
Working on the front-end to style the template we create will allow me to conduct QA with mysef on the 1:1 match between CSS tags and the Figma nomenclatures matching.