To choose a license it's important the purpose of the project.
If you will use the template for one project for one client, Single License is suitable for this case.
Extended license only applies when your project is created for more than one client, and all those clients are charged for the use of your end product, being a service or another product for resell.
Please refer to the marketplace usage license to get a final word about this.
This product comes adapted to different frameworks (angular, netcore, rails, etc), since it's only one product, the chosen license will apply only for the project version you decide to use.
It's not necessary to place your license in the final product. You need only to keep it with you in case it could be requested in the future but no necessary to be available in your code.
Both projects are almost the same. Main difference is that the Seed only has a few routes and dependencies. The purpose of the seed project is to provide a starter project where you can go adding more features progressively.
If you use the full-features version, you can customize it by removing features according to your project needs. If use the Seed version, you can customize it by adding features. It's mainly a personal choice of how you prefer to work.
The template was designed to build your application on top of it and not to integrate with another application, meaning, if you have separated components already created you can add them to the existing structure of the template with routes, views, etc. But if your application relies on an existing layout and structure, it's necessary to adapt it to the template.
A good option is to use a Seed version, it has a few dependencies and you can go adding there your own components, one by one if possible so you can isolate any issue that may appear.
Yes, after purchase, all updates to this product can be downloaded for free. You will receive an email from the marketplace with the link to download the new version.
The best practice recommended for update is to keep own code the most separated as possible from the template code. In that way, you can simply drop a new version without worrying to review many files. Anyway, this depends on each project and there are cases where you need to change parts of the template, using a comparing tool is the best option. WinMerge, Beyond Compare or Kaleidoscope are great solutions.
Another good approach is to update only those components that you need for your app, this requires to be more familiar with the organization of the project, but will help to discard parts that are not needed reducing the update process. In the changelog you will find details about what files were added/modified/delete for each version.
Currently I'm not taking custom jobs or consulting services.
Yes, the changelog for each version can be found in the product description page. The change.log file in the downloaded package also states each file status (added, modified, deleted).
The version number can be found in the changelog. Or, depending on the project, by looking into the sources in the main styles and scripts files.
Yes, documentation is included for each project version in the package.
Although the product includes a documentation that presents the main features such as structure, usage, compilation and execution, etc. It is necessary to have a basic knowledge of coding languages, frameworks and modern web technologies.
Each version is based on a different framework (angular, react, vue, etc), with different features and created for different purposes. The correct version you choose should depend on the requirements of your project.
No, unfortunately due to the nature of digital goods is not possible to provide source code for demonstration nor a trial version.
Online demo for all versions are available for test in the product preview page.
The code distributed in the downloaded package is exactly the same used to build a production release that then it's uploaded for each demo.
You can also get in touch to clarify any doubt you have about the product.
This is a representation of the folder structure and files organization that you will find in the product package.
Here you can see each folder is a project itself with no relation of dependency with other folders. You can grab the folder with the project of your choice, drop the rest and start working on it.
The following table aims to show the assets used to build this template and information related to license is only for reference and must be validated.
Click on each project name to see a list of dependencies used. The list includes the package name, a link to the website/repository and the license(s) with a link for reference.