Information architecture & content register
Inventory current pages, documents and owners; define navigation, metadata, review status and retirement rules for approved content.
Website design & development for Delhi organisations.
GreyBath helps Delhi organisations turn policy, services, publications and stakeholder enquiries into clear, governed websites that authorised teams can maintain.
Plan the content and governance model
01 / What we build
Build around information ownership, not only page layouts.
Accessible templates & governed CMS
Design responsive, keyboard-usable page patterns and CMS permissions for approved editors, reviewers and publishers.
Enquiry, membership & migration controls
Route enquiries and member actions, map legacy URLs, verify redirects and document launch, rollback and post-launch ownership.
City context, honestly stated
A remote website engagement for Delhi organisations.
We work remotely with Delhi teams through content inventories, design reviews and documented approvals; GreyBath does not claim a Delhi office or walk-in presence.
Separate information from promotion
Clarify which pages explain services, publish approved information, recruit members or direct a specific enquiry.
Record who may publish
Assign authors, reviewers and publishers so time-sensitive or sensitive updates cannot bypass agreed approval.
Keep archives findable
Give policies, notices, reports and event records durable URLs, dates and clear archive states.
02 / Where it fits
For organisations accountable to several audiences.
This route fits organisations managing public information, recurring publications or stakeholder services. It does not imply government affiliation, sector credentials or a local office.
Associations & member bodies
Organise membership information, committees, events, publications and contact routes under named content owners.
Professional & advisory firms
Explain services, credentials supplied by the firm and enquiry requirements without unsupported claims.
Public-interest & programme teams
Publish approved guidance, resources and updates with accessible navigation and visible review context.
Education & knowledge organisations
Structure programmes, participation information, resources and recurring announcements for distinct audiences.
03 / How we work
Audit content, establish authority, migrate with control.
Inventory content and authority
Map audiences, high-risk information, documents, forms, owners and approval rules.
Prototype governed templates
Test navigation, reading order, mobile behaviour and editing states with representative content.
Migrate and establish ownership
Verify redirects, forms, permissions, accessibility and backups; document launch and future review responsibility.
Define the publishing and enquiry boundary.
Content volume, approval risk, page types, document archives, languages, CMS permissions, integrations and migration dependencies shape the proposal and review plan.
Discuss your projectContent and evidence
Page types, documents, owners, review dates, languages and material your team will approve.
Publishing governance
Roles, permissions, editorial stages, accessibility checks and archive or withdrawal rules.
Systems and ownership
Forms, member tools, analytics, redirects, hosting, backups and named post-launch responsibility.
How do you handle outdated or duplicated content?
We create a content inventory, identify the accountable owner and agree whether each item stays, merges, redirects, archives or is removed.
Can different teams update only their sections?
Yes. CMS roles can limit editing and publishing by section or content type. The scope records permissions, approval stages and recovery responsibility.
Can the website include Hindi and English?
Yes. Your team supplies or approves translations and terminology. We define language switching, page relationships, layout testing and responsibility for future updates.
Can enquiry or membership forms connect to existing tools?
Yes, when the destination system, fields, consent text, access, duplicate handling and failure path are defined. Third-party licences and vendor changes remain separate.
How will existing links and documents be protected?
We inventory important pages and documents, retain stable URLs where appropriate and map approved redirects. Search visibility cannot be guaranteed, and monitoring is separately scoped.
Important content has too many versions and owners?