Plan the experience before building more pages.

Why planning matters

A website is not simply a collection of attractive pages. It is an experience designed for a particular audience, purpose, and set of intended actions. Before writing code, we should decide what kind of website we are building, why someone will visit, what information they need, and what result the experience should create.

Planning connects the website type, users, content, navigation, customer journey, requirements, scope, and success measures. It gives future changes a reference point: does a new idea strengthen the intended journey, or distract from it?

Why website types differ

Informational sites help people understand. Landing pages focus on one conversion. Journals encourage reading and return visits. Learning platforms guide progress. E-commerce sites support purchasing. SaaS products help users perform a repeated task. Each needs different content, navigation, features, calls to action, and measures of success.

What we are building

swe.tickerbell.biz is primarily a public educational journal, supported by a landing page and gradually developing into a learning web application. It documents the real journey from a simple public page toward a secure and capable web product through readable pages, downloadable lessons, decisions, mistakes, corrections, and working results.

Positioning statement

Three stages

1. Current: a public educational journal with lesson pages and PDFs.
2. Next: an authenticated learning website with selected resources and progress.
3. Future: an interactive learning application with exercises, tools, and personalization.

Who the website serves

The primary user is a beginner who wants to understand software engineering through a real project. They may know basic technology terms but feel overwhelmed by disconnected tutorials. They need a visible sequence, plain-language explanations, real evidence, and material they can save.

Secondary users include entrepreneurs learning how digital products are built, professionals entering software development, students looking for a practical roadmap, and potential Ticker Bell collaborators.

The planned customer journey

1. Awareness: the hero explains the project quickly.
2. Relevance: the journey section shows why the project is useful.
3. Orientation: the roadmap helps visitors choose where to begin.
4. Learning: consistent lesson pages explain goals, decisions, problems, and results.
5. Depth: a direct PDF download lets visitors keep the material.
6. Trust: real challenges, corrections, code, and public evidence support credibility.
7. Conversion: visitors may subscribe after receiving value.
8. Retention: previous/next links and updates encourage return visits.
9. Future engagement: accounts support saved progress only when that becomes useful.

Sitemap and navigation

The website should remain shallow and easy to understand. The landing page introduces the project and contains the journey, roadmap, lesson cards, updates, about, contact, and footer. Dedicated lesson pages teach one stage. Legal pages explain privacy and terms. A future learning area may contain saved progress and protected resources.

The global navigation should stay short: logo/home, Journey, Roadmap, Lessons, About, Ticker Bell, and a future Login action. Lesson-specific links belong inside lesson pages.

Landing-page plan

1. Navigation
2. Hero with Start the Journey and Explore the Roadmap actions
3. Why this journey
4. Software-engineering roadmap
5. Folding lesson cards
6. Brief architecture reference linking to Lesson 3
7. Journey updates and consent-based subscription
8. About the project
9. Contact and footer

Standard lesson-page template

Every lesson should include: lesson number and title, objective, why the step matters, planning, tools, implementation, problems, solution, security and privacy considerations, result, key lessons, PDF download, previous/next navigation, and the related roadmap step.

Requirements and success

Current requirements

• Responsive landing page and navigation
• Visual roadmap and folding lesson cards
• Dedicated, consistent lesson pages
• Direct PDF downloads
• Subscription form with clear feedback and consent
• Accessible, fast, mobile-friendly presentation
• Previous/next lesson navigation

Meaningful measures

• Relevant visitors and traffic sources
• Movement from the hero to the journey or roadmap
• Lesson-page visits and reading depth
• PDF downloads
• Confirmed subscriptions
• Returning visitors and next-lesson clicks

Analytics should answer product questions and must not collect unnecessary sensitive personal information.

Now, next, and later

• Now: publish Lesson 4, add its landing-page card, connect the PDF, and keep navigation consistent.
• Next: standardize lesson templates, strengthen roadmap links, and define privacy-conscious analytics events.
• Later: add accounts, saved progress, protected resources, search, exercises, and personalization only when their value is demonstrated.

The approved website plan

• Website type: public educational journal with a landing-page introduction.
• Primary audience: beginners learning through a real project.
• Primary value: transparent decisions, problems, working results, and reusable lessons.
• Primary journey: discover, orient, learn, download, follow, and return.
• Primary conversion: consent-based subscription after useful content is visible.
• Content system: roadmap plus a consistent web lesson and PDF for every completed stage.
• Future direction: authenticated and interactive features only when they add clear learning value.