Guide Publishing and Update Principles
This page explains how to assess the source and scope of information in our corporate technology guides. We distinguish company information, technical explanations and illustrative scenarios to help you prepare service requirements.
Updated:
Publisher and purpose
Disket Teknoloji Ltd. Şti. publishes these guides. Our sector activity began as a sole proprietorship in 2014 and continues under the limited company today. The sector start date does not state the incorporation date of the current limited company.
The guides help businesses identify server, hosting, email, GPU, data center and software requirements. Use them to prepare questions about resources, access, backups and operational responsibilities for a proposal discussion.
Technical sources
Sources are linked at the end of the relevant guide. Manufacturer documentation and original standards help explain protocols and product behavior. A source link does not incorporate that provider’s service terms into a Disket proposal.
Check the product version and documentation date before applying an explanation. Licensing, compatible hardware, service limits and regional options can change. Evaluate the source against your own configuration.
How content is prepared
AI assistance is used to prepare guide drafts and some conceptual illustrations. It helps structure topics and draft explanations. Conceptual service illustrations are identified in their captions.
Numerical examples state their assumptions. Company history and service descriptions draw on information provided by the company and the published scope. Customer results and measured performance require an identified factual basis.
Examples and service commitments
Hypothetical scenarios illustrate the impact of decisions. A failure scenario or memory calculation is not a measured customer result. The project scenarios page also identifies examples as illustrative.
Hardware, availability, pricing, SLA, backup retention and intervention scope are defined for each project. Use the guides to prepare requirements and the written proposal to assess the agreed service scope.
Publication and update dates
A guide’s update date changes when its content receives a meaningful revision. Its original publication date is kept separately. A layout or menu change does not mean the technical explanation has been reviewed.
Check both the guide date and the linked source version before a critical operation. Product changes and reported inaccuracies are reasons to reassess explanations and source links.
Report missing or inaccurate information
Use the contact page to report unclear, incomplete or outdated information. Include the guide URL, section heading and supporting technical source.
Do not send passwords, access keys or customer data. Discuss an appropriate sharing method first if project details are required.