Yeah, the translation bit definitely makes things tricky.
In our product, we have “fallback strings” that we can use while new strings get translated.
Let’s say I edit an old string. I can then define a fallback string, which tells the code to keep using the old string until the new string gets…
I heard from Andy that you take it the next level when it comes to working in the code. Major props for that! I still have a ways to go before I get to that point.
Everyone should also read your story about this:
I’m so sorry, but I don’t have a PDF version of this. Have you tried copying/pasting the content into an editor (like Microsoft Word, Google Docs, or Dropbox Paper) and then exporting as a PDF?
Or if you use Chrome, you might also be able to select “Print” and then choose “Save as PDF” instead of your printer. Does that work for you?
Thanks for checking it out!
Yeah, it’s funny how most flowcharts about the software development process make it seem like design always happens first and then implementation happens after that. But in reality, a good chunk of the design work happens partway though the implementation process.
Oh interesting… Thanks for that feedback! Just out of curiosity, why do you prefer to share your documentation as PDFs?
In many online documentation tools, like Google Docs, there’s usually a way to share the doc directly from the tool.