UI Updates

Initial Structure

Initially, the project cards just showed the information of the title and estimated read-time. While the text which was being rendered in many places would have the wrong highlighting effect.

Reason for these issues:

• Inside global.css it had the default hue for the Headings to be turquoise colour
• While text did not have its own colour inside the style giving it turquoise hue as well

Updated Structure

The structure for global.css was changed and how the hue was being added was changed inside GhostTerminal.jsx. This allowed the rendering to not have wrong hue to the text, while at times being just clean text. Which I think adds a sleek and clean nature to the site.

• Basic heading hue is set to nothing
• Allowing more flexibility when designing new features

The project cards are much more nicer. After brainstorming for some time the design I think best suits this theme and actually looks nice is: showcasing the image for the project, the project title, the project description, the tech stack which was used in the project, the estimated read time.

A cool effect is also added for hover the greyscale image with a turquoise tint to is slowly shows its colour on hovering and vault files have the same effect but with rustic amber theme

Backend Update

Initial Structure

The highlight area for the project was not fetching any logs initially as it was left with the placeholder. Alongside with this the transmissions/logs that were being stored did not contain the project ID.

So, there was no way to link the transmissions/logs to the project in any manner. So, filtering for only the project was not an option.

Before this, the plan was to always go to the private repo containing the source code. Adding another .mdx file and filling the content in it and then staging the changes pushing it and letting the github actions update the compiled site with the new added post.

Updated Structure

Transmissions

Now, the highlight area contains the logs which are fetched from the current existing logs the vault files are not fetched. While the number of logs that are shown in laptop, tablet, mobile phone are different making sure if multiple logs are attached to a project it doesn’t make the experience bad for the user.

CMS

Now, I introduced OAuth Appin github which Decan CMS can access. Such that, after confirming my credentials. I can then just write a post fill the fields and publish it just like this one. Where I can choose to make it vault post or just a public post.