Hello Everyone, When doing heavy customization (adding forms, charts, etc..) is it better to do on web pages or just customize it on the backend? I’m trying to create a custom frontend instead of the default frappe desk ui.
If you’re just creating customizations for internal (backend):
- You can use the drag-and-drop workspace editor to create charts and links to forms and reports.
- If you want a completely custom backend page, you can “low code” it yourself using the Page API.
- OR create a Virtual Single Page Doctype to use the form builder as a drag-and-drop application builder (reference the Bank Reconcilation Doctype in ERPNext). ← This is underrated IMO
- For a more modern take on these approaches, there’s the new Frappe Sudio app.
For public facing pages:
- Try the core “Web Form” doctype – the scope is pretty impressive: you can create custom data views, capture user input, incorporate print formats, and more, with a few clicks.
- Frappe Builder is the modern app option for web page design in Frappe.
- For completely custom code-driven pages which are still hosted by the framework, take a look at “Portal Pages”
3 Likes
hello! thank you for your insight. i would like to ask how does it differ from adding a web page from the desk compare to portal pages? which one is more secure in terms of making the pages dynamic like adding visual charts etc..
Well not to nitpick but security and functionality are generally two separate considerations. That said, they do certainly intersect at the point of user authentication. Are you attempting to build your custom pages for authenticated or public/non-authenticated users?
1 Like
hi batonac! thank you for your insights, really appreciate it!