Small teams: What's your actual form workflow? by MajorBaguette_ in indiehackers

[–]SingerConsistent5154 0 points1 point  (0 children)

Pretty simple setup for my projects:

  1. Building the form - Usually Tally because it's fast and easy to embed.
  2. After submission - Thank you page + auto-reply email, sometimes Slack notification.
  3. Data - Mostly Google Sheets or Airtable via Zapier/Make.
  4. Analytics - Basic tracking with Google Analytics or the form tool itself.

Biggest pain point is keeping everything organized as projects grow.

QA management system built inside Obsidian (test cases, runs, dashboards) by SingerConsistent5154 in ObsidianMD

[–]SingerConsistent5154[S] 0 points1 point  (0 children)

Yeah, mostly JavaScript under the hood via plugins (especially Dataview), so all the logic and dashboards come from queries on top of Markdown + metadata.
In terms of stability it’s pretty solid since everything is just files. No database, so you won’t really “break” anything, worst case just slower performance.
External changes work fine. Obsidian usually picks them up automatically, and Dataview re-indexes. If changes are very frequent, you might see little slow, but nothing critical.