I’m building something similar to https://pcpartpicker.com.
I’m struggling with one of the last things I need to do.
I could either build a product page for all of my different products I have 36 total product repeating group pages. So I would have another 36 Product pages.
Or Should I connect all products to one product page like how pcpartpicker does it.
If I do it that way how do I send 36 different product data to one page? Do I have 36 different groups then show and hide them?
Basically, I’m asking what’s the best practice.
Can Bubble handle 70ish pages?
For the love of the children, don’t make a 70 page app on your first try!
Go into the editor, double click outside the edge of the page, you can set what the “thing” is for this page… in your case a product.
You should have a product table for your products, containing several fields that are the main attributes about the product.
In your page add your texts but make the relevant ones dynamic… “this page’s product’s product name” etc
I recommend taking a step through the tutorials and going slow to understand the basics. I do NOT recommend jumping into bed with the first vendor trying to sell you services to do all this for you on here. If you want to maintain this site yourself in the end, there is no better way than to build it.
Best practice depends on exactly what you’re trying to do (but creating 70 separate pages is not an efficient way to build, especially for this use case).
I’m not sure understand your question fully.
You have 36 products and you want to have a page for each one?
Of you want to display all 36 products on a single page in a repeating group?
Or you want to display 36 related products in a repeating group, on each of 36 other pages?
Having had a quick look at the link you shared, they seem to have a pages of computer builds, and then on each of those pages they are displaying a list of parts for that particular build.
Is that what you’re trying to achieve?
If that’s the case you need to have a datatype that will contain the products for each page (if it’s only 36 products the using a list field will be the best way to link them).
Then use that datatype as the page’s content type, and display that database entry’s products on a repeating group on the page.
So, using https://pcpartpicker.com. as an example, you can have a datatype of ‘Build’ with each Build having a list of parts.
Then your Build page has a content type of Build, and on that page you can have a repeating group to display that page’s Build’s list of parts.
So I already have 36 pages that are repeating groups that function similar to this https://pcpartpicker.com/products/motherboard/ for each category.
Going with the pcpartpicker theme means I have 36 pages that are
Cpu’s
Graphics Card’s
Motheboard’s
What I need more clarification on is when you click on a product more find more details. This motherboard for instance. https://pcpartpicker.com/product/jcYQzy/msi-b450-tomahawk-max-atx-am4-motherboard-b450-tomahawk-max.
Do I make 36 different product pages?
Motherboard product Page
CPU product Page
Graphics card Product Page.
or
do I have one product page with 36 different groups?
Motherboard product Group
CPU product Group
Graphics card Product group
If it’s one product group what’s the best way to send data to that group from the product category page.
Because at my level in bubble it’s easier for me to clone 36 product pages and set them to each specific category.
But if the best practice is to have one product page with 36 different groups I’d be willing to that I just don’t know how to send the proper data.
You only need to create separate pages if the layout and page structure is different, or there some other major differences (although even then you could just use a single page with different group layouts shown conditionally).
So, most likely, you only need a single page (but it depends exactly what you’re trying to achieve).
So I already have 36 pages that are repeating groups that function similar to this
You mean you have 36 individual pages? Or one page with 36 database entries?
In any case, from what you’ve said it sounds as though you only need 2 pages.
One to show your repeating group with the products in, and another one to display the product details (this is a fairly standard approach for ecommerce sites).
For example, you might have 1 page called ‘Category’ and one page called ‘Product’.
On your Category page you show a repeating group with all the products in that page’s category.
Then on the product page you show the details of a particular product.
Your category page has a content type of Category (which is a datatype in your database).
Your product page has a content type of Product.
On your category page, the repeating group data source is the products from the current page’s category (however your 2 datatypes are linked).
When a product is clicked, navigate to the product page and send the current cell’s product data to that page.
This, I have 36 individual pages, each one with one database entry. Instead, what your saying is I should do one page with 36 groups and have conditionals to show the corresponding group.
It will be basically the same layout for each group. I just found it easier to manage each page separately. I started figuring that having 36 different pages was probably not the best way to go about it.
Just 1 page with a defined content type. Bubble will then create the 36 pages for you - one for each database entry - based on the URL (either the database entry’s unique id or Slug if you have them)…
