EUHUB Workstream workflow
Working to 2 week sprint each stream will include a Tech Lead that will manage the team and development for that stream. The leads/devs are not locked into these stream and can change from sprint to sprint and will be reviewed at the end of the sprint.
SPRINT 1
When we move our brands to MediaOS/InterUnity throughout the EU, we are dividing these into 2 types which is based on the size of the brands content and site traffic.
Clean Start Setup (low content & traffic)
Clean Start + Data Migration (large content & site traffic)
Every brand that is moved over to MediaOS/InterUnity will go through a clean start which involves the setting up of stage/prod instances by Dev Ops and the setup of the brands theme by DEV with the below checklist.
Setup RAMS-ID
Every brand that is moved over to MediaOS/InterUnity will go through a clean start which involves the setting up of stage/prod instances by Dev Ops and the setup of the brands theme with the below checklist.
Create/setup Region theme
Every brand that is moved over to MediaOS/InterUnity will go through a clean start which involves the setting up of stage/prod instances by Dev Ops and the setup of the brands theme with the below checklist.
Setup/configure Content
Spread over CORE feature and front-end template development this stream includes feature sets that extended the CORE and are available to all MediaOS sites with the latest version of the CORE.
This is divided into 2 codebases:
Examples:
Working closely with HDM/HMI, this stream involves the development of front-end/CMS functionality that improves the editorial workflow in the CMS and creates a more intuitive/engaging UX on the front-end.
Process
Oftern linked directly with CORE development for CMS functionality, front-end template development can include:
Process
Using the Quack migration library and toolset, migrations can be done using variety of sources to map content from EZ Publish, Expression Engine and Wordpress:
https://github.com/HearstUK/migrations
Sources:
Process
The global Unity Ad layer and 3rd party services are delivered via ensighten such as Comscore, GA, Lotame, Chartbeat, etc. The Ad layer is current owned/managed by Weyland Jung at Hearst CORP and will not require any development by DEV with the exception of setting up the Ad placements in the MediaOS theme.
For more info on the ensighten deployments, naming conventions and process please check out: http://docs.hdigital.net/ensighten.html
With MediaOS and as we move to a micro-service API driven model with InterUnity we will be developing tools/services to extend the CORE functionality and streamline workflow for DEV/Editorial
Current library of tools/services:
To create more visibility and streamline the DEV stream model we are moving towards a global board that uses EPICs for brands with filtering of streams with components/labels/fix versions
Example of a ticket for HBZ UK for the migration stream: https://thetower.atlassian.net/browse/HMIWS-6
Fix version: - Brand label
Component: - type of stream
Epic Link: - Brand Filter