* new exersice after long time
now will be learning https://github.com/a-h/templ
it's a templating solution for go, more similar to jsx
but it also needs a pre-processing step, so i'm adding it like tailwind

with Makefile for make run/live
and will need to add as a step in project build

* setting up 
https://git.sunshine.industries/efim/golang-templ-and-tailwind
have separate repo, but i guess i'll remove .git from this dir,
to have single commits across Learning HTMX?

or maybe magit will just allow for simple integration?
just not pushing into origin, committing, and then committing from overall repository?

** not so simple, but still quite OK!

there's now 'subtree' which is separate concept from submodule,
and it is maybe simpler:

https://magit.vc/manual/magit/Subtree.html

i'm using the repo url
ssh://gitea@git.sunshine.industries:65433/efim/golang-templ-and-tailwind.git

and the command magit subtree add,
specify the directory, and it gets embedded it seems.
i have one level magit dispatch and my notes would be committed to the main repo,
i would potentially be able to pull in commits from the parent?

and maybe somehow contribute, but yeah, this is still confusing 🙂
how would i commit to subtree upstream if there are conflicting changes?
maybe i'll just get denied, as simple as that.

allright! let's add exercise specific data (again)

* so, starting dev

old process:
1. open second browser and open png with style
   first mobile
2. enable view C-S-m in firefox
   the responsive mode

i suppose next is adding colors to tailwind configuration?
from the styleguide file

also
3. check desktop style, whether any big rearrangements are required
   so that i'd start mobile with way to rearrange things

do i have a separate note with all of these things?
i've also used some commands to vertically center my stuff

** DONE allright, tailwind config go
font, size, colors

** well, i don't really want to go on.
but yeah, i'll need hierarchy of the elements.

** ok. thoughs:
the componets would be
- my balance bubble
  because it is spacially separate
- spending summary
- graph inside spending summary
  or maybe don't even need that

the component should take up all space provided to it.
if parent would want to add space around - that's easy to do,
but if component insists on adding space around itself - harder to reuse?
because then if parent would want to have child take up all space - negative padding?

*** allright, @ to include sub templates

