Customising Episerver Forms

Practical notes

1 min read

Customising Episerver Forms

Verify field rules, record storage and notification delivery separately. Base confirmation on persistence and do not imply that saved data was lost when a notification fails.

Putting content management into practice

A content model defines independently maintained and reusable information. Authoring, preview, approval and publication form a workflow; an API response validates only one part.

Checking the result

Have real editors create, change and restore content using long headings, missing fields and multiple languages. Record development dependencies and release ownership.

Related practical notes

Practical notes

Episerver Personalization with persistent anonymous profiles

Separate temporary session preferences from persistent identifiers and provide a reset. Unidentified visitors should not receive content that depends on personal records.

Episerver Personalization with persistent anonymous profiles
OXOAK / Editorial

Practical notes

Practical notes

Practical notes

Explaining the purpose of a technical event

State the topic, audience, schedule and registration outcome, with a route for changes or cancellation. Use only confirmed partner marks.

Explaining the purpose of a technical event
OXOAK / Editorial

Practical notes

Practical notes

Organising a set of technical contributions

Practical notes

Organising a set of technical contributions

Organise contributions by problem, method and inspectable result. Preserve attribution and confirm names and disclosure with contributors.

Organising a set of technical contributions
OXOAK / Editorial

Practical notes

Practical notes

Optimizely

Practical notes

Generating image metadata and SVG thumbnails with Episerver DXC Azure Blob storage

Store dimensions, format, alternative text and permissions, retaining originals when creating thumbnails. A successful upload does not establish suitability for every crop or device.

Generating image metadata and SVG thumbnails with Episerver DXC Azure Blob storage
OXOAK / Editorial

Practical notes

Practical notes

Keeping recognition information accurate

Practical notes

Keeping recognition information accurate

Record provenance and publication dates and review current terminology. Rebranding a page must not transfer another organisation’s facts.

Keeping recognition information accurate
OXOAK / Editorial

Practical notes

Practical notes

Practical notes

Showing verifiable technical expertise

Use public documentation, code or implementation notes and state contribution boundaries. Do not transfer unverified personal recognition to OXOAK.

Showing verifiable technical expertise
OXOAK / Editorial

Practical notes

Practical notes