Skip to main content
Project Status: ProyectoWeb is currently in the planning stage. This guide provides general web development environment setup guidance for when development begins. No implementation code exists yet.

Current Repository Status

The source repository at ~/workspace/source/ currently contains only:
  • README.md (basic readme file)
  • Documentos/Proyecto desarrollo web 2026-10.pdf (project specification)
  • Documentos/HOLA ESTA ES UNA PRUEBA.txt (empty file)
There is no package.json, no source code, and no development environment to set up yet.

General Development Prerequisites

When development begins, you’ll typically need the following tools:

Version Control

Git for version control and collaboration

Code Editor

VS Code, WebStorm, Sublime Text, or your preferred IDE

Programming Language

Based on project requirements (Node.js, Python, etc.)

Package Manager

npm, yarn, pnpm, or equivalent for your stack

Typical Setup Process

When the project moves to the implementation phase, a typical setup process would include:
1

Clone the Repository

Once the project repository is initialized:
git clone <repository-url>
cd ProyectoWeb
Make sure you have proper access credentials and SSH keys configured.
2

Install Dependencies

After the project includes a dependency file:
npm install
The actual commands will depend on the chosen technology stack and package manager.
3

Environment Configuration

Configure environment variables as specified in project documentation:
cp .env.example .env.local
Never commit .env files or files containing sensitive credentials to version control.
Typical environment variables might include:
.env.example
# Application Settings
NODE_ENV=development
PORT=3000

# Database (example)
DATABASE_URL=your_database_connection_string

# API Keys (example)
API_KEY=your_api_key_here
4

Database Setup (if applicable)

If the project uses a database, you’ll need to:
  • Install the database system
  • Create the database
  • Run migrations
  • Optionally seed initial data
# Example commands (actual commands depend on stack)
npm run db:create
npm run db:migrate
npm run db:seed
5

Start Development Server

Launch the development server:
npm run dev
# or yarn dev, pnpm dev, etc.
Development servers typically include hot-reload functionality for rapid development.

Common Development Tools

Code Editor Extensions

Enhance your development experience with useful extensions:
General productivity:
  • Linter - Code quality and style checking
  • Formatter - Consistent code formatting (Prettier, etc.)
  • Git Integration - Enhanced Git functionality
  • Path Autocomplete - File path assistance
  • Bracket Colorizer - Matching brackets visualization
Depending on your stack:
  • JavaScript/TypeScript language support
  • Python extensions (if using Python)
  • HTML/CSS/JavaScript snippets
  • Framework-specific tools (React, Vue, Angular)
  • Database integration tools
Optional but helpful:
  • Better Comments - Styled code comments
  • TODO Highlight - Track TODO and FIXME comments
  • Error Lens - Inline error messages
  • Import Cost - Display package sizes
  • Live Share - Collaborative coding

Browser DevTools

Install browser extensions for development:
  • React Developer Tools - For React applications
  • Vue.js devtools - For Vue.js applications
  • Redux DevTools - For Redux state management
  • Lighthouse - Performance and accessibility auditing
  • JSON Formatter - Better JSON viewing

Code Editor Configuration

When the project begins, you might create workspace settings:
.vscode/settings.json
{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
  "files.exclude": {
    "**/node_modules": true,
    "**/.git": true
  }
}
The actual configuration will depend on the chosen technology stack and team preferences.

Platform-Specific Setup

Windows

macOS

# Install Homebrew (package manager)
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Install Git (usually pre-installed)
brew install git

# Install Node.js (example)
brew install node

# Or use nvm for version management
brew install nvm

Linux

# Update package manager
sudo apt update

# Install Git
sudo apt install git

# Install Node.js (example)
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt install nodejs

# Or use nvm for version management
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

Troubleshooting Common Issues

If the default port is occupied:
# Find process using the port (example: port 3000)
lsof -ti:3000 | xargs kill -9

# Or specify a different port
PORT=3001 npm run dev
If you encounter package installation problems:
# Clear package manager cache
npm cache clean --force
# or
yarn cache clean

# Remove node_modules and lock file
rm -rf node_modules package-lock.json

# Reinstall
npm install
On Unix-like systems, avoid using sudo with npm:
# Fix npm permissions (if needed)
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
Ensure:
  • Environment file has correct name (.env, .env.local, etc.)
  • File is in the correct directory (usually project root)
  • Development server is restarted after changes
  • Variables follow framework-specific naming conventions

Best Practices

Version Control

  • Commit frequently with clear messages
  • Use branches for features
  • Keep main branch stable
  • Review code before merging

Code Organization

  • Follow project structure conventions
  • Keep files focused and small
  • Use meaningful names
  • Document complex logic

Security

  • Never commit secrets
  • Use environment variables
  • Keep dependencies updated
  • Review security advisories

Performance

  • Optimize during development
  • Test with realistic data
  • Monitor build times
  • Profile when needed

When Development Begins

1

Review Project Specification

Start by thoroughly reviewing the project specification in Documentos/Proyecto desarrollo web 2026-10.pdf
2

Set Up Repository

Initialize the repository with:
  • Project structure
  • Configuration files
  • Development dependencies
  • Documentation
3

Configure Development Environment

Set up:
  • Linting and formatting tools
  • Testing framework
  • Build tools
  • CI/CD pipeline
4

Begin Implementation

Follow the development guidelines and start building according to the specification

Next Steps

Development Guidelines

Learn about coding standards and best practices

Project Specification

Review the project specification document reference
When the project moves to implementation, this guide will be updated with specific setup instructions based on the chosen technology stack.

Build docs developers (and LLMs) love