@KitchM This link is hosting our new website as it currently looks. It is still a work in progress. Feedback is very much welcome.
I like the look of it. Decent layout and format. Even with the darker theme, things appear easy to read.
I was able to zoom without the annoying horizontal scroll bar, so that is good.
Two things are missing. First, there is no About page. Second, there is nothing on the home page saying what QPrompt is. Kind of fundamental.
It is assumed that you do not have telephone or address access, so that might be explained in the About page instead. Otherwise, phone and address are normally a home page feature for a business.
Of course, make sure the site is compliant with the W3C.
Does that help any?
Thank you for your feedback, it does help.
The first bullet under Reasons To Use QPrompt makes a good description of the app. Maybe that and a bit more text could be turned into an about section that goes right before Downloads.
I’d like for everything to be in the landing page so adding an About QPrompt section would be preferable.
As for the means for outreach, those are disclosed in the Community and Support sections of the site.
The original version of the site I prepared was W3C compliant. IDK about the version you just saw because I don’t have the code for it yet. That said, I appreciate the reminder. I’ll make sure that it is compliant once I get the new code.
The web site’s focus is the program. Therefore, the home page must explain the program and have a picture of it on the desktop. This is pretty fundamental.
It is a little confusing to see all the other stuff on the home page, including the downloads and the community section. The community section is probably more appropriate to what you might refer to as contact info and/or support.
The download info on the home page is traditionally done with a Download page, which you already have. Therefore not really needed on the home page.
These things tend to clutter up the home page.
About is traditionally about the company, but this is not a company web site, so probably not needed. If you use the About link to describe the program, then that might be unnecessary as a button bar item.
I notice now that I’ve looked at it a little more that you are using the button bar or navigation bar to just jump to sections of the home page. I would not recommend that for two reasons. First, it is not traditional, and second it makes the home page too busy.
Can the user select which language the website is presented?
@KitchM I will break it up into different pages in the future, but I need time to do that because I’ll be using a framework that I’m not familiar with, called Hugo, to create that more traditional multi-site. If made the multiple HTML now it would be more effort that would have to be duplicated later. So it’s in my to-do list.
@videosmith Not for now. That is something that I plan to add but it didn’t made sense to have now because translators can take their sweet time translating. if I had started a couple of months earlier only a language or two would’ve been done on-time.
Could Google perform it realtime for you as the viewer selects like Google Translate?
The ‘inline’ teleprompter is very cool! Can it go fullscreen and save preferences? May make a great emergency backup if the operators local equipment failed.
It does save preferences and it could go full-screen but right now it doesn’t. The reason is because I’ve stripped down a few features to make it load faster, and it still takes way too long to go, which is why a fallback image is loaded first and it is then replaced once the app has loaded.
Right now it’s mostly for show, but I do plan on making it go full screen once I’ve added a few commodities to allow opening and saving files from and to the filesystem.
1 Like
The interactive app is currently not loading because of a misconfiguration in the server. I’ll fix it as soon as I can, but I have to go soon.
How about replacing the Welcome script with Reasons to Use QPrompt and let the viewer operate the app to read those? 
Good idea. I could do that for the WASM build exclusively.
Doesn’t work. The CSS appears to be too convoluted and JavaScript dependant, causing Google Translate to mess it up. That said, the site navigates fine using a text-based web browser such as Links.
This has now been fixed. https://qprompt.app/
It’s enabled only on desktop browsers due to the limited support for WebAssembly in mobile web browsers.
@KitchM Forgot to mention, I added the About QPrompt section. I know you suggested more but this was the best takeaway I could incorporate in a short time. Thank you for all of it.
Also thank you @videosmith for licensing your picture to us so we could use it in the About QPrompt section’s background.
Ok, so this is not entirely true. I’ve found the re-design messed-up the ability to swap from the image to the WebAssembly application and only after it’s been cached the browser shows it appropriately when revisiting the site.
Done. New build is a bit lighter and it incorporates the text from Reasons to Use QPrompt as part of the Welcome script.
Thank you. Appreciated.
BTW, Reasons are not Features. Something to keep in mind.
Good point, fixed it.
Now you have Reasons to Use followed by Why QPrompt. That seems redundant. Another problem is that Reasons to Use is not centered on the button, and does not fit the pattern of one-word titles. It messes up the button bar and loses the streamlined look.
Also, most traditional is to use Features instead. The features should convince the prospect to try out the program.
I would recommend that you use Features only, and break the two sections down into either the list or the box format, but not both. (Maybe two columns? Sections in the list format?)
Further, I would not want you to forget necessary Screenshots to show the prospect what the program interface looks like in various parts.