01 / Site inventory
Review content, plugins and existing URLs.
Content
01Content02Design03Technology
KG-NET / WordPress
Manage content. Keep control.
Planning, design and technology are considered together. Scope and price follow your actual requirements.
01Content02Design03Technology
WordPress
How it comes together.
Three perspectives on your project. Scroll through the process or select a step.
02 / Editorial system
Configure templates and permissions.
Design03 / Handover
Document editing and update routines.
TechnologyWORKING TOGETHER
Clearly agreed. Clearly delivered.
A defined scope
Before work begins, we agree goals, content, responsibilities and integrations. You know what is included and what needs a separate plan.
Reviewable milestones
Structure, design and function are reviewed in clear stages. Decisions follow your requirements and feedback.
A clear handover
The agreed scope defines access, guidance and an understandable operation and maintenance plan. Ongoing support is agreed explicitly.
WordPress websites: An editable website with thoughtful structure and maintainable technology.
What we build with you
Your team should edit pages without accidentally changing business logic or global design. We structure templates, editorial roles and extensions for manageable daily work in WordPress.
- Theme configuration
- Editorial components
- Roles and publishing workflows
- Update and maintenance plan
WordPress is planned as an editorial system. Content types, roles and media rules define who maintains information. Business records remain independent of visual design. Relaunches account for existing content and redirects. Updates should first be checked in an appropriate test environment; unnecessary extensions add maintenance without automatically providing value.
How the project takes shape
Site inventory
Review content, plugins and existing URLs.
Editorial system
Configure templates and permissions.
Handover
Document editing and update routines.
What makes working with KG-NET clear
We discuss how your business actually works before specifying individual features. Dependencies, responsibilities and the agreed scope are documented. Decisions are discussed using actual pages, tasks or data flows. Questions, materials and approvals are coordinated with an accountable contact. During handover we clarify what your team can maintain and which technical work requires a separate service. You can see what was agreed and where an additional decision is needed.
20 / QUESTIONS & ANSWERS
Decide with clarity.
What makes effective web design?
Clear information, recognisable actions and readable design. Motion supports orientation without obscuring content.
Will the site work on mobile?
We review navigation, forms, images and touch targets on small screens. The mobile content order is assessed separately.
Can I edit content myself?
Editable pages and components are created in the agreed CMS. Roles reserve technical settings for authorised people.
Can we use Elementor?
Yes. Elementor handles presentation while business logic and protected client data belong in independent modules.
How do animations stay fast?
We limit active effects, load media when needed and respect reduced motion. Testing on actual devices is essential.
Are existing URLs preserved?
Existing addresses are inventoried and retained where possible. Changed URLs receive specific redirects.
How is accessibility considered?
We review semantics, keyboard access, focus, contrast and form labels. A formal conformance audit is a separate scope.
Can the website be multilingual?
Language versions get separate URLs and matching links. Text and media labels need editorial care in each language.
How does the project start?
We clarify the audience, existing systems, responsible people and intended outcome, then agree the scope.
What determines the price?
Scope, integrations, content, licences and support are considered separately. You receive an individual offer before delivery starts.
When is the schedule agreed?
After discovery and prioritisation we agree milestones. Approvals, access and external dependencies influence dates.
Who supplies content and access?
We agree which text, images and data you provide. Access should use roles, invitations or limited tokens wherever possible.
Can existing systems keep running?
Yes, subject to a technical review. We plan changes, backups and rollback paths to keep the transition controlled.
How are changes agreed?
Questions are collected in the project. Extensions get a defined scope and approval before additional implementation.
How is acceptance handled?
We agree concrete test cases and responsible people. Open issues are documented and release follows the agreed approval.
Is a handover session included?
Handover can include training, documentation and defined access rights. The scope and format are specified in the offer.
What happens after launch?
Support, updates and response times are agreed separately, making internal and KG-NET responsibilities clear.
How is personal data handled?
We limit access and review data flows, retention and processor arrangements. Legal approval remains with the controller and their advisers.
Can you work across borders?
We work with businesses in Austria, Germany, Switzerland and Serbia. Language, responsibilities and actual market needs are agreed together.
How are outcomes assessed?
We agree verifiable goals and identify the data source. Without connected measurement there are no invented metrics or guaranteed outcomes.
Plan the connected services together
Depending on your project, we align this service with related areas. Content, technology and responsibilities should fit together. Discuss the interfaces and actual scope you need with us:
THE NEXT STEP
Your idea. A clear plan.
Tell us what you want to change. We will clarify goals, scope and the right approach, with an individual proposal.
KG-NET
Ilija Benjak
Völkermarkter Straße 280
9020 Klagenfurt am Wörthersee
Austria