projectdiscovery / projectdiscovery/docs

Rename "PDCP Account" to "ProjectDiscovery Account" Everywhere

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
28
Forks
62
Avg merge
1d 18h
Merged PRs (30d)
3

Description

Objective: Rename all instances of "PDCP Account" or "ProjectDiscovery Cloud Platform Account" to "ProjectDiscovery Account" across all documentation, interfaces, and communications.

Background:

We decided to rename "PDCP Account" or "ProjectDiscovery Cloud Platform Account" to "ProjectDiscovery Account" to better align with the fact that some users may use specific tools (e.g., cvemap) with their PDCP API key without engaging with the cloud platform. This change is intended to make the sign-up process more inviting and less intimidating, especially for users who may remain free users indefinitely.

Tasks:
  1. Identify Instances:

    • Conduct a thorough search to identify all instances of "PDCP Account" and "ProjectDiscovery Cloud Platform Account" across:
      • Documentation
      • User interfaces
      • Marketing materials
      • Email templates
      • Any other relevant communications
  2. Update Documentation:

    • Replace all instances of "PDCP Account" and "ProjectDiscovery Cloud Platform Account" with "ProjectDiscovery Account" in the documentation.
    • Ensure consistency in terminology throughout all documents.
  3. Update User Interfaces:

    • Update UI elements across all platforms (web, mobile, etc.) to reflect the new terminology.
    • Ensure that all buttons, labels, and messages use "ProjectDiscovery Account".
  4. Update Marketing Materials:

    • Revise marketing materials to use "ProjectDiscovery Account".
    • Ensure that all promotional content, including website banners and social media posts, reflects the change.
  5. Update Email Templates:

    • Update email templates to replace "PDCP Account" with "ProjectDiscovery Account".
    • Ensure consistency in all automated and manual communications.
  6. Review and Approve:

    • Share updates with relevant stakeholders for review and approval.
    • Incorporate any feedback and make necessary revisions.
  7. Communicate Change:

    • Inform users about the change through appropriate channels (e.g., blog post, announcement email).
    • Highlight the reasons for the change and any benefits it brings.

Acceptance Criteria:

  •  All instances of "PDCP Account" and "ProjectDiscovery Cloud Platform Account" are identified and updated to "ProjectDiscovery Account".
    
  •  Documentation, user interfaces, marketing materials, and email templates are consistent in using the new terminology.
    
  •  The change is reviewed, approved, and communicated to users effectively.
    

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by searching the repository for “PDCP Account” and “ProjectDiscovery Cloud Platform Account” to identify affected documentation. Review each match against the requested terminology, then verify that all repository instances use “ProjectDiscovery Account”; the issue also calls for review and communication beyond the repository.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.