Before a WEBSALE online shop can be individually customized, some basic prerequisites are required. This page explains which technical and administrative access is necessary to begin editing.
A provisioned WEBSALE online shop forms the basis for all customizations. It contains prepared configurations, standard templates for the storefront, and tools for managing shop data and settings. The shop and the initial access credentials to the Admin Interface (first user) and to GitLab are provided by WEBSALE upon provisioning.
In addition, access to the Admin Interface is required to adjust important configurations such as taxes, currencies, languages, products, and shipping and payment methods. The corresponding permissions are a prerequisite for editing.
For the development and management of the storefront files, GitLab is used by default. It enables version control and structured work with the template files. Changes to the code can be tracked, documented, and shared between developers.
Additionally, a suitable code editor is required to efficiently edit HTML, CSS, and JavaScript files. Programs such as Visual Studio Code or Sublime Text offer practical features such as syntax highlighting and auto-completion to make the work easier. The code editor must be organized independently and is not part of the WEBSALE provisioning.
The WEBSALE demo shop is delivered by default with the Strapi CMS and already contains a defined set of input masks and matching displays for your future shop content. When provisioning your shop, however, you can decide whether a Strapi instance should be set up — if you would like to use a different CMS, the Strapi setup is omitted.
This access provides you with access to all files of the shop, e.g., product images, JSON files, etc.To access the S3 object storage, you can use an S3-compatible client in addition to your browser, e.g., Minio Client, Cyberduck, S3 Browser (Windows), or the AWS CLI.
