Missing upgrading tutorial in documentation about ct-material-kit-pro-react

[lukaszswitaj]

Thank you @einazare

[einazare]

Hello @lukaszswitaj ,

And thank you for your interest in using our product.
Can you please provide a tutorial on how you should update this product so we can know how to make one?
We've always believed that the CHANGELOG.md should be enough for this.

Best,
Manu

[lukaszswitaj]

Thank you for reply, @einazare ,

I would like to know that myself ;)

The thing is, I'm not sure how to make the correct upgrade. I do not know which files to overwrite, which subdirectories to replace, which NPM commands to call in the console, etc.

Of course, in theory, I can make a copy of my project and try to make it work.

As the creator, you are the only people who know how to perform a full correct upgrade of an existing project. I assure you that if I was a more experienced programmer, I would be tempted to publish such tutorial.

Regards
Łukasz

[einazare]

Hello again @lukaszswitaj ,

We are going to think of something and try to make a tutorial for this.
Not sure how, since every of our clients have their own projects, and we can't figure out a way to generalize such tutorial.
Maybe make our CHANGELOG a bit more specific.
Anyway, we are going to think of something.

Best,
Manu

[einazare]

Hello there, @lukaszswitaj ,

We've devised a way to make updates of our products.
The easiest way to make updates is as follows:

• You create two repositories on a versioning control system (for example GitHub, GitLab, Bitbucket etc.) - if it's a PRO paid product, we suggest that the repositories to be private
• On the first repository, you add our product unaltered
• On the second repository, you add our product and/or develop your project
• Each time we release a new version of the product at hand, you download again the product, and put it on top of the first repository, the versioning control system (for example GitHub, GitLab, Bitbucket etc.) will tell you all the differences between the versions
• By using a repository, you can even make new branches for each of our new version, that way, you will always have all the versions

Hope this information is of help. If you have further questions, let us know.

Best,
Manu
ReactJS Developer @Creative-Tim.com