Handbook - publishing Fleet content#6051
Conversation
Added a table for Digital Experience service requests.
Updated text
Changes "with the contributor" to "to the contributor".
|
@mikermcneil I've pushed the .sailsrc up in my last text change commit 😩 |
|
@mikermcneil, is it as simple as hitting 'delete'? |
|
|
||
| ## Request Digital Experience services | ||
|
|
||
| The following table details how to request reviews and art assets from the Digital Experience team. |
There was a problem hiding this comment.
Let's make this about how to publish content or changes to content, rather than how to request reviews.
There was a problem hiding this comment.
@mikermcneil, are you referring to the wording of this intro only, or the entire table?
There was a problem hiding this comment.
@mike-j-thomas Both. This isn't a menu of digital experience services, it is a "how to" of how anyone can publish each type of content. Digital Experience doesn't write the content, it finishes it. (And gates it, as needed.) Digital Experience's job is to make sure that all content meets brand standards.
This should tell everyone exactly what they need to do to get content published, and the maximum turnaround time they can expect before it is both published and reviewed/finished by Digital Experience.
I don't think this is where we tell people how to request artwork, that is a separate thing.
There was a problem hiding this comment.
@mike-j-thomas i.e. Tim doesn't say "I want to publish some ad artwork today". He says "I want to run an ad campaign".
I would also differentiate between "New handbook page" and "Handbook edits", since I think a new handbook page is gated by digital experience, whereas handbook edits are edited post facto.
There was a problem hiding this comment.
@mikermcneil, ok. I'll have another go on Monday and remove the artwork/service references.
It's clear now that I don't exactly understand what this table should include.
It would be helpful to see an example of one row. I can't find anything in the wild to model it off.
There was a problem hiding this comment.
The screenshots above include an example row about how to publish a tweet.
There was a problem hiding this comment.
@mikermcneil - ah, I'm sorry. I thought I'd bookmarked that thread to read, but I lost it in Slack. Thanks again for sharing it.
There was a problem hiding this comment.
@mikermcneil, I committed another attempt, ready for review.
|
@eashaw Can you help @mike-j-thomas resolve the merge conflict here? |
Updated table and introduction.
text change
Omitted changes that were accidentally pushed.
mikermcneil
left a comment
There was a problem hiding this comment.
Lovely start, @mike-j-thomas! Up to you and your team to take it from here and evolve these processes based on what works.
Let me know when there's any way I can help.
|
Editor pass completed on: |





Add information for Digital Experience service requests.
Checklist for submitter
If some of the following don't apply, delete the relevant line.