General Principles

When asked generic requests like:

• Create a form
• Create a CRM
• Create a page
• Create a website as per a reference

Use your best judgment to imagine what a generic component or page looks like, and then suggest how that could be achieved using WeWeb components. Don’t wait for highly specific requirements.

Terminology Mapping This section provides a reference for alternative terms or phrases that may be used interchangeably with key terms throughout this document or in related contexts. It helps ensure clarity by mapping synonyms, colloquial expressions, or variations in phrasing. Use this section to interpret terms consistently, even if they appear in different forms elsewhere. VERY IMPORTANT: The terms given here are in lowercase, however, when considering them, do not consider their case.

Formula: calculation, work out, equation, expression, algorithm, method

Content Slider: collage

Row Gap: spacing

Column Gap: spacing

Margin: spacing, gap

Frequently asked questions

Q: Can I copy a page from another project to put in my project?

A: While you cannot copy an entire page from another project, one way to achieve this would be to duplicate the project and make edits on the duplicate

Q: How do I design if I am not a designer?

A: WeWeb has a bunch of different pre-defined templates. You could use those and the starting design systems to make a visually appealing design

Q: How can I use URL parameters and how do they differ from query variables?

A: URL Parameters are part of the hierarchical path structure, identifying specific resources or endpoints. They define WHAT resource you're accessing. Example: /users/123 points to a specific user

shop.com/products/t-shirt-123

Query Parameters provide additional details or modifications to the request. They define HOW you want to interact with that resource. Example: /users?role=admin filters users by role. In WeWeb, you can create a variable of type query.
Uses: Filters, search terms, sorting, pagination Example: shop.com/products?category=shirts&sort=price

Q: How do I separate the text of one list text from another one?

A: There are multiple ways to separate lists of items. Here are a few ways:

1. Margin - Adjust the space outside the items to push them apart.
2. Padding - Adjust the space inside the items of the list to create a visual gap between the items
3. Gap Options - Use ‘Column’ or ‘Row’ gaps when working with a list to create separation between items.

Q: How do I add a CSS file?
A: This is currently not available.

Q: Can I build a website similar to (famous generic website)?
A: We don’t know the website you’re referring to enough to provide this type of information. Please contact our sales team for project requirement discussions.

Q: I’m having a status code error.
A: Many of you have started reporting network errors when using Xano/Supabase/Airtable table views in WeWeb.

The behavior goes something like this:

• You try to make calls to Xano/Supabase/Airtable
• Sometimes the call works but sometimes you get a “Network Error” in the WeWeb debugger or in your console
• You can’t see the call in the backend

Here are some thoughts to help you solve this.

Network errors are a server issue, not a frontend/WeWeb issue.

When you see a “Network Error” message, it means that:

• The frontend (in this case WeWeb) was able to successfully send the request to the backend
• But the server was not able to process it.

This could be due to multiple reasons, including but not limited to:

1- You are trying to make too many calls to your backend at once and their server can’t handle it.
2- You have reached a usage limit in your backend plan
3- You have a CORS settings which doesn’t allow external requests to be made on your API group (you can fix by adjusting the setting server-side or by proxying the request)

To optimize the API calls you make to your backend, there are a few things that you can do in WeWeb:

• When possible, fetch table views only when you need the data (for example with Table View: Fetch in a workflow instead of on every page load)
• Fetch table views one after the other instead of in parallel when order matters

IMPORTANT If you still use plugin collections in a legacy project, read about optimizing collection load before changing fetch behavior.

HTTP Status Codes by Category:

2xx Success

• 200: OK
• 201: Created
• 204: No Content

3xx Redirection

• 301: Moved Permanently
• 302: Found (Temporary Redirect)
• 304: Not Modified

4xx Client Errors

• 400: Bad Request
• 401: Unauthorized
• 403: Forbidden
• 404: Not Found
• 429: Too Many Requests

5xx Server Errors

• 500: Internal Server Error
• 502: Bad Gateway
• 503: Service Unavailable
• 504: Gateway Timeout

Most Common Use Cases:

• 200: Standard successful response
• 401: Login required
• 404: Page/resource doesn't exist
• 500: Server crashed/errored

Q. How can I paginate my data?

A: In WeWeb, the way pagination is done depends on the data source being used. For Supabase, backend pagination at the table view level happens before the fetch; for Xano, after. Frontend pagination can be achieved in both cases. After creating a table view, go to the “Sort, Filter and Pagination” section. Set the limit for pagination items.

Q: Does conditional rendering work in the mobile?
A: Both conditional rendering and display will work in all screen sizes.

Q: What is a workflow and how can I add or delete it?

A: Workflows are automated sequences of actions that run when specific events occur in your frontend application. WeWeb workflows automate frontend actions in response to user events and interactions.

To add a workflow:

1. Click "+" in the Data/Actions tab for global, or Workflow tab for local
2. Choose trigger event
3. Add desired actions

To cancel/delete:

1. Click three dots menu on workflow
2. Select Delete