If you're reading this, first off I want to thank you for taking the time to check out my repo. I'm currently in the process of designing and building my developer portfolio site for which this is the code repository.
I have opted to design in browser, since I don't have much experience designing in a tool like Figma. Also, while I may have started my career as a web designer, I haven't truly designed much in the past decade as I focused primarily on UI/UX development.
Therefore, much of what you'll see on the live URL at patrickalcisto.dev is a part of my design process and may not look the same the next time you visit the site. I am taking advantage of this time to learn new tools and techniques to improve my skills and while reinforcing my existing knowledge and skillset.
So please, sit back have a drink and follow me on this journey. Who knows, maybe I'll settle on a couple different designs and implement a way to switch between both.
If you're still reading this, then I appreciate your patience and interest in what I do and hope you enjoy what you see.
Cheers, Patrick
Here's a list of a few things I'm trying out:
- Astro
- Netlify
- Responsive design w/ Tailwindscss
- Improving/sharpening my design skills
The motivation for this stack is based around performance in an effort to deliver an excellent user experience for visitors of this site. A second motivation of learning new things impacted my decision-making with some of the tech, such as Astro and TailwindCSS.
I had never used Astro prior to his project and had heard and read great things that intrigued me. So far I'm REALLY enjoying it -- so easy to get started and all of the integrations make many things a breeze! As for TailwindCSS, I have used it on a couple of prior projects but never really felt like I had as solid of a grasp of tool as I'd like to have. So this project was mostly an exercise of practice and becoming more deeply familiar with it's various concepts and conventions.
Furthermore, my performance based decisions include the utilization of woff2
fonts due to their improved compression over woff
and it's great browser support. The images have been optimized using TinyPNG (yes... I know Astro has image optimization built-in, but I've used TinyPNG for years and it's my go-to/habitual choice when I need to quickly optimize a few images, plus I figured I'd save the time of learning Astro's image optimization for another North Carolina rainy day of which there are many). SVGOMG handles all SVG optimization duties.
- Astro
- React
- TailwindCSS
- Netlify
Big thanks to @ladddesign for the beautiful font, Config Rounded.
This is a bare-bones Astro project that has everything you need to quickly deploy it to Netlify.
Hate reading, here's a video: https://youtu.be/SknFflQVOys!
Love reading, here's blog post: www.netlify.app/blog/deploy-your-astro-project-fast/!
- Quick Setup + Deploy Option
- Regular Setup
- Astro + Netlify Resources
- Project Structure
- Styling
- Commands
- Testing
- Want to learn more?
Click this button and it will help you create a new repo, create a new Netlify project, and deploy!
-
Clone this repo with one of these options:
- Click the 'Use this template' button at the top of the page
- Or via the command line
git clone https://github.com/netlify-templates/astro-quickstart
-
Then install the necessary packages and run the project locally to make sure everything works.
npm install npm run dev
Alternatively, you can run this locally with the Netlify CLI's by running the
netlify dev
command for more options like receiving a live preview to share (netlify dev --live
) and the ability to test Netlify Functions and redirects.
-
Install the Netlify CLI globally
npm install netlify-cli -g
-
Run
npm run build
-
Then use the
netlify deploy
for a deploy preview link ornetlify deploy --prod
to deploy to production
Here are a few other ways you can deploy this template:
- Use the Netlify CLI's create from template command
netlify sites:create-template astro-quickstart
which will create a repo, Netlify project, and deploy it - If you want to utilize continuous deployment through GitHub webhooks, run the Netlify command
netlify init
to create a new project based on your repo ornetlify link
to connect your repo to an existing project
Here are some resources to help you on your Astro + Netlify coding fun!
Hope this template helps :) Happy coding π©π»βπ»!
Inside of your Astro project, you'll see the following folders and files:
/
βββ public/
β βββ favicon.ico
βββ src/
β βββ components/
β β βββ Layout.astro
β βββ pages/
β β βββ index.astro
β βββ style/
β βββ demo-styling.css
βββ package.json
Astro looks for .astro
or .md
files in the src/pages/
directory. Each page is exposed as a route based on its file name.
There's nothing special about src/components/
, but that's where we like to put any Astro/React/Vue/Svelte/Preact components or layouts.
Any static assets, like images, can be placed in the public/
directory.
We've added some modern styling to this template using css within an external stylesheet, this will allow you to easily remove our styling and add in your own.
If you decide that you want to keep our styling you can review our style notes below.
The variables below give you the ability to change the gradient colors of the blobs and are interpolated into the URL string of the background-img within the body.
// Controls the blob blur gradient colors within the main tag's svg
--top-right-blur-1: #20c6b7;
--top-right-blur-2: #4d9abf;
--bttm-left-blur-1: #ff5c02;
--bttm-left-blur-2: #ffcdb1;
If you decide that our styling is not for you, all you'll need to do is remove the demo-styling.css file.
All commands are run from the root of the project, from a terminal:
Command | Action |
---|---|
npm install |
Installs dependencies |
npm run dev |
Starts local dev server at localhost:3000 |
npm run build |
Build your production site to ./dist/ |
npm run preview |
Preview your build locally, before deploying |
Weβve included some tooling that helps us maintain these templates. This template currently uses:
- Renovate - to regularly update our dependencies
- Cypress - to run tests against how the template runs in the browser
- Cypress Netlify Build Plugin - to run our tests during our build process
If your team is not interested in this tooling, you can remove them with ease!
In order to keep our project up-to-date with dependencies we use a tool called Renovate. If youβre not interested in this tooling, delete the renovate.json
file and commit that onto your main branch.
For our testing, we use Cypress for end-to-end testing. This makes sure that we can validate that our templates are rendering and displaying as weβd expect. By default, we have Cypress not generate deploy links if our tests donβt pass. If youβd like to keep Cypress and still generate the deploy links, go into your netlify.toml
and delete the plugin configuration lines:
[[plugins]]
package = "netlify-plugin-cypress"
- [plugins.inputs.postBuild]
- enable = true
-
- [plugins.inputs]
- enable = false
If youβd like to remove the netlify-plugin-cypress
build plugin entirely, youβd need to delete the entire block above instead. And then make sure sure to remove the package from the dependencies using:
npm uninstall -D netlify-plugin-cypress
And lastly if youβd like to remove Cypress entirely, delete the entire cypress
folder and the cypress.config.ts
file. Then remove the dependency using:
npm uninstall cypress
Feel free to check our documentation or jump into our Discord server.