Choose a platform around its editors

Explaining a developer’s contribution in a portfolio

Choose a platform around its editors
OXOAK / Content and design

Practical notes

1 min read

Explaining a developer’s contribution in a portfolio

State owned modules, collaboration and disclosure boundaries. Separate project outcomes from personal contribution and omit unsupported credentials.

Choose a platform around its editors

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.

Choose a platform around its editors

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

Support records

Support records

Project discipline

Define support records responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Titles and summaries

Project discipline

Define titles and summaries responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Tool permissions

Tool permissions

Project discipline

Define tool permissions responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Delivery scheduling

Delivery scheduling

Project discipline

Define delivery scheduling responsibilities, inputs, collaborators and review outcomes. This page describes a discipline; staffing is agreed for each project.

Keeping technical supplier relationships transparent

Practical notes

Keeping technical supplier relationships transparent

Explain platform, implementation and hosting responsibilities, costs and support routes. Make account ownership and data location clear.

Practical notes

Practical notes

Explaining a developer’s contribution in a portfolio

Practical notes

Explaining a developer’s contribution in a portfolio

State owned modules, collaboration and disclosure boundaries. Separate project outcomes from personal contribution and omit unsupported credentials.

Explaining a developer’s contribution in a portfolio
OXOAK / Editorial

Practical notes

Practical notes

Umbraco introduces composable DXP offering

Practical notes

Umbraco introduces composable DXP offering

Define interfaces for content, search, analytics and identity and preserve export and replacement paths. Test failure isolation before adding more systems.

Umbraco introduces composable DXP offering
OXOAK / Editorial

Practical notes

Practical notes

Umbraco Cloud Australian data centre welcomes first commercial customer

Practical notes

Umbraco Cloud Australian data centre welcomes first commercial customer

Inventory data, audience and dependencies and record storage and processing locations. Hosting location alone does not describe every data path.

Umbraco Cloud Australian data centre welcomes first commercial customer
OXOAK / Editorial

Practical notes

Practical notes

Umbraco cDXP targets enterprise market

Practical notes

Umbraco cDXP targets enterprise market

Validate multisite, roles, approval, integration and maintenance separately. Enterprise labels do not replace real content and editor testing.

Practical notes

Practical notes

How to choose the right CMS

Practical notes

How to choose the right CMS

Use an article, product and approval as sample tasks. Have real editors author, preview and restore content and record assistance and maintenance costs.

How to choose the right CMS
OXOAK / Editorial

Practical notes

Practical notes