social:
- icon: link
icon_pack: fas
link: https://massimilianodiluca.info
- icon: google-scholar
icon_pack: ai
link: https://scholar.google.com/citations?user=93hi3QcAAAAJ&hl=en
- icon: publons
icon_pack: ai
link: https://publons.com/researcher/1170808/massimiliano-di-luca/
- icon: twitter
icon_pack: fab
link: https://twitter.com/maxdiluca
- icon: tree
icon_pack: fas
link: https://neurotree.org/neurotree/peopleinfo.php?pid=6562
- icon: youtube
icon_pack: fab
link: https://youtube.com/playlist?list=PLRBLD3PiUPlzAmKsL7gicIvci2lRXoZah
- icon: linkedin
icon_pack: fab
link: https://www.linkedin.com/in/maxdiluca/
- icon: researchgate
icon_pack: fab
link: https://www.researchgate.net/profile/Massimiliano-Di-Luca
- icon: orcid
icon_pack: fab
link: https://orcid.org/0000-0003-3085-7251
- icon: github
icon_pack: fab
link: https://github.com/maxdiluca
email: "if you want your email to be listed, add it here otherwise leave this empty"
superuser: true
user_groups:
- Principal Investigator / Research assistants / Visitors / Researchers / Students
---
This is the space to write your full bio. It will appear on your personal page.
Instructions for changes to the websites
There are currently four WOWCHEMY- based websites:
, hit “Get started”, select a template and press “start with... →”. Please create an account on Github or connect with your current one, and give a name to the repository. You will then need to create a free account on Netlify. You will receive two emails, one with the SSH key to the GitHub repository, and the other with the invitation to the Netlify project.
More information on how to create content for the website (which is a HUGO template created with Wowchemy and published with Netlify) can be found here
The rest of the guide will be based on the ARME project, but it works in the same way for the other two and for any other Wowchemy website.
First-time setup for making changes to a website
To start working (e.g., add and modify content), you will need a GitHub account, to be added as a ‘contributor’ to the GitHub repository and the GitHub desktop.
or to another owner of the GitHub repository specifying which website you want to contribute to. Once one of the owners has set you up as a ‘contributor’, you can modify the content on GitHub where the code of the website resides (e.g.
To make changes (e.g. adding an entry in the ‘News’), you will need the GitHub Desktop app. For this, the first time you contribute, on the Github repository page (e.g.,
) click the “CODE” button and select “Open with GitHub Desktop”. You will now have a local copy of the code on the Github repository.
Making changes
The GitHub repository does not have HTML code, so you will need to change one of the files in the “content” folder, upload the file on GitHub (”Push”), and Netlify will automatically build the HTML site. You will need a few minutes before seeing any change.
If the icon is not green, a previous contribution did not build correctly. Go to point 13 to diagnose the problem.
In the desktop app, top left, select the repository you want to work on.
In the desktop app, “fetch” the repository and “pull” to get the latest files to reside on your computer (top right button).
In the desktop app, press this button to get to the local repository folder.
Open the “content” folder on the local copy of the repository.
Add or modify content by working on the folder.
For example, the “post” folder holds the news. To create a new entry, duplicate the “template” folder and give the folder another name, change the file index for the text and add pictures in the folder (“featured.jpg” are directly shown without needing to link them)
Once you finish editing files, be sure to change the tag “draft” in the file to “false”.
In the desktop app, “fetch” to check that there are no changes from somebody else (top right button).
In the desktop app, describe the changes made in the “description” box.
In the desktop app, select and deselect any files that you want to be updated.
In the desktop app press “commit” to save the changes you have made
In the desktop app finally “push” the changes on GitHub from your local version (same button top right, has now changed label)
Once the push is finished, refresh the github repository webpage page. The “state” logo on the readme page (with the netlify text) should change from green to yellow and say “building”.
Refresh the github repository and wait until the build process is finished. Check the state logo
- if it goes to green and says “success” the website has been updated and it can be seen if you refresh the live website.
- if it is red and says “error” then there is an error in the syntax of the file you uploaded or modified. Debug info can be seen by clicking the Netlify “state” logo, which will bring you to the deploy page
The last deploy is at the top of the list (in the image it has been successful). If you visualize the log, you will see this:
Scroll down until you see the two red lines. The file containing the error and the type of erro is reported just before them:
In the “search property” top right box, create a new property and select a URL prefix.
Add the URL of the website.
To verify the ownership, use the “HTML tag” method to “Add a meta tag to your site's home page”
Copy the meta tag.
In Netlify, go in the Settings>Site configuration>Build & Deploy>Post Processing>Snippet injection
Check that no other injections about Google console or google-site-verification properties are present, then “Add Snippet” select “before </head>”, name it google-site-verification and paste the snippet you copied.
In Netlify, go on “Deploys” and press “Trigger deploy” selecting “Clear cache and deploy site”.
Once the deploy is finished, go back on google and verify the property.
In Netlify, go in Integration, search sitemap and enable the “Sitemap” and then “install”. Also enable “Send sitemap to Google” and Install.
In Netlify, go on “Deploys” and press “Trigger deploy” selecting “Clear cache and deploy site”.
In Google, check that the sitemap is indexed and readable. Add one if it is not transferred automatically.
Verify your site by adding the search engine’s verification code to your params.yaml: