A prototype app can be found here: https://repocreator.zoltu.io/#/repo-creator. You will need a (free) GitHub login to use the site. Please note: The site currently takes a while to startup the first time, be patient (this will be improved before final release). For testing, use `Zoltu/Templates.NuGet` (should be in the favorites/sponsored lists).
Do not worry about the About page or Pricing page or the nav bar. The work I need done is for everything inside the `repo-creator` section.
The basic process for using the app is the user first needs to choose a GitHub repository to template from, then they need to fill in the replacements, then they need to provide a name for their new repository, then they wait for a bit while it is processed and then they are provided a link to their new repository on GitHub.
For the first step (choosing a repository), there are several ways to choose a repository including favorites, sponsored and popular lists as well as a manual search. The user can favorite any repository that shows up in any list so it will show up for them again in the future.
* If the user is not logged in then there will be no favorites and attempting to favorite something will bring up the favorites prompt, at which point the favorites will show up (if they log in).
* As seen in the prototype, the favorites, sponsored and popular lists will load after the page is loaded, and the experience for slow load times must be good.
* The lists don't have to remain separate, all in one list, a single filterable, list, anything that allows me to display the different information is fine, as long as the user can tell the difference between them.
For the second step (replacing items), the user will be provided with a list of items to replace. They must provide replacements for everything before they can continue. It may take a little time to get from the first step to here as some background processing is required.
* The number of items to replace may be long, or it may be short (only a couple items).
* If there are no items to replace then it means an invalid repository was chosen, the user needs a way to be notified of this.
For the third step (providing a name), the user must provide a repository name. The name may need to be validated (takes a moment) and then the user can create the repository.
For the final step (waiting for creation), actually creating the repository, the user may have to wait a medium amount of time before their repository is ready.
All throughout the process, the application needs a way to notify users of errors and potentially send them back one or more steps when an error occurs.
I am primarily looking for **USABILITY**! I do want the app to look good but more importantly I really need it to be intuitive and easy to use. I would prefer a clean UI without a lot of distractions. **RESPONSIVE** design is my second highest priority. I'm not looking for a phone version, but I do want the app to look good on a wide variety of monitor resolutions. Please do not design the app to only be in the center of a widescreen monitor as is common in many blogs and such these days.
Do not use the prototype as a template! The prototype I linked above is *TERRIBLE* and its only purpose is to show the general concept of the application. It is written in a very old fashion style of multi-page wizard and doesn't follow any modern best practices. I'm looking for a UX designer to take the general workflow and build a user experience for it, the prototype is so far away from a good user experience it shouldn't be used for anything other than to get an idea of what the application does.
Any ideas are welcome, please think outside of the box. The only constraint is that the application must be fully contained in a single browser window. Please do not be constrained by implementation concerns, I'll worry about that later.
The steps I listed above are the steps at a technical level. If you can figure out a way to make the user experience better with a different set of steps please do so. However, be aware that until the user chooses a template I can't show them the replacements list.
You will notice a nav bar at the top. This nav bar is also just a prototype but do not worry too much about it and do not consider it greatly in the design of the application. The website the application is hosted in *will* have a nav bar but depending on the design of the app, it may or may not need to be factored in. For example, if the app ends up being delivered via a modal pop-up, then the nav bar will just be a piece of the background. If the app ends up being rendered in the page, then the nav bar will be above or to the left of the app.