[QUESTION] Does JFW have default links for Cpanel site?

[nashinnov8]

What's your question?
Does JFW have default links for the cPanel site?

What have you tried already?
I want to make a feature that allows our users to access the CPanel default links. To be more concise, in our service, such as contact and browser, there will be a button in the header that allows them to view their profile on the cPanel site.

Moreover, I would like JFW to provide me with default links for my cPanel site, such as 'View Profile', 'Sign Out', and 'Pricing'.

Example: https://cpanel.myphones.app/profile/general -> To view the user's profile

[kenn3thx]

The links used within the cPanel are static and currently defined directly in the JFW frontend project. These links are not stored in any database and are subject to change at any time.

As these are static routes, there is no API available to retrieve them dynamically. Therefore, the recommended approach for now is to manually define these URLs as constants within your project.

That said, using cPanel in this manner does not align with the intended system architecture. Below is how JFW categorizes domain usage:

⸻

Domain Types in JFW

We classify domains into four main types:

1. Admin

This is the admin portal of a specific brand. It is pre-configured and includes source code that is fully controlled by the JFramework system. Users cannot modify or interfere with the code in this environment.

2. CPanel

This is the centralized management interface, exclusive to the JFramework ecosystem. It supports account-level operations such as:
• Wallet management
• Viewing the list of owned brands
• Subscription and billing management
• Editing personal information, configuring security settings, etc.

Note: CPanel is not designed to be shared or reused by other brands. Users do not have permission to alter or inject code into it.

3. Client (or Custom)

This type is intended for user-facing applications developed by customers or partners.

In the near future, Clients will be able to reuse shared UI components such as Pricing, Profile, Sign In, Sign Up, etc., through the upcoming jfw-design library.

In addition, Clients can extend their implementation with domain-specific features — for example, in your case, adding a Location page to display a list of device locations depending on the business logic.

4. Protocol: Domain

This model is used specifically for API communication. Instead of relying on a shared backend domain, each brand can define its own API endpoint using the structure protocol + domain (e.g. https://brand.example.com/api/...). This ensures data isolation and brand-level separation.

⸻

Current Issue

Based on your description, it seems that you are developing a Client, but treating it as a CPanel. This approach does not align with the original architectural intention.

⸻

Recommended Approach

In the long run, we recommend implementing views such as Edit Profile, Pricing, and others directly on your domain (Client), instead of redirecting users to the cPanel.

However, we understand that the necessary components are not yet available. Once the jfw-design library is released, you will be able to integrate those features into your application more seamlessly.

Temporary Solution

While waiting for jfw-design, it is acceptable to temporarily redirect users to the existing pages on the cPanel (e.g., /profile/general, /pricing, etc.) if you need to deliver those features sooner.

Please keep in mind:
• These URLs should be manually defined as internal constants
• And should be monitored for changes in case their structure evolves

⸻

If you need help defining those constants or would like a list of sample URLs, feel free to reach out.

Alternatively, you can manually access the cPanel and copy the routes you want to redirect to, based on your current use case.