Hi, I’m applying to a business request of a potential client, but there are some topics I’m not sure how to cover with Weweb. The business case is to develop a commercial website, that is meant to grow and to include several functionalitites in the future (being able to get reports, with an auth workflow etc). Two points thus remain :
is it possible to create a blog on Weweb ? How would you do this to simplify the blog posts on my client side (creation of the whole “back office” interface ?)
the client would like also to have reports like number of visitors/day, numbers of click/day, number of form completion etc. How can this be done in Weweb ?
Right now the best solution is to separate the Website part from the WebApp part.
You could use other solutions like Webflow for the website part, and navigate to an admin dashboard (in WeWeb) as a button.
This now runs off Supabase. I had to build my own admin UI to handle all the uploading and image storgage - just because I wanted full control over it.
If you don’t want to build the Admin UI, as I originally did, I had my blog running on Hashnode in headless API mode, which worked fine. However, they changed their pricing model so it’s expensive if you have more than 1 user now unfortunately. It’s a decent option though, but you have to get your hands dirty with cloudflare workers to manage pagination as Hashnode limits you to 20 max blogs on the api at once, but you can get round that. If anyone’s interested in this approach I can help them with this as creating a blog isn’t out of the box yet on WeWeb.
Not sure why others including @Agustin_Carozo from WeWeb team are saying to use WebFlow or not a good solution? Webflow is the competition
IMO, you can absolutely build a admin and reporting dashboard, with full auth and blogs. There’s no limits (except for SEO)?!
yeah I would be interested to know more about your statement @Agustin_Carozo about using another service for the landing page part (with Webflow or even Wordpress?).
I believe it’s SEO-related yes, and over all, each tool has a proper goal.
Finally I’m thinking of proposing this stack : Wordpress (static site), Weweb (client portal) and Supabase (for backend).
I’m learning Webflow but currently I’m best on Wordpress, don’t want to take risks!
yes, they have an Excel (listing all their centrales in France) file they want to use. The static site aims to display an interactive map, displaying markers representing different location of centrales.
The centrales displayed should be updated based on a specific rule, when the user enters his/her postal address.
Thinking of using Wordpress + Mapbox + n8n for this part, and for the client portal part Weweb + Supabase
The blog is not in the scope anymore (but could be un the future) !
Let me try to explain a bit more why we typically recommend tools like Webflow, WordPress, or VuePress for landing pages and blogs
We’re strong believers in using the right tool for the right job whenever possible.
For static content like landing pages and blogs, these tools shine because they offer excellent out-of-the-box SEO. That’s why we use them ourselves for SEO-focused projects like our marketing site and user documentation.
But when it comes to projects that require interactivity or app-like functionality, they don’t come close to WeWeb! That’s where we shine and why we use WeWeb for our internal tools, marketplace, academy, and other customer-facing apps.
Now, can you use WeWeb for landing pages and blogs?
Yes, you definitely can. But it’s important to know that content in WeWeb isn’t pre-rendered. Tools that pre-render or server-side render content generally perform better in search engines and increasingly in AI-driven platforms like ChatGPT or Perplexity.
That doesn’t mean SEO is completely off the table with WeWeb. You can still make your WeWeb site SEO-friendly and performant by following some best practices.
Here are some things that you can do on your WeWeb apps that will improve its SEO performance (and user experience):
Use semantic HTML and metadata
Add meaningful titles & meta descriptions to every page
Use proper heading structures (h1, h2, etc.)
Include alt text on all images
Use native elements with the correct HTML tags (e.g. buttons, select, etc.)
Optimize for performance
Compress and resize images
Avoid overly long or complex pages
Reduce unnecessary nested containers
Fetch data only when needed
Use backend filters to limit data on load
Use linked sections to avoid re-fetching already loaded data
I think my issue is it’s because the admin behind the site is in the same codebase. I’m considering splitting the whole project into 2 WeWen projects as a result. I didn’t initially because I read from official team at weweb not to do this in the forum.
However, how is WeWeb’s performance impacted by projects getting larger, with more variables, logic, etc? Obviously I know it plays an important part, and I’ve been incredibly careful with what loads when and I’ve done everything to reduce database requests etc. But if the front facing site still loads variables only relevant to the CMS admin for example, then it’s going to impact it. I’m unsure of how efficient and intelligent it is at loading content.
But if WeWeb must load the entire JS of the project on first load, then it’s unavoidable unless splitting website I think.
Use semantic HTML and metadata
Optimize for performance