Best Practice

Post Reply
vwn
Posts: 5
Joined: 07 Oct 2019, 09:17

12 Dec 2019, 18:07

Hi,

we just bought the theme as extended version and now we would like to use the theme in different (already existing and based on a free primeng theme) projects. But we wonder what would the best way to go:
1) Import the scss files etc. in each project and make all the development within each project (but also have more work when updating or fixing things in the "main theme").
2) Keep the theme in a separate project, create sub-themes for each project?
2a) and deploy the resulting css to the product
2b) use the resulting theme as a dependency via npm?

Do you have any suggestions?

cagatay.civici
Prime
Posts: 18307
Joined: 05 Jan 2009, 00:21
Location: Cybertron
Contact:

17 Dec 2019, 18:25

By theme do you mean the theme.css for the PrimeNG components or the whole layout, in our terms;

- theme: PrimeNG Components Theme
- layout: App layout like topbar, sidebar menu, footer and main content
- template: theme + layout e.g. Roma Template

vwn
Posts: 5
Joined: 07 Oct 2019, 09:17

18 Dec 2019, 10:50

Hi spoke with this terms I mean template :-)
To be precise:
- theme: just use it as it comes from Roma
- layout: based on roma wih some changes to meet our needs

cagatay.civici
Prime
Posts: 18307
Joined: 05 Jan 2009, 00:21
Location: Cybertron
Contact:

21 Dec 2019, 12:23

I think 2 could be a better option, you may publish the app.main.component in a local npm repository and import it from there.

Post Reply

Return to “Roma - PrimeNG”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest