Frontend CMS + UI developer to create basic prototype x-platform webpage in Angular/.Net
Budget: $750 – $1,500 NZD
We are looking for a UI frontend developer experienced in Angluar / .Net to help us build up our Cross Platform codebase (Web, Andriod, IOS) by taking wireframe / prototype designs done in Adobe XD (with HTML + CSS outputs) and code them up using both a Content Management System (Froala or other) and .Net/Angular code to achieve a restful responsive interface.
This assignment is to take a small number of blank template pages from the Adobe XD designs, add them to the CMS (Froala or other) and then get the write the code to bring the CMS content to the webpages according
to the designs. The pages will need to appropriately responsively size on Phones and tablets.
The web-pages will be very simple with no dynamic content other than the text that comes from the CMS.
Assignment Detail
------------------------------
The web pages we are looking to have developed are essentially going to be working shells with limited content (nothing complex).
In detail the pages we are looking to have developed will be limited to 9 pages as below:
1) Non-Authenticated landing page - simple introductory page with no more than 5x content components (text blocks, images, carousels, etc) from CMS
2) Non-Authenticated "Contact us" page with forms and/or email links
3) Blank template page with menu items, CMS placeholders and structures, that can be used to create other pages as needed. e.g. we could then use the structure to create other pages such as Terms of use; privacy policy, about us or whatever.
4) Non-Authenticated - Logon / Forgot my Password authentication screens (just the UI - the authentication logic exists)
5) Authenticated landing page (Dashboard Page) - as per design with basic authentication information presented (name, company)
6) Authenticated "Analyse Page" - simple page with non-dynamic placeholder graphics to mirror design from the Authenticated design set with menus as per authenticated design. No dynamic content other than authenticated information
7) Authenticated "Prioritise Page" - as above, but with slightly different images and design layout
8) As above, but for a page called "Sequence"
9) As above, but for a page called "Viewer"
Further Notes about the brief:
----------------------------------------------
a) All the above pages need to have a common menu that links the pages together (Authenticated and non authenticated).
b) Adobe XD design wireframes will be provided with ability to export to HTML and CSS
c) A CMS has not yet been implemented, so if you have a preference to use something other than Froala please feel free to make your recommendations
d) The pages we'd like developed are intended to be more placeholder / prototype pages but need to show content from the CMS and have functioning menus. We can add the dynamic content later.
e) Any code developed needs to be cross-platform code as mobile apps will be produced once the website is functioning.
f) the page designs will likely be changed many times, so any code written needs to be flexible / adaptable and using CMS content / object placeholders wherever possible
g) The CMS has not yet been selected, so a key part of the assignment will be to agree what CMS to use and to set it up and get it functioning with the site.
h) Overall we are looking for this to be a small and quick assignment to develop a working shell from prototype wireframe designs done and ideally find a developer / designer that we can work with more on future assignments as we begin to develop more of the dynamic content.
This assignment is to take a small number of blank template pages from the Adobe XD designs, add them to the CMS (Froala or other) and then get the write the code to bring the CMS content to the webpages according
to the designs. The pages will need to appropriately responsively size on Phones and tablets.
The web-pages will be very simple with no dynamic content other than the text that comes from the CMS.
Assignment Detail
------------------------------
The web pages we are looking to have developed are essentially going to be working shells with limited content (nothing complex).
In detail the pages we are looking to have developed will be limited to 9 pages as below:
1) Non-Authenticated landing page - simple introductory page with no more than 5x content components (text blocks, images, carousels, etc) from CMS
2) Non-Authenticated "Contact us" page with forms and/or email links
3) Blank template page with menu items, CMS placeholders and structures, that can be used to create other pages as needed. e.g. we could then use the structure to create other pages such as Terms of use; privacy policy, about us or whatever.
4) Non-Authenticated - Logon / Forgot my Password authentication screens (just the UI - the authentication logic exists)
5) Authenticated landing page (Dashboard Page) - as per design with basic authentication information presented (name, company)
6) Authenticated "Analyse Page" - simple page with non-dynamic placeholder graphics to mirror design from the Authenticated design set with menus as per authenticated design. No dynamic content other than authenticated information
7) Authenticated "Prioritise Page" - as above, but with slightly different images and design layout
8) As above, but for a page called "Sequence"
9) As above, but for a page called "Viewer"
Further Notes about the brief:
----------------------------------------------
a) All the above pages need to have a common menu that links the pages together (Authenticated and non authenticated).
b) Adobe XD design wireframes will be provided with ability to export to HTML and CSS
c) A CMS has not yet been implemented, so if you have a preference to use something other than Froala please feel free to make your recommendations
d) The pages we'd like developed are intended to be more placeholder / prototype pages but need to show content from the CMS and have functioning menus. We can add the dynamic content later.
e) Any code developed needs to be cross-platform code as mobile apps will be produced once the website is functioning.
f) the page designs will likely be changed many times, so any code written needs to be flexible / adaptable and using CMS content / object placeholders wherever possible
g) The CMS has not yet been selected, so a key part of the assignment will be to agree what CMS to use and to set it up and get it functioning with the site.
h) Overall we are looking for this to be a small and quick assignment to develop a working shell from prototype wireframe designs done and ideally find a developer / designer that we can work with more on future assignments as we begin to develop more of the dynamic content.