Standard Of Process for Pre-development

Here’s a list of points outlining the standard process for Pre-development to start with the new project:

Requirement Gathering

  • Ask relevant questions
  • Define project goals, objectives
  • Define Scope*

Identify stakeholders.

  • Responsibilities

Environment Setup

  • B2B
    • Client Server
  • B2C
    • Actual Server
  • Based on Request
    • SiteProof

Request for Credentials:(Redevelopment )

  • WordPress Admin
    • Create a new user (B2B)
    • Existing Credentials (B2B/B2C)
  • Hosting Account:
    • Git Access
    • SSH/SFTP including keys
    • Control Panel Access (e.g., cPanel): (For database and file management)
  • Domain Register Credentials (Optional):
    • Delegate Access First Priority
    • Registrar Login
    • Backup Authentication Codes
  • API Keys and Tokens
    • Third-Party Services: (Any relevant API keys for integrations)
      1. Login or
      2. Token/Keys
  • Analytics and Webmaster Tools(if required):
    • Number of events
    • Google Analytics Access, Google Search Console/Bing Webmaster Tools. (Read Access)
  • Payment Gateway Credentials
    • Discussion on using our Sandbox
    • Developer Access

Theme and Plugin Licenses

  • License Keys: (For premium themes and plugins)

Hosting Infrastructure(Optional)

  • Determine hosting requirements and server configuration that supports WordPress architecture.

Plugin/WP Version Selection

  • Select the latest and most stable versions of WordPress, PHP, and other required technologies.
  • WordPress Installation and Configuration with standard boiler plate of ZealousWeb or from client

Theme Selection or Development

  • Decide the project requirement to use a pre-built theme or develop a custom one.
    • Light weight theme is preferred for performance optimization
  • If you are using a pre-built theme, check its suitability and options for customization.
  • If developing a custom theme, establish design requirements and implement them using HTML, CSS, jQuery/JavaScript, and PHP.

Plugin Selection or Development

  • Identify required functionalities not provided by the theme.Search and evaluate existing plugins from the WordPress Plugin Repository.

Backup and Disaster Recovery

  • Via Git First Priority
  • Or need to be discuss with System Admin/ Server Administrator
  • Set up regular backups of the WordPress site, including files and database using plugin or any other solution.

Documentation

  • Phpmyinfo link should be provided


Following these technical points outline the key steps involved in the pre-development phase of a WordPress project.

Pre-development Checklist

Project Initialization

  • Define project goals, objectives, and scope.
  • Identify stakeholders and assign responsibilities.

Environment and Credentials

  • Set up the development environment (B2B Client Server, B2C Actual Server).
  • Ensure SiteProof is in place.
  • Obtain necessary credentials:
    • WordPress Admin (Create new user if B2B, obtain existing credentials if B2C).
    • Hosting Account (Git access, SSH/SFTP keys, Control Panel access, optional domain registrar access).
    • API Keys and Tokens (Third-party services, analytics, webmaster tools).
    • Payment Gateway (Sandbox discussion, developer access).
    • Theme and Plugin Licenses.

Technical Setup

  • Select and install the latest stable versions of WordPress, PHP, and other required technologies.
  • Configure WordPress with the standard boilerplate of ZealousWeb or from the client.
  • Determine hosting requirements and server configuration (optional).

Theme and Plugin Setup

  • Decide on theme (pre-built or custom):
    • For pre-built themes, check suitability and customization options.
    • For custom themes, establish design requirements and implement using HTML, CSS, jQuery/JavaScript, and PHP.
    • Prefer a lightweight theme for performance optimization.
  • Identify and evaluate necessary plugins from the WordPress Plugin Repository.

Backup and Documentation

  • Set up regular backups (preferably via Git, discuss other solutions with System Admin if needed).
  • Provide phpmyinfo link for documentation.