We have an internal Portal which we are using to:
1. Automate our business by exposing web forms and calling our internal API's
2. Document our API's in a Developer Portal using Swagger documentation
3. Store knowledge base content in a wiki
We are using GDS Prototype Kit as a web framework to develop our front end which uses NodeJS, Nunjuks and Express framework.
[login to view URL]
We use GitLab to store the codebase and have setup CI/CD into Kubernetes Engine using Docker for the containerisation.
I have some improvements I need to make to the site and if this works out I have more work to create a Client Portal and Job Candidate Portal
It is important that whoever we work with is responsive and able to start quickly and turn around changes fast. Thus please only apply if:
1. You are able to work direct - not interested in Consultancies as I have ongoing work
2. You must have extensive knowledge of Node JS, Express Framework, Nunjucks and ideally GDS Prototype Kit and Apache Camel
3. You are able to be responsive
4. You must be able to work within our standards and be pro-active
Some example changes that need working on urgently.
Change 1 - Here is an example of what I would like the swagger API docs to look like. The column on the left could contain the API names. The Panel on the right could contain the individual API Swagger docs. There is also a “Open example in a new window” option.
Change 2 - This is not a LTS Dashboard app. Rather it is an Internal Portal App for our staff to use for automation and as a knowledge base. There will also be a Client Portal in the near future. Please rename
Please change ” LTS Dasbhoard Portal” to “Internal Portal”
Change 3 - I would like to use the Portal as our own wiki as well, thus the current internal [login to view URL] can be replaced. There are example documentation pages already here which we should link to from the Portal.
Change 4 - The front page should not be the LTS dashboard but an overview page that can link through to various parts of the portal. I expect it to be very similar to this page: [login to view URL]
You can keep all the same headings for now if you like. However I envisage having sections like:
1. Technology Platforms
2. Standards and Methodology
3. Reference documentation
4. Tools and Resources
Change 5 - The header does not display the logo very well. It looks a mess
Pasted image at 2018-12-19, 12:36 AM
In our documents we have used the following header format. This idea of having white and then a folding blue tab on the right may work well as it seems you will need to keep the search bar which is white
Change 6 - our address has changed. Please update it to xxxxx
Change 7 - This profile does not seem to fit in the the GDS standard. Please remove it and move it somewhere else
Change 8 - This menu item also does not fit in with the GDS standard. Please remove it
Change 9 - All the API’s seem to point to the sales-api-p. Can you please update the links so that they all work?
Change 10 - The GDS standard shows that when you click on items they appear in the header like this. Please can you do the same