
<LogTimeMark>8am</LogTimeMark>
I intended to work.. 
and was frustrated on one of the first steps.
and took an excuse to slack at home again.

...

Now, though, I see an opportunity to code for a bit. 
____

<LogTimeMark>3pm</LogTimeMark>

planning to... do a coding working stream tonight.
that would be a big step for me. starting a posture.

Right now, just trying to get the NextJS blog to be happy with my slug structure.
____

for this...
- voice post (audio, spectrogen, article.. push to threadwise.. post to bsky)
- youtube video ? 

______

working alarm... 
template... 
mandala like article.. and structured sections.. aperaturation

thinking on preflight for the dev thicket... a space, a silence, 
a mindset.. a deliverable... seeking non frustration, but accepting and expecting frustration and disappointments




7-31-25


<LogTimeMark>9am</LogTimeMark>
I was frustrated with the slug pattern in NextJS - how we pull an article title into the sidebar.
With Next, components in the directory `/pages/` may also export a `getStaticProps` function which can pull dynamic data from the server and push it into the props of the page component.

In the end, all I'm saying is...
```typescript
export default function Home({ logSlugs }: Props) {
  // in here I have slugs
}

export async function getStaticProps() {
  const logs = await getAllLogs();
  const logSlugs = logs.map(l => l.slug);

  return {
    props: {
      logSlugs,
    },
  };
}
```

<Link href='nextjs.org/docs/pages/building-your-application/data-fetching/get-static-props'>Next docs - getStaticProps</Link>
<GitPush/>
____
<LogTimeMark>10am - 11:20am</LogTimeMark>

some reading in circles and early celebrations.
____
<LogTimeMark>11:30am</LogTimeMark>
solved an issue with my use of Next again. 

...HMTL hydration structure error, I had a container element in a Next \<Link/>

<LogTimeMark>11:30am</LogTimeMark>

{/* <RealEvent>
Charlie Kirk was shot and killed at a public event. Feels horrific. 
...
</RealEvent> */}

<LogTimeMark>12:20pm</LogTimeMark>


