terminalGETTING_STARTED_v1.0
Introduction
Layero is a marketplace of precision-built Next.js themes designed for high-performance websites. Each theme ships production-ready — TypeScript, Tailwind CSS, SEO and CMS connectors included.
codeSTART (Theme Only) is for
- checkDevelopers
- checkFreelancers
- checkAgencies
- checkTechnical DIY users
support_agentNot technical?
No problem. Our managed plans handle everything — from installation to launch and editing.
PRO Plan — we deploy for you
MAX Plan — deploy + editable interface
ULTRA — fully tailored solution
01. Purchase
Choose a theme and select your plan — START, PRO, or MAX.
02. Configure
Clone the repo, install dependencies, and set your environment variables in .env.local.
03. Customise
Edit content in the data/ folder, swap images, and adjust the Tailwind theme tokens.
04. Deploy
Push to Vercel, Netlify, or upload a static build to your Apache / cPanel hosting.
REQUIREMENTS
Node.js ≥ 18.17, npm ≥ 9 or pnpm ≥ 8. Git is required to clone and track your project.
Installation
After purchasing, you will receive download access to your theme's source repository. Follow the steps below to initialise your local environment.
Terminalbash
# Clone your purchased theme
git clone https://github.com/sitelift/your-theme.git
# Enter the project directory
cd your-theme
# Install dependencies
npm install
# Copy the environment template
cp .env.example .env.local
# Start the dev server
npm run devOpen http://localhost:3000 to see your theme running locally.
ENVIRONMENT VARIABLES
Edit .env.local with your credentials before running:
# Site config
NEXT_PUBLIC_SITE_URL=https://yourdomain.com
NEXT_PUBLIC_SITE_NAME="Your Business"
# CMS (optional)
CONTENTFUL_SPACE_ID=xxxx
CONTENTFUL_ACCESS_TOKEN=xxxx
# Stripe (optional)
STRIPE_SECRET_KEY=sk_live_xxxx
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_live_xxxx
Edit Content
All user-facing content is split into focused TypeScript files inside the data/ folder at the project root. You should not need to touch individual page files for basic content changes.
| File | What it controls |
|---|
data/site.ts | Business name, phone, email, address, hours, stats |
data/services.ts | Services / practice areas / menu items |
data/team.ts | Team member profiles |
data/testimonials.ts | Testimonials (where applicable) |
data/navigation.ts | Nav links |
Refer to your theme's own README for the complete list of data files and their exact structure — it varies per theme.
data/site.tsTypeScript
export const siteConfig = {
name: "Your Business",
tagline: "Your memorable tagline",
phone: "+1 (555) 000-0000",
email: "hello@yourdomain.com",
address: "123 Main St, City, Country",
};After saving the file, the dev server hot-reloads instantly. In production, a new build is required to apply changes.
How content updates work
The update process depends on where your site is hosted. Here is what to expect on each platform.
- 01Edit the relevant files in your theme's data/ folder
- 02Commit and push to your repo
- 03Vercel rebuilds and redeploys automatically
Fastest workflow — changes are live in under a minute.
- 01Edit the relevant files in your theme's data/ folder
- 02Commit and push to your repo
- 03Netlify rebuilds and redeploys automatically
Same as Vercel — push to deploy.
- 01Edit the relevant files in your theme's data/ folder locally
- 02Run npm run build to generate new static files
- 03Upload the new out/ folder via FTP
Requires access to source code and an FTP client each time.
WANT TO SKIP THE REBUILD?
Upgrade to the MAX plan and edit your content through a visual interface — no code, no terminal, no FTP required.
