/Strategyz-Inc

Landing page for Strategyz Inc

Primary LanguageJavaScriptMIT LicenseMIT

Strategyz Inc Website Documentation

1. Project Overview

  • Project Name: Strategyz Inc Website
  • Description: This website provides a brief overview of Strategyz Inc, showcasing the company and the different services they provide, along with their contact information.
  • Technology Stack: HTML, CSS, JavaScript, React, Bootstrap
  • Live URL: https://www.strategyzinc.com/

2. Getting Started

Prerequisites

  • Git: Ensure Git is installed on your system. You can download it from here.

Installation Guide

  1. Cloning the Repository: 
    git clone https://github.com/NotSoToxic/Strategyz-Inc.git
  2. Running the Project:
    • Navigate to the repository location on your device.
    • Open the terminal and run the following commands: 
      npm install --f
npm start

Here’s how you can include the contribution guidelines in your documentation:

3. Contributing

Contribution Guidelines

To contribute to the Strategyz Inc Website, please follow these guidelines to ensure consistency and maintainability across the project.

  1. Routes Management:

    • All routes are defined in the app.js file. When adding new routes, ensure they are appropriately defined and linked within this file.

  2. Styling:

    • The project uses a global CSS file named style.css. Any and all styling changes or additions should be made within this file to maintain consistency across the website.

  3. Component Structure:

    • When adding new components, ensure they directly correspond to their respective categories.
    • Components should be placed in the relevant subdirectory that reflects their function or role within the application. For example, a service-related component should be placed in the services directory.

Contribution Process

  1. Fork the Repository: Start by forking the repository to your GitHub account.
  2. Create a New Branch: Create a new branch for your feature or bug fix.
  3. Make Your Changes: Implement your changes according to the guidelines above.
  4. Commit Your Changes: Write clear and concise commit messages.
  5. Submit a Pull Request: Submit your changes for review via a pull request.