Post History
Writing a full translation will approximately double the time you spend creating each post, so as other answers have said, you'll need to consider the cost versus benefit. However, thee's another ...
Answer
#3: Attribution notice added
Source: https://writers.stackexchange.com/a/44672 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
Writing a full translation will approximately double the time you spend creating each post, so as other answers have said, you'll need to consider the cost versus benefit. However, thee's another approach you could take: keep writing in your native language and provide a _summary_ in the other language. Writing a paragraph or two in your non-native language will be easier, and in that summary you can offer to answer questions or translate parts _if people ask_. Somebody who, for example, wants to know what you said about the third photo you posted can ask and you can answer, but you don't have to translate the detailed explanations of the other five pre-emptively. And if, over time, you're getting more engagement from English speakers and want to expand what you include in your summary, you can do that. You're using LiveJournal, which has the "lj-cut" tag that you can use for this purpose. Add your English text and put it behind a cut labelled "English summary"; those who want it can easily click through, and those who are reading in your native language won't have to skip past it. I would put this cut at the beginning, because people who don't read your native language might not scan to the end to see the link. (If, like many people, you've moved to Dreamwidth since asking this question, they have the same feature and, further, expanding or collapsing a cut can be done in place without a new page-load.)