From 6c8bf190ba62fba524d6540d3205f0e0a5d45cbd Mon Sep 17 00:00:00 2001
From: Tina_Azure <->
Date: Mon, 3 Apr 2023 04:23:54 +0200
Subject: [PATCH] Add alias system and alias creation page to the spec

---
 spec/spec.md | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/spec/spec.md b/spec/spec.md
index 179b03f..5f2ecf1 100644
--- a/spec/spec.md
+++ b/spec/spec.md
@@ -44,13 +44,22 @@ $onDeliverPaid - A boolean representation of if the on-Deliver Payment has been
 
 ## Customer
 
-### "/"
+### /@{String}
+
+personal freelancer links that link to the freelancer profile and/or template
+DB structure 
+{
+	$alias
+	$destination
+}	
+
++++ "/"
 
 "/" should return the main page of the site based off an HTML template provided to the program. 
 
 Ideally, the only interaction on this page will be with freelancer "Profiles", which may be selected by the end user to view more details about commissioning said person.
 
-### /customer/$freelancer/
++++ /customer/$freelancer/
 
 This page should consist of all the information about a freelancer that the freelancer has decided to show. This includes contact information, pricing, templates, and anything else. Freelancers should be given a lot of sway with what they wish to put here.
 
@@ -68,6 +77,10 @@ This information should be stored in a database of commission requests. A reques
 
 ## Freelancer
 
+### "/freelancer/aliasSetup"
+
+A simple page for the selection of an alias and a destination which can be the profile or a specific template.
+
 ### "/freelancer/inbox"
 
 The inbox will be a simple list representation of commissions a freelancer has, ideally highlighting new ones. This web interface need not be complex for the back-end work currently, but it should be able to easily be stylized with simple CSS.