Skip to content
Snippets Groups Projects

WIP: Add website ownership and responsibilities to handbook

1 unresolved thread

Please discuss and make edits to add/update website ownership and responsibilities.

Closes #1192 (closed)

cc @regisF @luke @erica @timanglade @ChadMalchow @sytses

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • username-removed-619072 resolved all discussions

    resolved all discussions

  • @SeanPackham please see this issue where we agreed on a different ownership approach: https://gitlab.com/gitlab-com/www-gitlab-com/issues/1164#note_23448639

  • added 1 commit

    • 47faa2da - Add specific Technical Writing team responsibilities

    Compare with previous version

  • mentioned in issue #1164 (closed)

  • added 1 commit

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • username-removed-619072 resolved all discussions

    resolved all discussions

  • Who owns the about.gitlab.com/downloads page? I feel developers making changes to the way GitLab is packaged and shipped are in the best position to maintain this page along with about.gitlab.com/installation rather than the Technical Writing team.

    Who owns about.gitlab.com/community?

  • added 1 commit

    Compare with previous version

  • username-removed-619072 changed title from WIP: Update handbook with the team/people responsibile for updating website content to WIP: Add website ownership and responsibilities to handbook

    changed title from WIP: Update handbook with the team/people responsibile for updating website content to WIP: Add website ownership and responsibilities to handbook

  • Luke Babb
    Luke Babb @luke started a thread on the diff
  • 34 interested and excited about GitLab's products (e.g. solution landing pages
    35 like GitLab for DevOps or Why Git and GitLab over legacy tools)
    36 - SEO webpages (these are the standalone webpages that Mitchell usually creates)
    37 - Sale enablement pages e.g. /products page, comparison pages, eventual case
    38 study or resources page
    39 - Along with the Website Product Manager, create design briefs for the Design
    40 team to turn into mockups and designs. Work with the Design team to improve
    41 and implement the design brief over a number of iterations.
    42
    43 ### Design team
    44
    45 - Create mockups and designs for design briefs given by the Website Product
    46 Manager and Product Marketing team.
    47 - Iterate on the mockups and designs until the Website Product Manger and the
    48 Product Marketing team approve.
    49 - Produce a final approved PSD for the Frontend Development team to implement.
  • @JobV @amara any comments/feedback?

  • @SeanPackham looks good to me.

  • @amara any feedback?

  • @SeanPackham no, this is fine with me. I'll see if I can resolve the merge conflicts and go ahead and merge this.

  • Amara Nwaigwe added 2 commits

    added 2 commits

    • 38cda23d - remove resources page from product marketing list
    • 1f28ab0a - delete content marketing file to resolve merge conflict

    Compare with previous version

  • closed

  • Closing since I opened a new MR since it was faster than resolving all the merge conflicts https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/5578

  • Please register or sign in to reply
    Loading