Remove mentions of example apps + clean up URLs

Author: jits

ARCHITECTURE.md

@@ -1,12 +1,10 @@
 # Architecture and design decisions
 
-This document covers the overall architecture and design decisions made for this base template, and the associated [FullStacksDev](https://FullStacks.dev) Angular and Firebase tech stack.
+This document covers the overall architecture and design decisions made for this base template, and the associated [FullStacksDev](https://fullstacks.dev/) Angular and Firebase tech stack.
 
 > [!NOTE]
 >
 > Feel free to deviate from these as you wish. The base template is designed to be fairly flexible so you can adapt it to your needs. Though note that deviations may require more tinkering to get everything to work well together.
->
-> If you're keen on the full _curated tech stack_ experience — where we build on top of this base template with more opinionated patterns, practices and approaches — then check out the [example apps](https://fullstacks.dev/stacks/angular-and-firebase).
 
 > [!TIP]
 >
@@ -124,10 +122,6 @@ This live project is your **production** environment — what your users will ac
 
 The deploy script will deploy to this live project (details below).
 
-> [!TIP]
->
-> In the patterns example app (coming soon) we show you how to set up an intermediate staging environment, together with continuous deployment (CD), which requires a bit more set-up and configuration.
-
 ## How the deploy works
 
 | **:brain: Design decision**                                                        |
@@ -148,7 +142,7 @@ The [`./deploy`](./deploy) script in the root of the project is a simple script
 >
 > This is designed to be run locally only (not as part of a CI/CD pipeline) as it benefits from your locally authenticated `firebase` CLI.
 >
-> For CI/CD you'd want to update the GitHub Actions pipeline to deploy to Firebase, which would involve setting up a service account and securely storing the credentials in GitHub Secrets so that the pipeline can authenticate with Firebase. We show you how to do this in the patterns example app (coming soon).
+> For Continuous Deployment (CD) you'll want to update the GitHub Actions pipeline to deploy to Firebase, which would involve setting up a service account and securely storing the credentials in GitHub Secrets so that the pipeline can authenticate with Firebase. And also modifying the deploy script to make it non-interactive (or add a non-interactive mode via a flag).
 
 > [!IMPORTANT]
 >
@@ -244,7 +238,7 @@ This is a recommended folder structure based on [Nx's suggested library types](h
 
 For features within the `shared` folder you should follow the same structure, except you probably won't need a `feature` subfolder within each shared feature since these are shared bits of code for use elsewhere.
 
-As things grow you may need to adapt and tweak this structure (e.g. to add another level in the hierarchy) — we show you how to tackle this in the patterns example app (coming soon).
+As things grow you may need to adapt and tweak this structure (e.g. to add another level in the hierarchy).
 
 ## [`app`] Static prerendered pages and dynamic pages only
 
@@ -374,7 +368,7 @@ State management is a bit of a hot topic in the Angular community, and there are
 >
 > The [NgRx docs](https://ngrx.io/guide/store/why) do a fantastic job of explaining why you would want to use a library like NgRx to manage state. The linked page covers the older (but still relevant) NgRx Store, but the principles are still applicable to SignalStore. Note that SignalStore is more lightweight and does not follow the Redux pattern, making it a bit simpler to use.
 
-The base template uses SignalStore for the provided global auth store as well as the component-specific login flow store. We cover stores (and state management) in more detail in the [example apps](TODO).
+The base template uses SignalStore for the provided global auth store as well as the component-specific login flow store.
 
 ## [`app`] Accessing Firebase services from the Angular app
 
@@ -460,10 +454,6 @@ We encourage use of [ng-mocks](https://ng-mocks.sudo.eu/) to simplify a lot of t
 
 Most of the components, services, etc. provided in the base template have corresponding test suites.
 
-> [!TIP]
->
-> We cover testing in more detail in the [example apps](TODO).
-
 ## [`app`] Linting using ESLint and formatting using Prettier
 
 | **:brain: Design decision** |
@@ -521,10 +511,6 @@ We do recommend splitting out the actual functions into separate files within th
 >
 > Make sure you go through the [Firebase Functions docs](https://firebase.google.com/docs/functions) to understand how to write functions and what you can do with them. Also make sure you understand the costs and operational model of Firebase Functions.
 
-> [!TIP]
->
-> We make use of Firebase Functions extensively in the patterns example app (coming soon).
-
 ## [`firebase`] Security rules
 
 The base template comes with all security rules — for Firestore, Realtime Database and Storage — set to block all access by default. This is the most secure setting. As you build out your app you'll need to update these rules to allow the necessary access.
@@ -557,10 +543,6 @@ See the files within the [`firebase/test`](./firebase/test/) folder for the secu
 >
 > You can add any additional tests you want in this folder — Vitest will pick these up as long as they contain ".test." or ".spec." in their filename.
 
-> [!TIP]
->
-> We cover more Firebase testing, such as functions testing and integration testing, in the patterns example app (coming soon).
-
 ## [`firebase`] Linting using ESLint and formatting using Prettier
 
 | **:brain: Design decision** |
@@ -586,5 +568,3 @@ Use the [Firebase Console](https://console.firebase.google.com/) to manage and m
 > [!CAUTION]
 >
 > Firebase currently doesn't have a way to set a hard limit on costs, so you need to be vigilant about monitoring your usage and costs, and how you build features to make sure of Firebase services. Ultimately, you are responsible for the costs incurred by your use of services like Firebase.
->
-> We cover some strategies for managing costs in the patterns example app (coming soon).

README.md

@@ -1,15 +1,11 @@
-# The [FullStacksDev](https://fullstacks.dev) Angular and Firebase base template
+# The [FullStacksDev](https://fullstacks.dev/) Angular and Firebase base template
 
 Part of the curated [**FullStacksDev Angular and Firebase tech stack**](https://fullstacks.dev/#angular-and-firebase). For solo devs and very small teams.
 
 An opinionated full-stack starting point for building a web app, using Angular and Firebase. Aiming to be lean and useful enough so you can hit the ground running and focus on stuff that matters. With enough room for you to extend as you need.
 
 You are free to use and customize this template as you want — build a prototype, an internal tool, a side project, or the next big thing.
 
-> [!IMPORTANT]
->
-> This is currently in **beta**. We're actively working on it and will be making regular updates — expect big changes and improvements until it gets to a stable release. Feel free to give your feedback and suggestions via the Issues tab.
-
 ## Features
 
 This template gives you an empty app skeleton, working end-to-end, with the following included:
@@ -280,7 +276,7 @@ Make sure to do all this in a branch, test locally and push to GitHub, then open
 
 > [!IMPORTANT]
 >
-> This is like any other dependency update process and can sometimes require changes to your code. Especially with major version updates with breaking changes. We aim to keep the base template up-to-date with the latest versions of dependencies, and if these result in changes to the code we make a new release of the base template with specific instructions on what to do. See the next section for more on this.
+> This is like any other dependency update process and can sometimes require changes to your code. Especially with major version updates with breaking changes. We aim to keep the base template up-to-date with the latest versions of dependencies, and if these result in changes to the code we make a new release of the base template with best-effort instructions on what to do. See the next section for more on this.
 
 > [!TIP]
 >
@@ -298,7 +294,7 @@ Make sure to do all this in a branch, test locally and push to GitHub, then open
 >
 > Also, we won't usually make releases for simple dependency updates, or content changes.
 
-Whenever we make a new release of the base template we will provide detailed release notes with specific instructions on what to do to update your app. These will contain specific code changes you can make (some may be optional), and it will all depend on how much you have deviated from the base template, and what is relevant to your app.
+Whenever we make a new release of the base template we will provide release notes with best-effort instructions on what to do to update your app. These may contain specific code changes you can make (some may be optional), and it will all depend on how much you have deviated from the base template, and what is relevant to your app.
 
 > [!IMPORTANT]
 >
@@ -314,10 +310,6 @@ We document the architecture and design decisions in [a separate doc](ARCHITECTU
 
 Feel free to deviate from these as you wish. The base template is designed to be fairly flexible so you can adapt it to your needs.
 
-> [!TIP]
->
-> If you want to get the full "curated tech stack" experience check out the example apps for this tech stack (more info at the end of this doc).
-
 ## How-to guides
 
 Here we document some how-to guides to help you get started with this base template.
@@ -464,20 +456,9 @@ Some email templates (e.g. for Authentication) are customizable in the [Firebase
 
 ## How we decide what goes into the base template
 
-It's important that the base template is as lean and broadly useful as possible, whilst maintaining the opinionated approach to the tech stack, architecture and patterns that we are developing as part of the _curated tech stacks_ approach in [FullStacksDev](https://fullstacks.dev).
-
-For this reason, we carefully consider what goes into the base template and err on the side of caution. New capabilities are only added to the base template when they are proven to be broadly useful and fit within the tech stack, by first applying them to real-world projects and the example apps.
-
-## What next? Check out the example apps for this tech stack…
-
-If you want to continue learning more about the [FullStacksDev Angular and Firebase tech stack](https://fullstacks.dev/stacks/angular-and-firebase) you can check out the premium example apps built using this template (requires a premium upgrade):
-
-- [Simple example app](https://github.com/FullStacksDev/angular-and-firebase-simple-example-app)
-- Patterns example app (coming soon)
-
-These apps showcase the capabilities of the tech stack and give you an opinionated, pragmatic and in-depth learning experience. Each come with comprehensive documentation and learning content covering patterns, architecture decisions, design decisions, data models, tech stack capabilities, learnings and more.
+It's important that the base template is as lean and broadly useful as possible, whilst maintaining the opinionated approach to the tech stack, architecture and patterns that we are developing as part of the _curated tech stacks_ approach in [FullStacksDev](https://fullstacks.dev/).
 
-You can read more about the [purpose and specs of the example apps](https://fullstacks.dev/example-apps-and-patterns).
+For this reason, we carefully consider what goes into the base template and err on the side of caution. New capabilities are only added to the base template when they are proven to be broadly useful and fit within the tech stack, by first applying them to real-world projects.
 
 ## License
 

app/src/app/website/feature/home-page.component.ts

@@ -6,7 +6,7 @@ import { ChangeDetectionStrategy, Component } from '@angular/core';
   template: `
     <h1 class="mt-8 text-center">
       This is the
-      <a class="underline decoration-dotted" href="https://fullstacks.dev">FullStacksDev</a>
+      <a class="underline decoration-dotted" href="https://fullstacks.dev/">FullStacksDev</a>
       Angular and Firebase template running on Firebase
     </h1>
   `,