DawnLuma Platform, Website & SEO Design
Version: 0.2
Date: 16 October 2026
Language: English
DawnLuma is intended to become an umbrella platform for financial research and analytics.
The platform is divided into three clear areas:
- Stocks
- Options
- Strategies
Each area should be independently useful while still being able to exchange data with the others.
This document covers:
- platform architecture;
- system boundaries;
- website information architecture;
- homepage design;
- public naming strategy;
- SEO structure;
- metadata;
- internal linking;
- sitemap planning;
- structured data recommendations;
- future roadmap.
DawnLuma on harrylo.com
Section titled “DawnLuma on harrylo.com”- Overview & SEO (this page)
- Stocks
- Options
- Strategies
Table of Contents
Section titled “Table of Contents”- Overview
- Design Goals
- Platform Structure
- Website Structure
- Homepage Design
- Stocks
- Options
- Strategies
- How the Three Areas Work Together
- Data and System Boundaries
- Branding Approach
- SEO Strategy
- SEO Metadata
- Internal Linking Strategy
- Structured Data
- Sitemap and Indexing
- Content Strategy
- Public vs Private Documentation
- Future Evolution
- Research Published on harrylo.com
- Related Documentation on This Site
- Summary
Overview
Section titled “Overview”The proposed DawnLuma structure is:
DawnLuma├── Stocks├── Options└── StrategiesAt a high level:
- Stocks focuses on discovering and analysing equity opportunities.
- Options focuses on analysing options-market data and options behaviour.
- Strategies combines useful outputs from both systems to research stock-and-options strategy combinations.
The three areas should remain logically separate.
This allows:
- stock-focused users to use the Stocks area independently;
- options-focused users to use the Options area independently;
- more advanced users to combine both through the Strategies area.
On this site: Until dawnluma.com launches as the public product site, architecture and research notes are published on harrylo.com. Use the Stocks, Options, and Strategies hubs to browse related articles. The Stocks area aligns with MarketLens work; the Options area is documented in Options Analysis Platform Architecture v0.1.
Design Goals
Section titled “Design Goals”Independent Modules
Section titled “Independent Modules”Each area should be independently useful.
The Options area should not depend on Stocks before it can analyse an option contract.
Likewise, the Stocks area should not require options data to perform stock screening or technical analysis.
Shared Data Where Useful
Section titled “Shared Data Where Useful”Although the systems are separate, they should be able to exchange useful information such as:
- ticker / symbol;
- market;
- timestamp;
- stock signals;
- volatility metrics;
- liquidity metrics;
- strategy-analysis results.
Loose Coupling
Section titled “Loose Coupling”One system should not depend directly on the internal database schema of another system.
Where possible, information should be exchanged through:
- APIs;
- events;
- exported analytical datasets;
- well-defined shared data contracts.
Expandable Architecture
Section titled “Expandable Architecture”The design should allow new:
- markets;
- data providers;
- analytics;
- strategy models;
- frontends;
to be added later without rewriting the whole platform.
Platform Structure
Section titled “Platform Structure”flowchart TD A["DawnLuma<br/>Financial Research & Analytics"]
A --> B[Stocks] A --> C[Options] A --> D[Strategies]
B --> B1[Stock Screening] B --> B2[Technical Analysis] B --> B3[Trend / VCP / Relative Strength]
C --> C1[Options Data] C --> C2[IV / Greeks / OI / Volume] C --> C3[Options Backtesting]
D --> D1[Combine Stock + Options Signals] D --> D2[Strategy Research] D --> D3[Opportunity Ranking]The key principle is:
Stocks and Options remain separate analytical systems, while Strategies acts as the integration and research layer.
Website Structure
Section titled “Website Structure”The main public website structure should be simple and predictable.
The paths below target the future dawnluma.com property. They are planning references, not routes on harrylo.com.
dawnluma.com/├── stocks/├── options/├── strategies/├── about/└── research/A more detailed future structure could be:
dawnluma.com/│├── stocks/│ ├── research/│ ├── architecture/│ ├── screening/│ └── backtesting/│├── options/│ ├── research/│ ├── architecture/│ ├── volatility/│ ├── unusual-activity/│ └── backtesting/│├── strategies/│ ├── research/│ ├── architecture/│ └── combined-analysis/│├── research/├── about/└── changelog/Website Information Architecture
Section titled “Website Information Architecture”flowchart TD HOME[DawnLuma Home] STOCKS["/stocks"] OPTIONS["/options"] STRATEGIES["/strategies"] RESEARCH["/research"] ABOUT["/about"]
HOME --> STOCKS HOME --> OPTIONS HOME --> STRATEGIES HOME --> RESEARCH HOME --> ABOUT
STOCKS --> SR[Stock Research] STOCKS --> SSA[Stock Architecture] STOCKS --> SS[Screening]
OPTIONS --> OR[Options Research] OPTIONS --> OA[Options Architecture] OPTIONS --> OB[Options Backtesting] OPTIONS --> OV[Volatility Research]
STRATEGIES --> STR[Strategy Research] STRATEGIES --> STA[Strategy Architecture] STRATEGIES --> CA[Combined Analysis]
RESEARCH --> ARTICLES[Research Articles]Homepage Design
Section titled “Homepage Design”The homepage should explain DawnLuma in a few seconds.
The visitor should immediately understand:
- what DawnLuma is;
- what the three areas are;
- where to go next.
Recommended Homepage Hero
Section titled “Recommended Homepage Hero”Headline
Section titled “Headline”Financial Research & Analytics
Supporting Copy
Section titled “Supporting Copy”DawnLuma is an independent research platform for exploring stocks, options, and trading strategies through data, analytics, and backtesting.
Primary Navigation
Section titled “Primary Navigation”StocksOptionsStrategiesResearchAboutPrimary CTA
Section titled “Primary CTA”Explore Research
Secondary CTA
Section titled “Secondary CTA”View Architecture
Homepage Section: Three Core Areas
Section titled “Homepage Section: Three Core Areas”Stocks
Section titled “Stocks”Find and analyse stock opportunities
Research market trends, relative strength, VCP structures, breakouts, volume behaviour, and other technical signals.
Suggested button:
Explore Stocks
Options
Section titled “Options”Understand the options market
Analyse implied volatility, Greeks, open interest, volume, liquidity, volatility skew, and historical strategy behaviour.
Suggested button:
Explore Options
Strategies
Section titled “Strategies”Connect stock and options research
Combine stock signals with options-market conditions to compare strategy structures and study historical outcomes.
Suggested button:
Explore Strategies
Homepage Section: How DawnLuma Works
Section titled “Homepage Section: How DawnLuma Works”flowchart LR A[Market Data] --> B[Stocks Research]
A --> C[Options Research]
B --> D[Strategies] C --> D
D --> E["Combined Research & Backtesting"]Suggested copy:
DawnLuma keeps stock analysis and options analysis independent, then connects them through a separate strategy research layer. This makes each area useful on its own while allowing deeper cross-market research when needed.
Homepage Section: Research Philosophy
Section titled “Homepage Section: Research Philosophy”Suggested copy:
DawnLuma is built around reproducible research rather than trade tips.
The goal is to understand market behaviour, test assumptions, and compare strategies using transparent data and repeatable analysis.
This wording is preferable to language such as:
- “best trades”;
- “guaranteed opportunities”;
- “winning strategies”;
- “recommended trades”.
Homepage Section: Current Status
Section titled “Homepage Section: Current Status”Suggested copy:
DawnLuma is currently under active research and development.
Architecture, market-data studies, backtesting experiments, and technical notes are published as the platform evolves.
Suggested CTA:
Follow the Research
Stocks
Section titled “Stocks”The Stocks area is responsible for equity research and opportunity discovery.
Possible capabilities include:
- trend analysis;
- moving averages;
- relative strength;
- VCP detection;
- breakout / pivot detection;
- volume analysis;
- support and resistance;
- volatility;
- stock screening;
- candidate ranking;
- technical-analysis signals.
A simplified flow:
flowchart LR A[Market Data] --> B[Stock Analysis] --> C[Signals] --> D[Stock Candidates]Possible output:
Symbol: AAPLTrend: StrongRelative Strength: 92VCP: YesNear Pivot: YesVolume Pattern: PositiveThese results may later be passed to the Strategies area, but the Stocks system should remain fully usable by itself.
Options
Section titled “Options”The Options area should focus only on options-market analysis.
For now, public articles and prototypes should use the neutral working name:
Options Analysis Platform
This avoids prematurely locking the project into a final product name.
Possible capabilities include:
Market Data
Section titled “Market Data”- option chains;
- bid / ask;
- trades;
- volume;
- open interest;
- expiry;
- strike;
- contract multiplier.
Analytics
Section titled “Analytics”- implied volatility;
- IV Rank;
- IV Percentile;
- Delta;
- Gamma;
- Theta;
- Vega;
- volatility skew;
- term structure;
- liquidity analysis;
- abnormal option volume;
- OI changes.
Backtesting
Section titled “Backtesting”- Long Call;
- Long Put;
- Bull Call Spread;
- Bull Put Spread;
- Cash-Secured Put;
- Covered Call;
- Iron Condor;
- other configurable strategies.
Simplified architecture:
flowchart LR A[Options Market Data] --> B[Data Normalisation] --> C[Options Analytics] --> D[Backtest Engine] --> E[Research Output]The Options area should be able to analyse a user-selected symbol directly without requiring the Stocks system to select it first.
Strategies
Section titled “Strategies”The Strategies area is the integration layer.
Its purpose is not to replace Stocks or Options.
Instead, it takes useful analytical results from both systems and performs higher-level research.
flowchart LR A[Stocks<br/>Trend / VCP / RS] --> C[Strategies]
B[Options<br/>IV / OI / Liquidity] --> C
C --> D[Combined Analysis] D --> E[Strategy Research] E --> F[Opportunity Ranking]Example research flow:
Stock:Strong bullish trendVCP breakoutRelative Strength = 92
+
Options:Good liquidityIV Percentile = 68Suitable 30-45 DTE contracts
↓
Strategy Research:Long CallBull Call SpreadBull Put SpreadThe purpose is to compare and analyse possible strategy structures rather than force all logic into one application.
How the Three Areas Work Together
Section titled “How the Three Areas Work Together”flowchart LR A[Stocks] -->|Stock signals| C[Strategies]
B[Options] -->|Options analytics| C
C -->|Research context| A C -->|Research context| BStocks to Options
Section titled “Stocks to Options”Stocks may identify:
- strong trends;
- VCP patterns;
- breakouts;
- high relative strength;
- unusual price or volume behaviour.
A ticker can then be passed to Options for deeper options analysis.
Options to Stocks
Section titled “Options to Stocks”Options may identify:
- abnormal option volume;
- unusual OI changes;
- volatility spikes;
- unusual skew.
The ticker can then be passed to Stocks for underlying technical analysis.
Strategies
Section titled “Strategies”The Strategies layer can combine the two outputs and research questions such as:
- Is there a strong underlying stock setup?
- Is the options market sufficiently liquid?
- Is implied volatility relatively high or low?
- Which strategy structures are worth comparing?
- What historical behaviour has occurred under similar conditions?
Data and System Boundaries
Section titled “Data and System Boundaries”Each system should own its own internal data.
flowchart TD A[(Stocks Database)] B[(Options Database)] C[(Strategies Database)]
A --> D[Stocks API / Data Contract] B --> E[Options API / Data Contract]
D --> F[Strategies Engine] E --> F
F --> CThe Strategies system should preferably not directly query the internal production tables of Stocks or Options.
This helps avoid:
- tight coupling;
- accidental schema dependencies;
- difficult migrations;
- unclear ownership of calculated values.
Instead, each system should expose a stable interface.
Branding Approach
Section titled “Branding Approach”DawnLuma should remain the umbrella brand.
For the early research and prototype stage:
DawnLuma├── Stocks├── Options└── StrategiesPublic technical articles can use descriptive names such as:
- Stock Analysis Platform
- Options Analysis Platform
- Strategy Research Platform
This allows the technical architecture to mature before choosing permanent product names.
It also reduces the risk of becoming attached to a name that later conflicts with:
- another software product;
- an existing domain;
- an existing trade mark;
- an established financial brand.
A final naming decision can be made when the products are closer to public release.
SEO Strategy
Section titled “SEO Strategy”The SEO goal should be broader than ranking for the brand name DawnLuma.
The site should build authority around three topic clusters:
Stock AnalysisOptions AnalysisTrading Strategy ResearchEach main section should become a topic hub.
SEO Topic Clusters
Section titled “SEO Topic Clusters”Stocks Cluster
Section titled “Stocks Cluster”Primary topics:
- stock analysis;
- technical analysis;
- VCP pattern;
- relative strength;
- breakout analysis;
- stock screening;
- stock backtesting.
Possible article examples:
How VCP Detection WorksRelative Strength Scoring ExplainedDesigning a Stock Screening EngineBacktesting Breakout SignalsOptions Cluster
Section titled “Options Cluster”Primary topics:
- options analysis;
- options data;
- implied volatility;
- IV Rank;
- IV Percentile;
- options Greeks;
- open interest;
- unusual options activity;
- options backtesting;
- bull call spread;
- bull put spread.
Possible article examples:
Designing an Options Analysis PlatformHow Historical Options Data Is StructuredIV Rank vs IV PercentileBacktesting a Long Call StrategyBacktesting Bull Put SpreadsUnderstanding Historical Bid/Ask DataStrategies Cluster
Section titled “Strategies Cluster”Primary topics:
- trading strategy research;
- stock and options analysis;
- strategy backtesting;
- risk/reward analysis;
- market-condition analysis.
Possible article examples:
Combining Stock Signals with Options DataChoosing Option Structures for Different Volatility EnvironmentsDesigning a Strategy Research EngineSignal Backtesting vs Strategy BacktestingCurrent harrylo.com cluster mapping (illustrative)
Section titled “Current harrylo.com cluster mapping (illustrative)”These existing articles support the three clusters while dawnluma.com hubs are still in planning:
| Cluster | Examples on harrylo.com |
|---|---|
| Stocks | MarketLens momentum models, Momentum & trend formulas |
| Options | Options hub, Options Analysis Platform Architecture, Options quantitative programming guide, Market data provider research |
| Strategies | Strategies hub, architecture §20, MarketLens momentum models |
SEO Metadata
Section titled “SEO Metadata”Each page should have unique metadata.
Recommended frontmatter pattern:
---title: "Designing an Options Analysis Platform"description: "A technical exploration of data ingestion, options analytics, backtesting, and market-independent architecture for an options research platform."pubDate: 2026-10-16updatedDate: 2026-10-16version: "0.1"draft: false---If your Astro/Starlight setup supports these fields, additional metadata may include:
canonical: "https://dawnluma.com/options/architecture/"ogTitle: "Designing an Options Analysis Platform"ogDescription: "Architecture, market data, analytics, and backtesting design for an options research platform."Do not add unsupported custom fields blindly if the site template does not consume them.
On harrylo.com, Starlight articles use title, description, and optional sidebar frontmatter. Canonical URLs, hreflang, Open Graph, and BlogPosting JSON-LD are generated at build time for this site (https://harrylo.com). Use dawnluma.com canonicals only when content is published on that domain.
Recommended Homepage SEO
Section titled “Recommended Homepage SEO”SEO Title
Section titled “SEO Title”DawnLuma — Stock, Options & Strategy Research
Alternative:
DawnLuma — Financial Research & Analytics
Meta Description
Section titled “Meta Description”DawnLuma explores stock analysis, options analytics, trading strategies, market data, and backtesting through independent technical research.
Suggested Canonical
Section titled “Suggested Canonical”https://dawnluma.com/Stocks Page SEO
Section titled “Stocks Page SEO”Stock Analysis & Research | DawnLuma
Description
Section titled “Description”Explore stock screening, technical analysis, VCP patterns, relative strength, breakout research, and stock backtesting at DawnLuma.
Canonical
Section titled “Canonical”https://dawnluma.com/stocks/Options Page SEO
Section titled “Options Page SEO”Options Analysis & Backtesting | DawnLuma
Description
Section titled “Description”Explore options data, implied volatility, Greeks, open interest, unusual activity, liquidity, and options strategy backtesting.
Canonical
Section titled “Canonical”https://dawnluma.com/options/Strategies Page SEO
Section titled “Strategies Page SEO”Strategy Research & Backtesting | DawnLuma
Description
Section titled “Description”Explore research that combines stock signals, options analytics, market conditions, and historical strategy backtesting.
Canonical
Section titled “Canonical”https://dawnluma.com/strategies/Internal Linking Strategy
Section titled “Internal Linking Strategy”Internal linking should connect related research without forcing all content into one page.
Example:
flowchart TD A[Options Analysis Platform] --> B[Historical Options Data] --> C[IV Rank vs IV Percentile] --> D[Long Call Backtesting] --> E[Bull Call Spread Backtesting]
F[VCP Research] --> G[Stock Signal] --> H[Strategy Research]
D --> H G --> HUseful internal-link patterns:
From Stocks articles
Section titled “From Stocks articles”Link to:
- relevant Strategy research;
- related technical-analysis concepts;
- related backtests.
From Options articles
Section titled “From Options articles”Link to:
- IV research;
- historical-data architecture;
- options backtesting;
- Strategies pages where the signal is combined with stock analysis.
From Strategies articles
Section titled “From Strategies articles”Link back to:
- the original stock signal;
- the options-market metric;
- the individual strategy backtest.
This creates clear topic relationships for both users and search engines.
Structured Data
Section titled “Structured Data”Structured data should be added only where it accurately describes the page.
Potential schema types:
WebSiteOrganizationArticleTechArticleBreadcrumbList
For research and architecture articles, TechArticle or Article may be appropriate depending on the content.
Conceptual JSON-LD example:
{ "@context": "https://schema.org", "@type": "TechArticle", "headline": "Designing an Options Analysis Platform", "description": "A technical exploration of options data, analytics, and backtesting architecture.", "datePublished": "2026-10-16", "dateModified": "2026-10-16", "author": { "@type": "Person", "name": "Harry" }, "publisher": { "@type": "Organization", "name": "DawnLuma" }}The implementation should generate JSON-LD from page metadata where possible rather than maintaining duplicated values manually.
Sitemap and Indexing
Section titled “Sitemap and Indexing”The sitemap should contain public research pages only.
Example:
/ /stocks/ /options/ /strategies/ /research/ /about/
/stocks/architecture/ /stocks/vcp/ /stocks/relative-strength/
/options/architecture/ /options/backtesting/ /options/implied-volatility/
/strategies/architecture/ /strategies/combined-analysis/Private documents should not appear in:
- the sitemap;
- public navigation;
- RSS feeds;
- search indexes.
If private documentation exists, it should be protected by real access control rather than merely hidden from navigation.
robots.txt Considerations
Section titled “robots.txt Considerations”Public areas should remain crawlable.
Conceptually:
User-agent: *Allow: /
Sitemap: https://dawnluma.com/sitemap-index.xmlPrivate content should be protected through authentication or access-control infrastructure rather than relying on robots.txt.
Content Strategy
Section titled “Content Strategy”DawnLuma should publish technical research rather than promotional trading claims.
Recommended article categories:
ArchitectureMarket DataStock ResearchOptions ResearchBacktestingStrategiesEngineering NotesResearch NotesRecommended Content Style
Section titled “Recommended Content Style”Prefer:
We tested how this signal behaved historically.
Rather than:
This signal predicts the next winning trade.
Prefer:
This strategy had the following historical characteristics under these assumptions.
Rather than:
This is the best strategy.
Prefer:
The backtest assumes execution at the ask for buys and bid for sells.
Rather than:
The strategy returned X%.
The assumptions matter as much as the result.
Public vs Private Documentation
Section titled “Public vs Private Documentation”The public DawnLuma site should explain:
- what the system does;
- why the architecture is designed this way;
- high-level workflows;
- research methodology;
- general findings.
Private documentation may contain:
- proprietary scoring formulas;
- detailed weighting;
- unreleased algorithms;
- strategy-selection logic;
- internal implementation details;
- credentials;
- licensed raw data;
- commercial agreements;
- private partner discussions.
A useful rule is:
Publish the What and Why; protect the proprietary How.
Future Evolution
Section titled “Future Evolution”Phase 1 — Independent Research Systems
Section titled “Phase 1 — Independent Research Systems”StocksOptionsBuild each analytical system independently.
Phase 2 — Standard Data Contracts
Section titled “Phase 2 — Standard Data Contracts”Define common fields such as:
marketsymboltimestampsignalTypescoresourcePhase 3 — Strategies Layer
Section titled “Phase 3 — Strategies Layer”Create a separate engine that consumes outputs from both systems.
Phase 4 — Combined Backtesting
Section titled “Phase 4 — Combined Backtesting”Research combinations such as:
Stock signal+Options condition+Strategy definition=Historical outcomePhase 5 — Multi-Market Support
Section titled “Phase 5 — Multi-Market Support”The same architectural principles can later support:
- United States;
- Hong Kong;
- other markets.
Market-specific data adapters and rules should remain separate from the core analytical logic.
Phase 6 — Public Product Naming
Section titled “Phase 6 — Public Product Naming”Once the products are mature:
- check domains;
- check relevant trade marks;
- check naming conflicts;
- choose final product names;
- update navigation and metadata accordingly.
Until then, generic labels such as Stocks, Options, and Strategies remain sufficient.
Research Published on harrylo.com
Section titled “Research Published on harrylo.com”While DawnLuma product pages (/stocks/, /options/, /strategies/) are planned for dawnluma.com, reproducible research is published here:
- Platform & SEO (this page) — umbrella architecture and SEO plan (v0.2)
- Options — Options hub, Options Analysis Platform Architecture
- Market data — Market data provider research
- Stocks / momentum — MarketLens momentum models
- Learning path — AI Engineer roadmap (MarketLens)
When dawnluma.com goes live, migrate or cross-link hubs without breaking harrylo.com URLs where articles remain the canonical research copies.
Related Documentation on This Site
Section titled “Related Documentation on This Site”- Stocks hub
- Options hub
- Strategies hub
- Options Analysis Platform Architecture v0.1
- Market Data Provider Research
- MarketLens Momentum Models and Strategies
- Momentum and Trend — Academic Analysis & Formulas
- Options Terms Complete Guide
- AI Engineer Learning Roadmap (MarketLens)
Summary
Section titled “Summary”The proposed DawnLuma structure is:
DawnLuma│├── Stocks│ └── Stock research and opportunity discovery│├── Options│ └── Options analytics and backtesting│└── Strategies └── Combined stock + options strategy researchThe website should mirror the same structure:
dawnluma.com/├── stocks/├── options/└── strategies/The homepage should position DawnLuma as:
Financial Research & Analytics
The most important design principles are:
- Keep Stocks and Options independently useful.
- Connect them through a separate Strategies layer.
- Keep data providers separate from analytical logic.
- Publish reproducible research rather than trading promises.
- Use DawnLuma as the umbrella brand while product names remain flexible.
- Build SEO around topic clusters rather than only the DawnLuma brand name.
- Keep public architecture and private proprietary implementation clearly separated.
This creates a clean foundation for DawnLuma to grow from a technical research blog into a broader financial analytics platform over time.