Replies: 1 comment
-
|
Hey,
I'm glad you like the repository. I've set it up so that you can customize
any part of the site. Just like you would with a WordPress theme and its
child theme. So you would just override the parts of the site that you want
to customize. This way, you can update the code in the GitHub repository
without losing your customizations. I'm probably going to add the
`woonuxt_base` folder to a repo (example
<https://nuxt.com/docs/guide/going-further/layers#git-repository>) of its
own and have the demo repo separate. But for now, overriding the components
and pages is the way to go.
Kind regards
Scott
…On Mon, Apr 15, 2024 at 2:57 AM MA ***@***.***> wrote:
This repository is excellent, but I'm concerned about the time it will
take to update my code. Let's say I download this repository, customize it
for a client, and then, a few months later, I need to update the code due
to a bug or to add a new feature. Since the code in the GitHub repository
has been updated, what approach should I take here?
—
Reply to this email directly, view it on GitHub
<#151>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHBH7LOFXELPSX6IG32OY3Y5MXXTAVCNFSM6AAAAABGGN5QOSVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGUYDONJTGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This repository is excellent, but I'm concerned about the time it will take to update my code. Let's say I download this repository, customize it for a client, and then, a few months later, I need to update the code due to a bug or because of a new added feature. Since the code in the GitHub repository has been updated, what approach should I take here?
Beta Was this translation helpful? Give feedback.
All reactions