https://arstechnica.com/information-technology/2018/03/lets-encrypt-takes-free-wildcard-certificates-live/

When creating a new Ad, the following workflow should be followed.

Click Sell
Verfiy VIN
Upload Photos
Validate Images {Confirm vehicle match}
Provide Details of Item (Extra details ex.papers)
Provide Price of Item
Validate Price
POST

GTmetrix-report-avosa.co.za-20171119T223636-RGhszCu3-full.pdf

After doing a few performance tests, we should look at increasing performance for a Higher Rating.

We should put `json:"omitempty" on slices and nested models so that they are ignored when transformed to JSON.

Everyone selling an item, must have an account.

Register Model

Name
Email
Cellphone
Location (Lat & Lon)
Verified == false
"Password"

The proxy application doesn't get an updated URL if it's subdomain applications weren't active at the time of launch. We could merge the "router" application with the "proxy/main" application to make it easier to control load and requests

Many items on this application can be up/down voted.

Votes have the following rules:

Only logged in accounts can vote
One vote per user
Votes should only show the summary after a vote.
If non-users click on vote, they will be asked to register.

Currently we have to keep full URLs in javascript, but this creates more work when deploying and testing. We should rather get the URL from the target application ("Communication.API") and the instanceKey as we do in the back-end services.

Because Listen and Serve TLS is running on a goroutine, we don't see errors from this function.
The most common error is that the certificates aren't copied to the bin folder automatically and causes the Gate.APP to crash if it can't find the caretificates.

https://user-images.githubusercontent.com/13828838/28325991-b4783758-6bdf-11e7-8a0e-724d756569b5.png

We don't need any themes at this stage. A simple bootstrap theme will suffice.

Before analytics is loaded, we should implement a check to see if the applications are running in DEBUG. This will avoid inaccurate page data.

https://startbootstrap.com/template-categories/ecommerce/

Also check if Payfast will work?

https://www.payfast.co.za/accept-payments-easy-way/?utm_source=google&utm_medium=cpc&utm_campaign=payfast_signup&gclid=CjwKEAjw6szOBRCF2sPTjfrJuXASJADDOLEFi1mv7Kvo2zVs7V1l5j5wT0tO14M1fNdguaNGJQ03wBoCpzjw_wcB

Ads should display all data made available by the "Ad model"
Users should also be able to comment on the ad, as well as up/down vote it.
Comments can also be up/down voted.

Currently we are loading webservices directly from the full URLs. We need to get the "active" URL from the Router, to reduce config and mapping.

http://www.abantecart.com/

Currently we are directly calling the /Message API to handle contact us requests.
Applications should only be allowed to call the proxy service for API requests

https://www.jetbrains.com/buy/opensource/?product=go

You have to be a project lead or a regular committer.
Your OS project meets the Open Source definition.
Your OS project may not offer paid sponsorship; receive funding from commercial companies or organizations (NGO, education, research, or governmental). You do not provide any paid support, consulting or training services for your OS project, and you do not distribute paid versions of your OS software. Contributors who are paid to work on the project are not eligible.
Your OS project is in active development for a minimum of 3 months.
Your OS project's community is active. This means that you have recent activity in your newsgroups or forums.
Your OS project has a website including either a regularly updated News section or links to social network account(s) where project updates are posted.
You release updated builds on a regular basis.

We don't want bot abuse. :)

When in mobile view. The menu resets when pressed.

The ID column of every table should have the following Attributes;
Type: int64 (bigint)
Primary Key
Auto Increment

Although CORS settings have been setup on every API, we can also limit some origins from accessing certain URLs

http://blog.lemonstand.com/html-projects-with-source-code/

We need to retrieve client information so that we can send contact-us emails to their respective destinations.

We will also need to log application names in the comms database.

For websites that we host, we need to keep track of domain expiry and customer details, etc.

Currently only javascript is being compiled.
We must clean and minify any CSS found across our applications.

All applications should be accessed by HTTPS only.
https://godoc.org/golang.org/x/crypto/acme/autocert

Hier is n paar snippets dalk kan jy iets gebruik.

https://bootsnipp.com

People selling items must have an account, thus the need for a login page.
All logins should be salted and hashed. At this stage we don't have a need for using Oauth logins.

Once registered, users should be able to login with their email OR cellphone details.

Loggin should be setup, so that we can replay every action a user executes. This way, when an error occures, we can take the session ID and replay all events.

https://docs.microsoft.com/en-us/aspnet/mvc/overview/security/xsrfcsrf-prevention-in-aspnet-mvc-and-web-pages

Currently we keep all routing statistics in memory. These requests should be logged to a database.

sellers will often be viewed to see which other ads they currently have.

This page should display the basic information of the seller and also his/her active ads.

People can also comment and up/down vote sellers.

At a glance we should be able to see a summary of all of our social media accounts

For API level authentication we should return a 401 and any caller should then handle the status as needed.

For UI level authentication, when a user is not authorized, we must redirect to the login page. The referer/returnURL will be the original application requested. This means that the user will be redirected to the original application after successful login.

Warring not return to page.
"Password must be at least 6 characters."

Possible to enter invalid email. (end of email)

Currently the site edit page only loads data, we need to implement save and edit functionality.

We need to keep track of all Request/Response Data;

• Time from Request to Response
• Request Size
• Response Size
• Origin and Referers
• Other data to come...

Part of making our software meet OS standards, we need to have a news/updates section.
This will also be used to post blogs

http://formvalidation.io/examples/contact-form/

https://en.wikipedia.org/wiki/Vehicle_identification_number
https://en.wikibooks.org/wiki/Vehicle_Identification_Numbers_(VIN_codes)/World_Manufacturer_Identifier_(WMI)
https://www.yourmechanic.com/article/how-to-decode-a-vin-vehicle-identification-number-by-jason-unrau

https://jalopnik.com/5165656/how-to-read-a-cars-vin

Can be used to give visitors more information on the vehicle and also to be used to verify other information related to the vehicle.

Most Important Brands

• BMW
• Ford
• GWM
• Honda
• Hyundai
• Isuzu
• KIA
• Mahindra
• Mercedes
• Nissan
• Renault
• Toyota
• Volkswagen

We can use www to host other businesses websites (avosa.co.za/carlacandles).
We will then also have to seperate the routing/domain logic to a seperate program.

We should write a function that creates validation rules based off of orm: rules on model level.
These validation rules should then be rendered on the client side and validated again on server-side.

https://za.pinterest.com/pin/375839531377308156/
https://www.google.co.za/search?q=SplinterCell+Blacklist+UI&safe=off&rlz=1C1CHBD_enZA785ZA785&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwjY6KnkgKPaAhUVM8AKHZIIDb4Q7AkIQQ&biw=1678&bih=954#imgrc=lOhQkMj-mv6XeM:
Base design off of SplinterCell Blacklist UI,

--Menu
https://www.google.co.za/imgres?imgurl=https%3A%2F%2Fi.pinimg.com%2Foriginals%2F94%2Ff7%2Fcb%2F94f7cbd425306cd9a99c4783304b9f67.jpg&imgrefurl=https%3A%2F%2Fwww.pinterest.com%2Fpin%2F460563499373494918%2F&docid=lfwF0a9ra_hVvM&tbnid=yX76Yh1KlIS70M%3A&vet=1&w=1680&h=1050&safe=off&bih=954&biw=1678&ved=0ahUKEwig0ZnzgKPaAhWKJcAKHTioDE0QMwhqKCEwIQ&iact=c&ictx=1

We should be able to test certain applications without the need to spin up any other programs.

Some users will block the permission for requesting their location.
We should display an info section stating the reasons we are trying to get the user's location.

https://twitter.com/Avosasoftware

Subdomains have to be controlled within go.

For complete subdomain control and allowing different services to be called from a subdomain.
https://gist.github.com/thezelus/d5ac9ec563b061c514dc

The login and registration pages' CSS doesn't fit in the screen correctly.

To allow for an easier, more object oriented approach, models should inherit a "DBSet" for more control over objects and how they are persisted to the database.

When a page with many records (GetAll) is loaded, it should always be loaded as page 1 and limit records to 10.
When a user navigates to the next "page", we can go back to the server and load the next result set.
This will ensure that every "page" is index-able.