I haven't personally but there are some templates in the Marketplace. There have been a lot of requests about auth lately, I should really make a tutorial 🙂
Can you explain your exact use case so I can better tailor the tutorial?
Working with final projects delivered directly to the client.
As a freelance builder, no-code / low-code.
It is extremely common for clients to look for web apps with user authentication in projects of this type.
Business/service catalog
Private content/list directory
Newsletter
Companies wanting a personalized training area.
Menus for local businesses
My project is very close to this example:
https://www.freelancethings.co/https://filter-ui-16cfc7.webflow.ioEx: Supabase as database and authenticator - Webstúdio as logical UI/UX front end
Basically the possibility of creating projects that have a user system that is possible.
User X only views content Y Created/Edited/Updated/Deleted by this user.
User X only views content Y Created/Edited/Updated/Deleted by this user.
Just want to make sure I understand...
- You want roles you can create and assign permissions to like Role A can view Page 5?
- You want permissions based on the author of the content. Essentially if person A creates the content then they have full rein of their own content but no one elses?
How would item 2 work because Webstudio isn't a CMS.. that's more CMS logic the way I understand it.
Wized + Webflow + Supabase or Xano
or
Make + Webflow + Supababe or Xano
This type of no-code / low-code, which requires more than 3 different tool hires that do not involve fixed values.
The end customer chooses any other option that is just Back End <----> Front End.
Designers, builders and freelancers create their kits with 4,5,10 different tools.
But it's only beautiful in the world of builders, the client wants to distance themselves from all this cost, from all the dependence that will remain in the future.
I'm confident that Webstudio will do different in the future, it will think not only about the pyrotechnics that designers love to show to other designers.
But you'll also think about entrepreneurial freelancers who design directly for the client, clients who aren't worried about a shiny ferris wheel inside a .div.
@John Siciliano Webstudio has a clear path to success ahead of it, so please don't just be another option for designers.
Be the platform designed to design business.
Yes, considering that for it to do this, it needs to be a registered user of the base. And now you have access, with login and password.
Think about Bubble's logic flows for example. They are terrible at building, but the flow of logic can be created there, in a visual way.
If it were here, it would definitely be a killer, because webstudio is already among the best front end builder interfaces.
The best PageSpeed score I've seen to date.
The greatest UX fluidity I've ever experienced.
And also the only one that offered the option of hosting on external servers.
My client can stay at Webstudio for the rest of his life.
If Webstúdio becomes the best front end builder using visual logic to interact seamlessly with databases.
Easy as that!
2 Steps - 2 Tools
i agree with everything you said
I think there was a miscommunication. Can you explain what you mean by this
User X only views content Y Created/Edited/Updated/Deleted by this user.
And what you want Webstudio to do
Sorry for the euphoria, discovering Webstudio filled my head with possibilities.
I will explain:
Webstudio already integrates with Backends.
OK!
Now how do I create interaction logic with the content and my users in my tables in the Backend?
I need to get my user information from Supabase.
There you have it, Name, Images, Links, Addresses, everything about my user base.
How do I use webstudio natively, to create logic so that the user can create, edit and delete items in my backend?
Part of this is displaying CMS/database data. Simple enough... use whatever backend you want such as Supabase and use Webstudio Resources to fetch a specific row, all the rows, or whatever conditions you want to including dynamic ones (e.g. if a certain filter is active, get matching results).
Having users create data, I would add a Webhook Form which lets you send form submissions to a given Webhook
Letting users Edit or Delete data, seems like an operation that should happen on the backend itself. What's your use case for this? Not saying it's impossible or that you shouldn't do it, but to me that's a smell that the backend/CMS is the place that should occur
CMS is replaceable with database
btw this is something i have in the works right now. Data comes from baserow, can be filtered, users can submit the "report a mistake" form to request and edit, and another form to add a new platform which needs to be reviewed by us
Perfect! His response was this is what I need to continue. Thanks.
@Naldo gMoura i hear you brother, i would love the achieve the same thing. I currently have projects on webflow.com, ycode.com and softr.io for this, but would dearly love to move everything to Webstudio...Its not there yet as far as I can see or it requires a lot of hacking...I am sure @Webstudio Team is listening
Can you describe your use case?
I used Ycode for a while, I also used Bubble and recently I tested Weweb before Webstúdio.
After 5 years working as a freelance builder. I got to the point where I couldn't answer questions like.
Why do I need to pay for so many tools?
How will I manage all of this? Will I depend on you forever?
I don't care about complex animations or an award-winning designer if my sales increase.
@Naldo gMoura for clarity, do you agree that webstudio + backend should be 2 separate tools?
I have two use case:
1.Members website
User roles: Admin, Members-free, Member-Paid
Admins: can manage members and content, as well as page access rules
Members: Depending on type of membership, they can access specific content. Members can also submit content for moderation before it’s published on the site.
2.Portal
User roles: Admin, Employees, Public users
Admins: can manage members and content, as well as page access rules
Employees can login and manage content (CRUD)
Public Users: Can register and manage their profile, also view some content.
1 - this is basically a startup, e.g. nocodebackend
2 - same thing, maybe one backend can do all of it, maybe not, services like baserow/airtable can solve most of it I think, it's unimaginable to do both airtable and webstudio in one product
if we combine all of this in one product, both products will suck
might i remind you that webflow has paused dev on memberships and logic to focus their resources. Massive argument to rely on companies that dedicate their focus to one thing and enable ecosystem compatibility
https://wishlist.webflow.com/ideas/WEBFLOW-I-5385And that's a company with 500 devs
Yes! As said, there are already great CMS on the market.
Why not be the best front end integrator for backend integrations.
Webstúdio has a great variable system that will make it possible to build complete web apps using a flow of front end logic to interact with your backend integrations.
True! Webflow is focused on companies and marketing teams.
Webflow even decreased its focus on animations and pyrotechnics.
Marketing budgets of enterprises.
I want to share my recent experience, where my client made me go to hell, in one of the projects I have on Webflow.
Initially I sold it for a monthly fee of $167/month which jumped to $275.9/month
Until now...
CMS: Xano - $99
Logic: Wized - $29
Login: Memberstack - $99
Webflow - $39
Goat Slider - $9.90
So you wonder.
Serious? Also pay for a tool to have a decent slide?
We still have e-commerce not included, which I will certainly need to integrate with Shopify.
Wized $99 means they have 10k+ members, is it a saas?
Still seems to expensive, need to research that market as well better
Overall these prices don't say much. Could be super cheap if they bring the value
Membestack and xano have some overlap in functionality btw, so interesting to see reasoning which is used for what
What happened was the typical solution that creates a problem.
The default webflow slide did not meet the design.
Wized was just for logic, but when it reached 5,000 members, the Wized plan needed to be updated.
It's a SAAS and so is everything else, pages, blogs, members area.
If it were a SAAS where 100% of users pay, it wouldn't be expensive.
It has free lifetime access plans for upgrades whenever the user wishes.
Memberstack and Xano, it happened because at first only member stack served, but as the Webflow CMS talked about managing more than 10 thousand items.
Then Xano came.
It will increase if the article store is launched, the plan is to try to use another tool to integrate with an existing store on Shopify.
That's quite confusing, I am lost
to simplify, start off with auth capability on Webstudio that can integrate with Airtable or/and Supabase. ycode.com does it well. But the platform is slow (i think its built on laravel)
I don't think this is the solution. For starters if you want me to understand what is going on, I need laser sharp definition of what you use and why. If I understand correctly, you are in between migrating from one platform to another. You are not using them all because you need to, after that I can see what the ideal solution would be if we replace webflow with webstudio in this combination.
You may want to consider checking out
Smootify and
Shopyflow. I haven't used them yet, but they are supposed to integrate Shopify headless with Webflow!
Did you work at Webflow, and now contribute to Webstudio? I would love to hear that story.
