nativesintech / nativesintech.org Goto Github PK

Problem

In order to get the v2 roadmap off the ground, someone will need to create a branch and push up a starter skeleton of the project using Next.js.

Acceptance Criteria

• Skeleton project setup using TailwindCSS and TS
• Storybook is added so components can be built in isolation

https://www.netlify.com/press/

Problem

The header component from v1 was created with the semi css framework that I created. Instead it should be created with TailwindCSS. It might help to use storybook for this as well so that component can be build in isolation.

Depends On

#84

Design

Acceptance Criteria

• Header looks like v1
• Header is made using TailwindCSS
• Header link styles are updated
• Header is mobile responsive
• NiT icon in the top left is replaced with computer svg icon
• Computer svg icon colors are update to match tailwind css (teal-400, gray-800)

Problem

The footer component was made with my personal css framework. It should be updated to use TailwindCSS instead.

Depends On

#84

Design

Acceptance Criteria

• Footer looks like v1
• Footer is made with TailwindCSS
• Figure out where Netlify's logo goes without it looking weird :)

Summary

When on a mobile, specifically phone, device and you click on the menu to navigate to another page, clicking on the same page you are on does not close the menu. Instead you have to click on a new page and then click the menu again to navigate to the old page. This is tedious and bad UX.

@all-contributors please add @csutherl for code,doc

Background

It has been about a year since the site has been developed and it needs some improvements from an aesthetic as well as a functional point of view. I think the site can be improved in two ways: (1) Move over to using Next.js with TypeScript & TailwindCSS and (2) use ghost as our headless CMS.

Initiatives

Move to Next.js with TypeScript support and TailwindCSS

This project was originally developed using Phenomic, but it doesn't look like it will be maintained in the future :( MoOx/phenomic#1286. For this reason, it makes sense to move the project over to using Next.js. There are bindings out there to still use Reason, which would make the transition easier, but it's more fun to build something from scratch am I right?

TailwindCSS is a utility first CSS framework. It makes it super easy to build beautiful sites using their utilities and they also have great editor support. When I started the project it was a goal of mine to develop my own CSS framework and although it was a nice learning experience it was not something that I could maintain in the long term. So going with TailwindCSS I think is a safe bet going forward.

ReasonML is a wonderful language but there is a learning curve to using it. It's still in its infancy and I would like to see other people contribute to the codebase other than myself. TypeScript is being adopted at a quick rate in the web dev industry and even though the types are terrible at times, it's where many devs are at right now so I need to meet them there.

Ghost CMS

It seemed fine when I first started that the CMS would be the code itself. However, this limits the number of contributors to the blog. I think the CMS should open up opportunities for other people to write for it and Ghost CMS will do that. It also has support for Next.js to provide headless CMS content so we can continue to use the JAM stack and get excellent performance.

Todos

These changes will take place over a series of steps. First, move the project over to Next.js and build out the current pages we use.

Problem

The project used my own css framework. It should be updated to use TailwindCSS.

Depends On

#84

Design

Acceptance Criteria

• [] Home page looks like v1 home page
• [] Uses TailwindCSS
• [] Is mobile responsive
• [] Hook up email

Issue lives here: https://nativesintech.org/awesome/ https://nativesintech.org/awesome/

Error message: Sorry, there was an error: Expected field 'data',[object Response]

(still learning how to contribute, and work with issues, so please let me know if there's a better way to address or collaborate!)