Moved the misc files to the correct folders, updated the content, improved formatting

Author: mrdavidorok

docs/ff-concepts/advanced/build_scalable_web_apps.md

@@ -0,0 +1,45 @@
+---
+keywords: ['build', 'application', 'pwa', 'scalable', 'flutterflow']
+slug: /concepts/advanced/build-scalable-web-apps
+title: Build Scalable Web Applications with FlutterFlow
+---
+
+# Build Scalable Web Applications with FlutterFlow
+
+FlutterFlow allows you to build high-performance, client-side web applications—including Progressive Web Apps (PWAs) and internal tools—with a focus on scalability and maintainability.
+
+:::info[Prerequisites]
+- A FlutterFlow account with a web-compatible project.
+- A basic understanding of responsive design and Flutter widgets.
+- (Optional) A hosting platform such as Firebase Hosting or Vercel for web deployment.
+:::
+
+**Platform Capabilities**
+
+    - **Client-side applications:** Build dashboards, PWAs, and internal or external apps.
+    - **Cross-platform deployment:** Publish to Android, iOS, Web, macOS, Windows, and Linux using Flutter.
+    - **Code export:** Download your full source code and continue development outside of FlutterFlow with no vendor lock-in.
+
+**Productivity and Reusability**
+
+    - **Low-code builder:** Accelerate development using drag-and-drop functionality—up to 10x faster than traditional methods.
+    - **Design System:** Create themes and reusable components once and use them across multiple projects.
+    - **Shared libraries:** Consolidate and reuse custom code, actions, and APIs across your organization’s projects.
+
+**Integration and Extensibility**
+
+    - **Third-party APIs:** Connect to any external service using REST APIs or custom code.
+    - **Custom components:** Build complex or reusable components in the design system and drag them into multiple screens or apps.
+
+**Pricing and Scalability**
+
+    - **Developer-based subscription:** Billing is based on the number of team members, not end users.
+    - **No usage-based charges:** FlutterFlow does not charge based on the number of users or sessions.
+    - **External backend costs:** If you're using services like **Firebase** or **Supabase**, charges will be based on their pricing models.
+
+:::info[Additional Resources]
+- **[FlutterFlow Documentation](/)**
+- **[Manual Firebase Connection Setup](/integrations/firebase/connect-to-firebase/#connect-an-existing-firebase-project-manually)**
+:::
+
+FlutterFlow provides a scalable, low-code platform for building web applications and PWAs. Its component-based design system, cross-platform support, and code export capabilities make it ideal for teams that need flexibility, speed, and full ownership over their codebase.

docs/marketplace/creators-hub/submission-criteria.md

@@ -1,5 +1,5 @@
 ---
-slug: submission-criteria
+slug: resources/projects/submission-criteria
 title: Submission Criteria
 description: Learn about marketplace item submission criteria.
 tags: [MarketPlace, Creators Hub]
@@ -22,7 +22,7 @@ Below, you'll find the criteria our Submission Review Team uses to review items
 - **What To Do:**
     - **If you're the sole creator:** Great! Make sure you're submitting the project from your own FlutterFlow account.
     - **If you're collaborating:** The project owner should be the one to submit it to Marketplace. Discuss this with your collaborators beforehand.
-    - **If you've acquired a project:** Ensure the original creator has officially [transferred ownership](../../resources/projects/how-to-collaborate-on-projects.md#transferring-project) rights to you. This may involve legal documentation, so it's important to handle it properly.
+    - **If you've acquired a project:** Ensure the original creator has officially [transferred ownership](/resources/projects/collaboration) rights to you. This may involve legal documentation, so it's important to handle it properly.
 
 #### 1.2 Significant Edits Made
 

docs/resources/projects/add_team_members.md

@@ -0,0 +1,102 @@
+---
+keywords: ['members', 'project', 'team']
+slug: /resources/projects/add-team-members
+title: Add Team Members to a Project
+---
+
+# Add Team Members to a Project
+
+FlutterFlow enables project collaboration through user invitations, organization-level access, real-time editing, and activity tracking. You can assign different roles and permissions to manage how collaborators interact with your project.
+
+:::info[Prerequisites]
+Ensure the invited user has a valid **FlutterFlow account** or an accessible email address to receive the invitation.
+:::
+
+## Invite Team Members to a Project
+
+Follow these steps to invite team members and assign roles:
+
+  1. **Open the Project**
+
+    Launch your FlutterFlow project.
+
+  2. **Navigate to Team Settings**
+
+    In the left sidebar, go to **Settings & Integrations > Project Setup > Team**.
+
+  3. **Invite a User**
+
+    Click **Invite User** and enter the email address of the person you want to add.
+
+  4. **Set Role and Send Invitation**
+
+    Choose a role (**Editor**, **Read-only**, or **Owner**) and click **Invite**.
+
+    ![](imgs/20250430121506784010.gif)
+
+    The user's status will show as **Pending** until they accept the invitation. If they’re not yet registered with FlutterFlow, they will receive an email invitation to create an account.
+
+  :::note
+  Each team member can only access features available under their individual FlutterFlow subscription.
+  :::
+
+## Assigning Roles and Permissions
+
+  When inviting collaborators, choose from the following roles:
+
+    - **Editor**: Can edit the project.
+    - **Read-only**: Can view the project but cannot make changes.
+    - **Owner**: Full access, including administrative control.
+
+  :::info
+  - The default role assigned is **Editor**.
+  - Read-only users cannot access shared team libraries like custom code or design systems.
+  - Read-only users added through *Teams* or *Organization* do not count against your team’s seat limit.
+  :::
+
+## Share Project with an Organization
+
+  You can share a project with all current and future team members in your organization by enabling the **Grant team members access** toggle in **Team Settings**.
+
+  ![](imgs/share-with-team.avif)
+
+  This ensures that every member of the organization can access the project without needing individual invitations.
+
+## Real-Time Collaboration
+
+  Real-Time Collaboration allows multiple builders to work on the same page, component, or design system at once. All changes are visible instantly to everyone on the same page.
+
+  ![](../../../static/img/real-time-collaboration.gif)
+
+  This increases productivity by allowing simultaneous contributions without overwriting each other's work.
+
+  :::info
+  Real-Time Collaboration is available only on **Teams** and **Enterprise** plans.
+  :::
+
+## Transfer Project Ownership
+
+  You can transfer ownership of a project to another user if needed.
+
+  :::danger
+  This action is irreversible. To regain ownership, the new owner must transfer it back to you manually.
+  :::
+
+  To transfer ownership:
+
+  1. Go to **Settings & Integrations > Project Setup > Collaboration > Project-Level Access**.
+  2. Click on the role of the current user.
+  3. Select **Owner** from the dropdown.
+
+  ![](imgs/transfer-ownership.avif)
+
+## View Project Activity
+
+  Project Activity provides a timeline of changes made by all collaborators. It helps track progress and audit modifications across the project.
+
+  ![](imgs/project-activity.avif)
+
+  :::info
+  - **Teams** users can view the past 7 days of activity.
+  - **Enterprise** users can access and download the full activity history.
+  :::

docs/resources/projects/how-to-collaborate-on-projects.md

@@ -0,0 +1,39 @@
+---
+keywords: ['community', 'join', 'account issue']
+slug: /resources/projects/join-flutterflow-community
+title: Join the FlutterFlow Community
+---
+
+# Join the FlutterFlow Community
+
+The FlutterFlow Community lives on a separate platform from your FlutterFlow editor account and requires a separate login. If you’re seeing errors like _"account not created"_ or _"password is wrong,"_ it’s likely because the community account hasn’t been set up yet.
+
+:::info[Prerequisites]
+You must be a registered FlutterFlow user to join the community.
+:::
+
+**Steps to Join the Community:**
+
+  1. From your **FlutterFlow Dashboard**, click on **Resources** in the left-hand menu.
+
+  2. Click **Join Community**.
+
+  3. Check your inbox for an email from `[email protected]`.
+
+  4. Open the email and click **Accept the Invitation**.
+
+  5. Complete the signup process by setting a password.
+
+  ![](imgs/20250430121510782041.png)
+
+  **Use the same email** associated with your FlutterFlow account to receive the invitation.  
+  You can verify your email on your **[FlutterFlow Account Settings](/settings/account)**.
+
+**Common Issues:**
+
+  - **Didn’t receive the invite?**  
+    Check your spam or promotions folder for an email from `[email protected]`.
+
+  - **Email mismatch?**  
+    If you used a different email to sign up for FlutterFlow, the invitation may not arrive. Confirm your registered email in your FlutterFlow account.
+

docs/resources/projects/imgs/20250430121506784010.gif

@@ -0,0 +1,40 @@
+---
+keywords: ['build', 'websites', 'apps']
+slug: deployment/build-web-apps
+title: Build Web Applications with FlutterFlow
+---
+
+# Build Web Applications with FlutterFlow
+
+FlutterFlow can generate code that runs as a web application. However, there are important limitations and platform-specific issues to keep in mind.
+
+:::info[Prerequisites]
+- A FlutterFlow project with web as a selected platform.
+- Familiarity with Flutter Web deployment using the Flutter CLI.
+- Access to a third-party hosting service (e.g., Firebase Hosting, Vercel).
+:::
+
+**Web Support Status**
+
+    :::note
+    Flutter Web is not officially supported in FlutterFlow. However, the generated code can still be compiled and run as a web app using Flutter tools.
+    :::
+
+    While the platform can generate code suitable for web, some features may not behave consistently across all browsers or devices.
+
+**Platform Limitations**
+    - **Scrolling issues on iOS Safari.**
+    - **Video playback limitations:** Native video and YouTube players may not function correctly on iOS web.
+
+**Deployment Considerations**
+
+    FlutterFlow does not currently offer direct deployment to the web from its interface. To publish your app:
+
+        1. Export the Flutter project from FlutterFlow.
+        2. Follow the **[Flutter Web Deployment Guide](https://flutter.dev/docs/deployment/web#deploying-to-the-web)** for instructions on building and deploying your app.
+
+:::info[Additional Resources]
+- **[Flutter Web Deployment Guide](https://flutter.dev/docs/deployment/web#deploying-to-the-web)**
+:::
+
+FlutterFlow supports generating web-compatible code, which can be deployed using Flutter tools. However, because Flutter Web is not officially supported, some features—especially on iOS—may be limited. Deployment must be handled manually using an external platform or CLI.

docs/resources/projects/imgs/20250430121510782041.png

@@ -174,7 +174,9 @@ Adding a custom domain to your web app can give it a more professional look and
 :::info[Important]
 
 - Only *Pro* and *Teams* plans include **one** free custom domain. The *Teams* plan comes with one custom domain for the whole team. If you are on the *Standard* plan, you will need to purchase a custom domain, as it is not included in the plan for free.
-- Only paid plans can purchase domains. *Standard* and *Pro* users can buy from their *Account* page, and Teams owners can buy it from **[My Organization](../../resources/projects/how-to-collaborate-on-projects.md#sharing-a-project-with-an-organization)**.
+
+- Only paid plans can purchase domains. *Standard* and *Pro* users can buy from their *Account* page, and Teams owners can buy it.
+
 - A single custom domain slot can be linked to only one domain or subdomain.
 - You can connect only one domain to a project, which can be either a root domain (like 'myapp.com') or a subdomain (such as 'beta.myapp.com'). That means if you connect a root domain, none of the subdomains under it will connected to the project. This leads to the rule of '*One project => One domain OR subdomain'*.