-
Notifications
You must be signed in to change notification settings - Fork 42
2020 website content publishing process
JennySanchez edited this page Aug 3, 2020
·
17 revisions
This is the standard publishing process for the IBM.com Library website
- Estimated # of sprints: 2 per website page
- Most of the heavy lifting will be in collating, writing, and asset production.
- Reviews will depend on availability of designers and stakeholders.
- The "Sprint order" is not a delivery commitment but rather a best practice. The timeline is subject to change based on the complexity of the task.
Task | Stage | Tool | Action | Dependencies | Contributor/Task owner | Sprint & LOE |
---|---|---|---|---|---|---|
Initial research | Research/Investigate | Ideation board | Identify adopter pain points, ideate, Identify proper IA placement, and identify proper level of details and fidelity | Adopter needs and pain points | Assignee/Content creator | Ideation |
Publishing agreement | Planning | Ideation board | Get the content needs agreed by the DDS leaders and create proper Epic or Task issue on Git for prioritization | — | Proposed by the website stream lead and approved by the DDS leaders | Planning |
Collect content documentation | Research | Agile board | Gather designs and specs, gather content guidance (and/or content model), gather developer notes, and gather research notes | Designer, content strategist, developer, and researcher of pattern must be available to share documentation and relevant assets. contributor may need to write documentation | Task assignee/Content creator | 1 (week one) |
Fill in the content template | Creation | Agile board and Box document | Take all documentation and assign to pattern content template and add new subsections as per pattern needs | See above | Task assignee/Content creator | 1 (week one) |
Produce supporting assets | Creation | Agile board, Sketch app, or Photoshop | Do's and don'ts, visuals to support each sections and/or subsections of written guidelines, and Video/diagram/specs | Contributor to share [draft] assets and work with the Visual/UX Designer to ensure the assets are accurate | Task assignee/Content creator | 1 (week two)–2 (week one) |
Create draft design mockup | Creation | Agile board or Sketch app | Create mockup of page with content and visuals and share mockup with all contributors for feedback | Availability of all contributors | Task assignee/Content creator or Visual/UX Designer | 2 (week one) |
Share with the team to get feedback | Review | — | — | — | — | 2 (week one) |
Update content or design | Creation | Agile board or Sketch app | — | All contributors have reviewed | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
Share with Carbon, IDL, ibm.com adopters | Review | — | Gather feedback from teams on content and page design | — | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
Finalize documentation and update copy | Creation | Agile board or Sketch app | Add any additional Carbon comments, ensure language and style is consistent and updated, and writer review and proof | Availability of Carbon | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
(Optional0 Review with IDL governance board | Review | — | Share/present pattern to IDL board for approval | — | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
Finalize content and documentation | Creation | Agile board or Sketch app | Add any additional Carbon Board comments, ensure language and style is consistent and updated, writer review and proof, and review with DDS leaders for approval | — | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
Create a new page and publish on website | Publish | Agile board and Github (markdowns and html code) | Publishing with markdown by Visual/UX Designer, publishing with code by a Developer (as needed), PR preview link is ready, and PR review request set | Final pattern documentation has been reviewed and approved, patterns and guidelines have been approved by Carbon review board, and all assets must be made available to publishers | Task assignee/Content creator or Visual/UX Designer | 2 (week two) |
Website page go live | Release | Agile board and Github | QA via the preview link and approve the PR and merge the PR to master branch | Jenkins built | — | 2 (week two) |
Get adopter feedback | Review | Ideation board and Cupcake website | Update roadmap / GitHub, Slack communications, spot opportunity and make plan for improvement,and Catalog/consolidate feedback | — | Task assignee/Content creator or Visual/UX Designer | Iteration starts |
Publishing guidelines (6)
Layout component (37)
- CTA block
- CTA section
- Callout media
- Callout quote
- Callout
- Card group
- Card section carousel
- Card section images
- Card section offset
- Card section simple
- Card section
- Content block cards
- Content block horizontal
- Content block media
- Content block mixed groups
- Content block segmented
- Content block simple
- Content block
- Content group banner
- Content group cards
- Content group pictograms
- Content group simple
- Content group
- Content item horizontal
- Content item
- Content section
- Dotcom shell
- Feature section
- Lead space block
- Lead space search
- Lead space
- Link list section
- Logo grid
- Table of contents
- Tabs extended media
- Tabs extended
- Universal banner
Service (3)
UI component (34)
- Back to top
- Background media
- Button group
- CTA
- Card in card
- Card link
- Card
- Carousel
- Expressive modal
- Feature card
- Filter group
- Filter panel
- Footer
- Image with caption
- Image
- Input select
- Leaving ibm
- Lightbox media viewer
- Link list
- Link with icon
- Locale modal
- Masthead L0
- Masthead L1
- Masthead account
- Masthead mobile
- Masthead navigation
- Masthead
- Mega menu
- Pictogram item
- Quote
- Search typeahead
- Tag group
- Tag link
- Video