JakeVacovec

By popular demand, we released hard-coded text support as part of this announcement.

We support React, Angular, and Vue. We are working to improve the user experience for editing hard-coded so there is more context of where the text is in the code (and UI).

The environment is selected when a repo is connected but can be changed in your settings as well. Typically customers are making changes to the development environment. We treat content as a feature with a PR to the [development] environment for each content change.

*Branch-based changes are not yet supported but is in the roadmap.

Happy to have you on board. Don't hesitate to reach out jake[at]flycode.com

Lots of motivation in the air for the FlyCode team. Hoping to work with Airbyte's cloud product soon ;)

We actually created a PR last week to be added to Jamstack for use-cases like the process you detailed.

Auth only via our GitHub app, no database needed. We've tried to eliminate as many manual steps / additional development work to spin up. The team is here to help you set up for smb sites and your projects for work.

Btw - awesome to hear you're building a product in the same space. Happy to collaborate and exchange notes! jake[at]flycode.com

Thank you! You have been an incredible design partner and we're looking forward to growing with you :)

Async collaboration has become the norm so it is more important than ever to empower individual contributors to improve the product without dependencies on dev.

Distribution

- besides for supporting BitBucket and GitLab we plan to:

- Improve our editing experience by introducing more context from the UI

- Integrate with platforms like Linear and Jira

Great idea

- our main focus is creating value for our users.

- We believe that most of the great ideas come directly from the development community, which is why we are continuously collecting feedback and revalidating our assumptions.

Exactly! When we first started, our design partners helped us analyze their logs and it was amazing to see how many hours we could've and now will be saving them by automating this process.

Text is the ground-floor for us - if you have other use-cases you'd like us to productize that will create value for you please shoot me a note jake[at]flycode.com

Lokalize is a great product! Btw so is Notion...is has almost entirely replaced our usage of Google Docs/Sheets. But translation is a whole different beast, one that we plan to support via partner integrations similar to our level of integration with GitHub.

The main differentiator for us (going forward) is that we plan to support editing more than just text: images, configuration (like constants in the code), links, variables, etc.

The main difference between our current version and TSMs is FlyCode can edit texts inside the code whereas TSMs allow you edit texts in external files (JSON, PO) but not inside the code. Often times teams don’t want to lose the ability to search for texts inside the code just to support localization.

With FlyCode you can edit their texts in the primary language (e.g. English) inside the code and texts in other locales in a JSON file. FlyCode is editing texts inside Git allowing teams to run CI on the changes to the copy and make sure they're delivered safely to production, which reduces the integration cost and doesn’t introduce new points of failure. If FlyCode is down (worst-case scenario) you can still edit the texts inside Git just like any other part of the code.

Our goal is to make complex flows as simple as possible! Static website have amazing tools to support web developers and we believe the next wave will be for modern web apps. P.S. we love our designer :)

That's amazing to hear! The product is mature and stable end to end. We integrate via our GitHub app, which has been live in the marketplace since last year.

Solving problems > Tedious Work

OP here - thank you for the question! Yes, FlyCode will automatically scan the code, find the texts, and makes them editable in the FlyCode dashboard. When edits are submitted we create a Pull Request that updates the text in the code!

When editing texts in the code it identifies each instance of the text as a separate text for now, It currently lists the text with the file it found them for texts in the code and with key for texts from JSON.

We also helped some clients with performing an automated component mapping to add additional context.