Questions about publication websites and shared tools

Can the site contain Albanian, Serbian Latin and English material?

Yes, a project can support the agreed language editions and scripts. First identify what actually exists, what needs to be prepared and who can review it. A complete report, a summary and a translated navigation label have different purposes. The site should explain those differences instead of presenting every language link as an equivalent full edition.

Does that mean project meetings and support are available in those languages?

The usual technical working and handover language is English. Other arrangements require agreement for the project, including suitable people to review specialised content. The website's language pages do not by themselves establish translated support, certified translation or staff fluency.

Can we keep our existing content-management system?

Possibly. We inspect the task it needs to support and the way it currently behaves. A publication record, search rule or editing instruction may be repairable within the existing platform. Replacement is considered when the required capability or maintainable path cannot be established, not simply because the current site looks dated.

Will old report links keep working?

Their treatment needs to be included in the migration plan. Some should continue to reach the same publication or file. Others may require an explanatory destination or a deliberate replacement. A single redirect of every old reference to the homepage usually loses the information that made the original citation useful.

Can partners check a document without seeing everything else?

That is a possible workspace requirement, but it needs actual role and material definitions. Identify the partner's people, the collaboration they belong to and the review they are being asked to perform. Tests should include both a permitted task and a prohibited one. A partner's organisational name alone is not a complete access policy.

Can the website approve programme eligibility or institutional statements?

Those decisions stay with the organisation and its appropriate advisers. We can build a route that presents approved information, collects an enquiry or records a review. The implementation does not supply authority to make a professional or institutional decision.

Do you remediate PDFs as part of a website redesign?

Only when the document work is explicitly included. Improving a library record or download label helps readers reach the document, but it does not establish the document's reading order, tagging, alternatives or other accessibility properties. We agree the pages, documents, tasks and testing methods in scope.

Can an event page connect to our registration provider?

We first inspect what your provider and account support. A supported link may be sufficient; a deeper connection may require permissions, stable event references and a way to handle unavailable or changed information. The public event description and the provider's registration outcome must remain consistent without assuming they are the same system.

Is ongoing maintenance included automatically?

Maintenance and support need a defined arrangement. The agreement should identify the systems covered, access, update responsibilities, recovery expectations and how new work is requested. Hosting, third-party subscriptions, editorial work and urgent response should not be left to inference.

What should we send first?

One public page or safe example, the person trying to use it, and the result they need. Include required editions and the people available to approve the content. The contact page explains the enquiry details, while scope and pricing describes the decisions needed before estimating delivery.