Hippo
Hippo
Hello again! :) 1. As we discussed, I'm already working on the code snippet package right now. :) The copy & paste function will be a part of it, so...
Hey @kylebutts, thanks for chiming in on this again! I completely understand how this would work *technically*, my issue with this idea was from a *docs content* perspective: I did...
I'm not familiar with any of this, unfortunately. I never used the `NavDictionary`, `UIDictionary` or `public/captions` folder and have no idea how we could best check translation status/freshness for these....
I'm also not sure how we could best integrate those files into the translation status data structure, or into the visual presentation in the issue. The file name of the...
What do you think, @delucis ? Is tracking the dictionaries without special processing just like regular pages BTWWHB and good enough? If so, I can add them to the status...
> The only thing I'm not sure of is that I've often seen people only translate a few of the items in the nav for example. If we go with...
LGTM! Welcome to team docs! 🎉
I have seen it and I think it's a great idea! I have no time to work on this however, so if anyone else wants to give it a shot,...
> Good idea! Maybe something for the Styling & CSS page? Yes, either that, or on the Components page, where there even is a CSS Styles example: https://docs.astro.build/en/core-concepts/astro-components/#css-styles
> Love this, @hippotastic ! And just to clarify, if we were to include a file name at the top to show where the code sample exists, it could be...