> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/iasul-nostru-romania/how-iasul-nostru-started.md). # How Iașul Nostru started Iașul Nostru was initiated in 2021 by Alex Enășescu, who previously worked as a journalist for PressOne. Enășescu had a particular interest in reporting on local issues during his tenure at PressOne. However, he also noticed a gap in the provision of local news that existing media outlets were unable to fill adequately. Inspired by the emerging trend of local newsletters in the United States, he had been contemplating the idea of establishing a new local medium in his hometown for some time. When the opportunity arose to apply for funding through the newsletter platform Substack, it didn’t take Enășescu long to put his plan into action. He submitted an application and was awarded $40,000 to launch a local newsletter on Substack. This initial funding served as the catalyst for the inception of Iașul Nostru. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.beabee.io/community-journalismus/english/pioneer-portraits/iasul-nostru-romania/how-iasul-nostru-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.