AEA Polimi on the web

Static site generator for the site of the Politecnico di Milano Automation Engineering Association AEA Polimi, built with React and Gatsby.js.

Creato con React + Gatsby. Per modificarlo installa Node. Qui sotto i comandi di routine da usare avendo l'ambiente pronto e un quickstart per impostare l'ambiente al primo avvio.

Info su React, Gatsby.

🤓 Comandi di routine

0. git pull

   NB: Se git pull restituisce modifiche a package-lock.json uso npm install per verificare che la nuova versione non abbia librerie che io non ho.

1. Modifico il codice

2. npm run develop (per vedere se il sito funziona con le modifiche)

3. git add .

4. git commit -m "Messaggio del commit"

5. git push

6. git push origin master:build (Per pubblicare USARE POCO CHE POI ANDIAMO FUORI DALLA QUOTA GRATIS)

🚀 First start

1. git clone.

   Clona questa repository, sotto esempio con https.

   # clone repo con https
   git clone https://github.com/aeapolimi/aeapolimi.github.io.git

2. yarn install.

   Entra nella repository clonata e installa il necessario richiesto da questa web app.

   # entra nella repository
   cd aea
   # installa
   yarn install

3. Start developing.

   inizia a sviluppare aprendo la development build, si dovrebbe aprire da solo il browser col sito.

   gatsby develop
   # If gatsby develop doesn't work:
   npm run develop

4. Open the source code and start editing!

   Your site is now running at http://localhost:8000!

   Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

   Open the aea directory in your code editor of choice and edit src/components/HomePage.js. Save your changes and the browser will update in real time!

5. Pubblica il sito su Netlify

   Se sei sicuro che tutto vada bene puoi pubblicare la nuova versione del sito con le tue modifiche. Per vedere le modifiche su aeapolimi.github.io potresti dover aspettare cinque minuti.

   git add .
   git commit -m "Messaggio"
   git push
   git push origin master:build

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

9. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

12. README.md: A text file containing useful reference information about your project.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

• For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

• To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

💫 Altri possibili deployment

Nel caso dovessimo finire la quota gratuita o ci dovessero essere altri problemi con netlify possiamo momentaneamente usare la github page aeapolimi.github.io con questo comando:

npm run deploy

Ricorda in caso di aggiornare il dns.