Bastien <b...@gnu.org> writes:
> this is more like: the main website should contain as little as > possible while worg, being collaborative, should contain as much > as possible. Ok. I'll keep this in mind in future efforts. Sounds like the current tools page should be shifted over, I'll try to do this in the future. > I think for handling tiles and other fancy display layouts, it is > safer to use a minimal css framework. I like https://bulma.io a lot, > but as long as it is CSS-only, it's good. Thanks to the CSS grid / flexbox, this is actually pretty trivial now :) The most annoying thing is getting Org's export to wrap the div in a link. At the moment it's quite hacky - it relies on browsers correcting malformed XML and I'd desperately like to fix this but I'm not sure how. Example: #+begin_src html <div id="outline-container-python" class="outline-3"> <h3 id="python">Python</h3> <div class="outline-text-3" id="text-python"> <p> <a href="https://github.com/karlicoss/orgparse"> <img src="https://cdn.iconscout.com/icon/free/png-256/python-14-569257.png" alt="python-14-569257.png"> </p> # malformed here <p> <i>orgparse</i> creates a tree from an org file. </a> # malformed here </p> </div> </div> #+end_src > Then once this is done, we can let worg display tiles for some pages. > > Is this something you would like to explore? I'll happily lay the groundwork in Worg's CSS. All the best, Timothy.