This commit is contained in:
@@ -1,21 +1,28 @@
|
||||
# now
|
||||
|
||||
Completed if not perfect docs first with a new update (check db update if worth doing as well)
|
||||
double check all links may have changed
|
||||
Post online with notice in beta forum then can perfect docs more later but should do email contact form thing first.
|
||||
|
||||
|
||||
|
||||
|
||||
rockfish contact email form app
|
||||
do not email confirmation to user anymore, just show message sent result to user so we avoid spamming back to spammers
|
||||
add an external .json list it can read from to see who to NOT send emails from but pretend it did so can edit anytime
|
||||
Intuit thing from cardjohn email fuckers need some hand holding apparently for old production keys, fuck!!!
|
||||
|
||||
Docs completion
|
||||
search for 
|
||||
less than 30 so that's good! :)
|
||||
|
||||
Image all the prior docs: Docs could use images on every page of each item, people like images and they may read the docs rather than look at the app so it's nice to show them
|
||||
Add where items are selected to all prior docs just as it's been done at the top of the vendors doc which goes a long way to have users understand the purpose of each type of object and why they might want to use it
|
||||
Use the "references avendor" search pattern substituting vendor for whatever to find all the links in the schema which is the most reliable way to find them
|
||||
this process also finds missing things in the docs like the vendor for User subscontractor I found which was not documented as it only appears when you select subcontractor type
|
||||
ADD TO DOCS:
|
||||
test server license expired so goes to license request page even though there is data in it and when I enter the license request company name etc it says all data will be erased!?
|
||||
must be something to do with expired license but no idea why it would say that fuckery!
|
||||
It's deliberately coded this way in the client UI: if there is existing data and it's an expired *trial* then it will automatically prompt to erase db before it will even send the request
|
||||
this is good, but confusing, maybe a better message indicating what's up?
|
||||
Also docs need addition about this issue and process.
|
||||
not a highly important thing, but should be noted in docs at least
|
||||
|
||||
rockfish contact email form app
|
||||
do not email confirmation to user anymore, just show message sent result to user so we avoid spamming back to spammers
|
||||
add an external .json list it can read from to see who to NOT send emails from but pretend it did so can edit anytime
|
||||
|
||||
|
||||
TEST IMPORT FILE OPEN ON iPad device as the file input accept type may not work with apple
|
||||
|
||||
@@ -23,6 +30,11 @@ There is a postgres14 update, check into it for the windows standalone and docs,
|
||||
|
||||
Release new beta version and document on forum
|
||||
|
||||
Image all the prior docs: Docs could use images on every page of each item, people like images and they may read the docs rather than look at the app so it's nice to show them
|
||||
Add where items are selected to all prior docs just as it's been done at the top of the vendors doc which goes a long way to have users understand the purpose of each type of object and why they might want to use it
|
||||
Use the "references avendor" search pattern substituting vendor for whatever to find all the links in the schema which is the most reliable way to find them
|
||||
this process also finds missing things in the docs like the vendor for User subscontractor I found which was not documented as it only appears when you select subcontractor type
|
||||
|
||||
|
||||
start in on QBI
|
||||
minimum viable product, just something that works
|
||||
@@ -82,9 +94,14 @@ critical path items:
|
||||
- QBOI (or server to login and path for them to do it on their server however that works so we can exit that biz)
|
||||
- import inventory and parts for future new sales will be critical
|
||||
ultimately being able to import directly from other apps export formats or online api keys would be ideal
|
||||
- Pricing, how we will approach it for new vs v7 and what it will be
|
||||
inflation additions
|
||||
set full price but then coupon it for v7 users for first year so they pay same price
|
||||
process of going from one to another must be handled carefully, ideally we get them on a new subscription with a discount to be same price
|
||||
- License agreement change from beta to regular
|
||||
- Docs completed filling in, many empty pages still
|
||||
- business stuff like rockfish, licensing new site, new forums (update docs links when new forum), direct purchase
|
||||
need v7 stuff still easily available, maybe all under a new /v7 but kept exactly as is in path
|
||||
- Beta testing completed
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user