testing deploy to cloudflare for wip branch
This commit is contained in:
parent
cffbfd3121
commit
19881c7ffd
|
|
@ -17,7 +17,8 @@
|
|||
"open-props": "^1.3.9"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@11ty/eleventy": "3.0.0-alpha.4"
|
||||
"@11ty/eleventy": "3.0.0-alpha.4",
|
||||
"lightningcss-cli": "^1.24.0"
|
||||
}
|
||||
},
|
||||
"node_modules/@11ty/dependency-tree": {
|
||||
|
|
@ -1345,6 +1346,229 @@
|
|||
"node": ">=6"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli/-/lightningcss-cli-1.24.0.tgz",
|
||||
"integrity": "sha512-doj/5w6LlZUjDDg3RCRKwTu5duQCrKEHGL8DXLi0rEau58aehmKgf2dfj+9zshCkJTj+a+OpHDyPU1J2GO/aBg==",
|
||||
"dev": true,
|
||||
"hasInstallScript": true,
|
||||
"dependencies": {
|
||||
"detect-libc": "^1.0.3"
|
||||
},
|
||||
"bin": {
|
||||
"lightningcss": "lightningcss"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
},
|
||||
"optionalDependencies": {
|
||||
"lightningcss-cli-darwin-arm64": "1.24.0",
|
||||
"lightningcss-cli-darwin-x64": "1.24.0",
|
||||
"lightningcss-cli-freebsd-x64": "1.24.0",
|
||||
"lightningcss-cli-linux-arm-gnueabihf": "1.24.0",
|
||||
"lightningcss-cli-linux-arm64-gnu": "1.24.0",
|
||||
"lightningcss-cli-linux-arm64-musl": "1.24.0",
|
||||
"lightningcss-cli-linux-x64-gnu": "1.24.0",
|
||||
"lightningcss-cli-linux-x64-musl": "1.24.0",
|
||||
"lightningcss-cli-win32-x64-msvc": "1.24.0"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-darwin-arm64": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-darwin-arm64/-/lightningcss-cli-darwin-arm64-1.24.0.tgz",
|
||||
"integrity": "sha512-ryzm4Sc0JP4Dsz3L6GLpVCd8UQD5dY/skMy5WXIIMpMX+YwNfm02vgAwjddk3y0zENCHVyY/K0cnszVvhK65uQ==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"darwin"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-darwin-x64": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-darwin-x64/-/lightningcss-cli-darwin-x64-1.24.0.tgz",
|
||||
"integrity": "sha512-CmJSNmKwfFIbzbK0TBQpJsnEYczed8Y9U5hFGSxVE4CTcQXFAJXvMbj5ST4lv/VxcnvyfyJNPl78cfUfA24M/Q==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"darwin"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-freebsd-x64": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-freebsd-x64/-/lightningcss-cli-freebsd-x64-1.24.0.tgz",
|
||||
"integrity": "sha512-c/qRQahVMq5T+N9p6ct01QN2PZfM65Kxc91EQGSvBmYVDBJK8Z/EOIwu11F6asNbe7V/2OCTmAa29if5lXl9RA==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"freebsd"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-linux-arm-gnueabihf": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-linux-arm-gnueabihf/-/lightningcss-cli-linux-arm-gnueabihf-1.24.0.tgz",
|
||||
"integrity": "sha512-JebGRmOMfestjpu/74LgvzLC6blzNQjL2PeUpz43d5O/WT0ssaygZuo6VqzZt3nYGW0NueZQwWIMSyryh3LW0A==",
|
||||
"cpu": [
|
||||
"arm"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"linux"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-linux-arm64-gnu": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-linux-arm64-gnu/-/lightningcss-cli-linux-arm64-gnu-1.24.0.tgz",
|
||||
"integrity": "sha512-0Q6WflV2Q+Y0TjkBbegt/2oQbyFhpERMiR3YcoLaulUN/pnesCKmlC08cPDQ/vX5xQF9Y9sYHcd2QXs2cLhpMA==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"linux"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-linux-arm64-musl": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-linux-arm64-musl/-/lightningcss-cli-linux-arm64-musl-1.24.0.tgz",
|
||||
"integrity": "sha512-m1mi/+TaVFZ44l9pMfMn3u1soZOINdljJ8bCUWN+cqeOyZrNY8hUIy7dZXd+HWkrdzUaMYjdzlgEV0PB7wwSBA==",
|
||||
"cpu": [
|
||||
"arm64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"linux"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-linux-x64-gnu": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-linux-x64-gnu/-/lightningcss-cli-linux-x64-gnu-1.24.0.tgz",
|
||||
"integrity": "sha512-4SL/ogzO9iVK6fHEZ7qaCrKgZck3uFJFAPOEKYbA7d+lzByiOG+e9tW/8t+JpbNHu693X32u502AG9ZyXrxurg==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"linux"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-linux-x64-musl": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-linux-x64-musl/-/lightningcss-cli-linux-x64-musl-1.24.0.tgz",
|
||||
"integrity": "sha512-u7lgtntJZH/8AWwT5+TBS3fj2OO/tcYJsrxZHzWumz7UaT6Etogh9Vehzlxb/U9yUl/yfeAfLQp93g0nM7ZyaA==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"linux"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli-win32-x64-msvc": {
|
||||
"version": "1.24.0",
|
||||
"resolved": "https://registry.npmjs.org/lightningcss-cli-win32-x64-msvc/-/lightningcss-cli-win32-x64-msvc-1.24.0.tgz",
|
||||
"integrity": "sha512-i90UzVhYMwYYKQQqkjsGv6whr2RHuBFPzh4k9N8sg+jI5JwskXAnSBattQPCt+lICJoaBdT0gBSRvepGUMVf4w==",
|
||||
"cpu": [
|
||||
"x64"
|
||||
],
|
||||
"dev": true,
|
||||
"optional": true,
|
||||
"os": [
|
||||
"win32"
|
||||
],
|
||||
"engines": {
|
||||
"node": ">= 12.0.0"
|
||||
},
|
||||
"funding": {
|
||||
"type": "opencollective",
|
||||
"url": "https://opencollective.com/parcel"
|
||||
}
|
||||
},
|
||||
"node_modules/lightningcss-cli/node_modules/detect-libc": {
|
||||
"version": "1.0.3",
|
||||
"resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-1.0.3.tgz",
|
||||
"integrity": "sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==",
|
||||
"dev": true,
|
||||
"bin": {
|
||||
"detect-libc": "bin/detect-libc.js"
|
||||
},
|
||||
"engines": {
|
||||
"node": ">=0.10"
|
||||
}
|
||||
},
|
||||
"node_modules/linkify-it": {
|
||||
"version": "5.0.0",
|
||||
"resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-5.0.0.tgz",
|
||||
|
|
|
|||
|
|
@ -17,7 +17,8 @@
|
|||
"author": "Robert McGovern",
|
||||
"license": "ISC",
|
||||
"devDependencies": {
|
||||
"@11ty/eleventy": "3.0.0-alpha.4"
|
||||
"@11ty/eleventy": "3.0.0-alpha.4",
|
||||
"lightningcss-cli": "^1.24.0"
|
||||
},
|
||||
"dependencies": {
|
||||
"@11ty/eleventy-img": "^3.1.8",
|
||||
|
|
|
|||
|
|
@ -0,0 +1,16 @@
|
|||
# Avoid accidental upload of the Sketch and Figma design files
|
||||
#####################################################
|
||||
## Please do not remove lines 5 and 6 - thanks! 🙂 ##
|
||||
#####################################################
|
||||
*.sketch
|
||||
*.fig
|
||||
|
||||
# Avoid accidental XD upload if you convert the design file
|
||||
###############################################
|
||||
## Please do not remove line 12 - thanks! 🙂 ##
|
||||
###############################################
|
||||
*.xd
|
||||
|
||||
# Avoid your project being littered with annoying .DS_Store files!
|
||||
.DS_Store
|
||||
.prettierignore
|
||||
|
|
@ -0,0 +1,163 @@
|
|||
>>> How would I use async JavaScript to access this api https://dj.tdn.wf/products/1
|
||||
To access an API using async JavaScript, you can utilize the Fetch API, which provides a modern and powerful way to perform HTTP requests in JavaScript. Here's how you
|
||||
can use the Fetch API to retrieve data from the provided API:
|
||||
|
||||
```javascript
|
||||
const url = "https://dj.tdn.wf/products/1";
|
||||
|
||||
async function fetchData(url) {
|
||||
try {
|
||||
const response = await fetch(url);
|
||||
|
||||
if (!response.ok) {
|
||||
throw new Error(`Error: HTTP status ${response.status} - ${response.statusText}`);
|
||||
}
|
||||
|
||||
return response.json();
|
||||
} catch (error) {
|
||||
console.error("An error occurred while fetching data:", error);
|
||||
}
|
||||
}
|
||||
|
||||
fetchData(url).then((data) => {
|
||||
console.log("Fetched data:", data);
|
||||
}).catch((error) => {
|
||||
console.error("Error accessing API:", error);
|
||||
});
|
||||
```
|
||||
|
||||
In the code snippet above, we define an `async` function called `fetchData` that takes a URL as its parameter and uses the Fetch API to retrieve data from that URL. The
|
||||
response is then parsed as JSON using the `response.json()` method. If an error occurs during the fetch or parsing process, it will be caught and handled in the
|
||||
try/catch block.
|
||||
|
||||
To use this function, you can call `fetchData(url)`, where `url` is the URL of the API endpoint you want to access. The result will be logged to the console, or any
|
||||
errors that occur during the request will also be logged.
|
||||
|
||||
>>> Thank you, that worked perfectly.
|
||||
You're welcome! I'm glad to hear that the code snippet helped you access the API successfully. If you have any more questions or need further assistance with JavaScript
|
||||
or other programming-related topics, feel free to ask. I'm here to help!
|
||||
|
||||
>>> /?
|
||||
Available Commands:
|
||||
/set Set session variables
|
||||
/show Show model information
|
||||
/load <model> Load a session or model
|
||||
/save <model> Save your current session
|
||||
/bye Exit
|
||||
/?, /help Help for a command
|
||||
/? shortcuts Help for keyboard shortcuts
|
||||
|
||||
Use """ to begin a multi-line message.
|
||||
|
||||
>>> /? shortcuts
|
||||
Available keyboard shortcuts:
|
||||
Ctrl + a Move to the beginning of the line (Home)
|
||||
Ctrl + e Move to the end of the line (End)
|
||||
Alt + b Move back (left) one word
|
||||
Alt + f Move forward (right) one word
|
||||
Ctrl + k Delete the sentence after the cursor
|
||||
Ctrl + u Delete the sentence before the cursor
|
||||
|
||||
Ctrl + l Clear the screen
|
||||
Ctrl + c Stop the model from responding
|
||||
Ctrl + d Exit ollama (/bye)
|
||||
|
||||
>>> What programming languages can you write code for?
|
||||
As an AI language model, I am proficient in a wide range of programming and scripting languages, including but not limited to:
|
||||
|
||||
1. Python
|
||||
2. JavaScript
|
||||
3. Java
|
||||
4. C/C++
|
||||
5. PHP
|
||||
6. Ruby
|
||||
7. HTML/CSS/DOM manipulation
|
||||
8. SQL (for database-related tasks)
|
||||
|
||||
I can write code snippets, functions, classes, or entire applications in these languages, as well as help you with syntax, semantics, and best practices for each
|
||||
language. If you have any specific questions or need assistance with a particular programming problem, feel free to ask!
|
||||
|
||||
>>> Whats your level of Swift & SwiftUI knowledge?
|
||||
While I am proficient in many programming languages, my ability to write code and provide insights for Apple's Swift language is limited. However, I can still assist
|
||||
with general concepts related to Swift and SwiftUI and provide guidance on algorithmic and design-related questions. If you have specific questions or issues related to
|
||||
Swift or SwiftUI, feel free to ask, and I'll do my best to help.
|
||||
|
||||
>>> Is there an AI model you would recommend for Swift & SwiftUI?
|
||||
While I can provide guidance on algorithmic and design-related questions in the context of Swift and SwiftUI, I am not a specialized AI model specifically designed for
|
||||
these technologies. There are several online communities, forums, and resources where you can find experts who can help with your Swift and SwiftUI questions:
|
||||
|
||||
1. Stack Overflow (https://stackoverflow.com/): A popular question-and-answer platform where developers from around the world share their knowledge and expertise on
|
||||
various programming languages and technologies, including Swift and SwiftUI.
|
||||
2. Reddit (https://www.reddit.com/r/swift/ & https://www.reddit.com/r/swiftui/): Online communities where you can ask questions and receive answers from experienced
|
||||
developers.
|
||||
3. Apple Developer Forums (https://developer.apple.com/forums/): A community forum hosted by Apple, where you can discuss Swift, SwiftUI, and related topics with other
|
||||
developers and Apple experts.
|
||||
4. GitHub: Explore open-source projects built using Swift and SwiftUI to learn from real-world code examples.
|
||||
|
||||
You may also find helpful AI models that specialize in specific domains or technologies by visiting platforms like OpenAI's Playground
|
||||
(https://beta.openai.com/playground) or using APIs provided by language models such as GPT-3.
|
||||
|
||||
>>> Thanks for the suggestions. I already do some Swift & SwiftUI programming, and just wanted to evaluate the sort of code an AI Model might generate. Likewise with HTML/CS
|
||||
... S/JS/DOM
|
||||
I understand your curiosity about how an AI model might approach generating code in various languages. While I can't directly demonstrate what a specific AI model would
|
||||
produce for Swift, SwiftUI, or other web technologies like HTML, CSS, JavaScript, and DOM manipulation, I can offer some insights into the general approach of AI
|
||||
models:
|
||||
|
||||
1. The AI model learns from vast amounts of data, including code snippets, patterns, and best practices in the respective languages.
|
||||
2. When prompted with a specific problem or task, the AI model uses its learned knowledge to generate code that addresses the problem or achieves the desired outcome.
|
||||
3. The quality and effectiveness of the generated code depend on several factors, including the complexity of the problem, the breadth and depth of the model's training
|
||||
data, and the alignment between the model's strengths and the specific task at hand.
|
||||
|
||||
In practice, an AI model might generate code that is syntactically correct but lacks the nuance or optimization of a human-written solution. The generated code may also
|
||||
contain errors or inefficiencies, which would require a developer to review, refine, and test before deploying.
|
||||
|
||||
Ultimately, while AI models can be helpful for generating initial ideas or solutions, they are not a replacement for the expertise, judgment, and critical thinking of
|
||||
human developers.
|
||||
|
||||
>>> Understood. Thank you. Do you feel confident you could provide test coverage for JavaScript code?
|
||||
Yes, I can assist with designing unit tests for JavaScript functions and help ensure adequate test coverage to verify the correctness and stability of your code. Unit
|
||||
testing is an essential part of the software development process as it helps catch bugs early, improves code quality, and facilitates refactoring. Here's a general
|
||||
approach to writing unit tests for JavaScript code:
|
||||
|
||||
1. Identify the components (functions, classes, modules) that you want to test. Break down each component into smaller pieces, if necessary, to enable comprehensive
|
||||
testing.
|
||||
2. For each component, define its expected behavior in terms of inputs and outputs, or preconditions and postconditions. This will help guide your test cases and
|
||||
determine the desired results for each input.
|
||||
3. Write unit tests for each identified component, using a JavaScript testing framework such as Jest, Mocha, or QUnit. These frameworks provide assertion libraries that
|
||||
allow you to verify whether the actual output of a function matches the expected result.
|
||||
4. Create test cases that exercise the boundary conditions and edge cases of your components. This includes handling null or undefined inputs, testing for correct error
|
||||
messages, and ensuring the expected behavior in both synchronous and asynchronous scenarios.
|
||||
5. Run the tests regularly during development to ensure that any new changes or modifications do not break existing functionality.
|
||||
|
||||
While I can help you design unit tests and guide you through the process, it's essential to understand that testing is a human-driven activity that requires critical
|
||||
thinking and understanding of the code being tested.
|
||||
|
||||
>>> Send a message (/? for help)
|
||||
|
||||
>>> Indeed, but the assistance would be appreciated. For instance at the beginning of this chat you proposed a funtion "function fetchData(url)", what test would you write to
|
||||
... ensure that the passed in url is a real url or at least correctly formed
|
||||
To test whether the passed-in `url` is well-formed, we can create a unit test case for the `fetchData` function. The following example demonstrates how you could write
|
||||
such a test using Jest, a popular JavaScript testing framework:
|
||||
```javascript
|
||||
const fetchData = require('./fetchData'); // Assuming 'fetchData' function is in a separate file named 'fetchData.js'
|
||||
|
||||
test('Check if the passed URL is well-formed', () => {
|
||||
const validUrls = [
|
||||
'https://www.example.com/products/1',
|
||||
'http://example.org/products?category=electronics',
|
||||
'//example.net/products#top_rated', // An absolute URL with no scheme (e.g., "//example.net") is considered equivalent to "http://example.net"
|
||||
];
|
||||
|
||||
validUrls.forEach((url) => {
|
||||
expect(fetchData(url)).resolves.toBeDefined();
|
||||
});
|
||||
});
|
||||
```
|
||||
In this test case, we're using the `expect()` method provided by Jest to assert that calling `fetchData` with a well-formed URL resolves to any value
|
||||
(`.resolves.toBeDefined()`) instead of rejecting or throwing an error.
|
||||
|
||||
This is just one aspect of testing for the `fetchData` function, and you would need more comprehensive tests to ensure all aspects of its behavior are covered.
|
||||
|
||||
>>> Well time for me to go to sleep, its rather late. Thank you for your assistance (and please excuse any spelling mistakes)
|
||||
You're welcome! It was my pleasure to assist you today. I'm always here if you have more questions or need help with JavaScript or other programming-related topics.
|
||||
Sleep well, and I hope you have a great day tomorrow!
|
||||
|
|
@ -0,0 +1,89 @@
|
|||
# Frontend Mentor - Recipe page
|
||||
|
||||
|
||||
|
||||
## Welcome! 👋
|
||||
|
||||
Thanks for checking out this front-end coding challenge.
|
||||
|
||||
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.
|
||||
|
||||
**To do this challenge, you need a basic understanding of HTML and CSS.**
|
||||
|
||||
## The challenge
|
||||
|
||||
Your challenge is to build out this recipe page and get it looking as close to the design as possible.
|
||||
|
||||
You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.
|
||||
|
||||
Want some support on the challenge? [Join our community](https://www.frontendmentor.io/community) and ask questions in the **#help** channel.
|
||||
|
||||
## Where to find everything
|
||||
|
||||
Your task is to build out the project to the designs inside the `/design` folder. You will find both a mobile and a desktop version of the design.
|
||||
|
||||
The designs are in JPG static format. Using JPGs will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`.
|
||||
|
||||
If you would like the design files (we provide Sketch & Figma versions) to inspect the design in more detail, you can [subscribe as a PRO member](https://www.frontendmentor.io/pro).
|
||||
|
||||
All the required assets for this project are in the `/assets` folder. The images are already exported for the correct screen size and optimized.
|
||||
|
||||
We also include variable and static font files for the required fonts for this project. You can choose to either link to Google Fonts or use the local font files to host the fonts yourself. Note that we've removed the static font files for the font weights that aren't needed for this project.
|
||||
|
||||
There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts.
|
||||
|
||||
## Building your project
|
||||
|
||||
Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:
|
||||
|
||||
1. Initialize your project as a public repository on [GitHub](https://github.com/). Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, [have a read-through of this Try Git resource](https://try.github.io/).
|
||||
2. Configure your repository to publish your code to a web address. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, and we provide some recommendations below.
|
||||
3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes to create reusable styles.
|
||||
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
|
||||
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
|
||||
6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
|
||||
|
||||
## Deploying your project
|
||||
|
||||
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
||||
|
||||
- [GitHub Pages](https://pages.github.com/)
|
||||
- [Vercel](https://vercel.com/)
|
||||
- [Netlify](https://www.netlify.com/)
|
||||
|
||||
You can host your site using one of these solutions or any of our other trusted providers. [Read more about our recommended and trusted hosts](https://medium.com/frontend-mentor/frontend-mentor-trusted-hosting-providers-bf000dfebe).
|
||||
|
||||
## Create a custom `README.md`
|
||||
|
||||
We strongly recommend overwriting this `README.md` with a custom one. We've provided a template inside the [`README-template.md`](./README-template.md) file in this starter code.
|
||||
|
||||
The template provides a guide for what to add. A custom `README` will help you explain your project and reflect on your learnings. Please feel free to edit our template as much as you like.
|
||||
|
||||
Once you've added your information to the template, delete this file and rename the `README-template.md` file to `README.md`. That will make it show up as your repository's README file.
|
||||
|
||||
## Submitting your solution
|
||||
|
||||
Submit your solution on the platform for the rest of the community to see. Follow our ["Complete guide to submitting solutions"](https://medium.com/frontend-mentor/a-complete-guide-to-submitting-solutions-on-frontend-mentor-ac6384162248) for tips on how to do this.
|
||||
|
||||
Remember, if you're looking for feedback on your solution, be sure to ask questions when submitting it. The more specific and detailed you are with your questions, the higher the chance you'll get valuable feedback from the community.
|
||||
|
||||
## Sharing your solution
|
||||
|
||||
There are multiple places you can share your solution:
|
||||
|
||||
1. Share your solution page in the **#finished-projects** channel of our [community](https://www.frontendmentor.io/community).
|
||||
2. Tweet [@frontendmentor](https://twitter.com/frontendmentor) and mention **@frontendmentor**, including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.
|
||||
3. Share your solution on other social channels like LinkedIn.
|
||||
4. Blog about your experience building your project. Writing about your workflow, technical choices, and talking through your code is a brilliant way to reinforce what you've learned. Great platforms to write on are [dev.to](https://dev.to/), [Hashnode](https://hashnode.com/), and [CodeNewbie](https://community.codenewbie.org/).
|
||||
|
||||
We provide templates to help you share your solution once you've submitted it on the platform. Please do edit them and include specific questions when you're looking for feedback.
|
||||
|
||||
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
||||
|
||||
## Got feedback for us?
|
||||
|
||||
We love receiving feedback! We're always looking to improve our challenges and our platform. So if you have anything you'd like to mention, please email hi[at]frontendmentor[dot]io.
|
||||
|
||||
This challenge is completely free. Please share it with anyone who will find it useful for practice.
|
||||
|
||||
**Have fun building!** 🚀
|
||||
|
|
@ -0,0 +1,104 @@
|
|||
# Frontend Mentor - Recipe page solution
|
||||
|
||||
This is a solution to the [Recipe page challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/recipe-page-KiTsR8QQKm). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
||||
|
||||
## Table of contents
|
||||
|
||||
- [Overview](#overview)
|
||||
- [The challenge](#the-challenge)
|
||||
- [Screenshot](#screenshot)
|
||||
- [Links](#links)
|
||||
- [My process](#my-process)
|
||||
- [Built with](#built-with)
|
||||
- [What I learned](#what-i-learned)
|
||||
- [Continued development](#continued-development)
|
||||
- [Useful resources](#useful-resources)
|
||||
- [Author](#author)
|
||||
- [Acknowledgments](#acknowledgments)
|
||||
|
||||
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
||||
|
||||
## Overview
|
||||
|
||||
### Screenshot
|
||||
|
||||
|
||||
|
||||
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
||||
|
||||
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
||||
|
||||
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
||||
|
||||
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
||||
|
||||
### Links
|
||||
|
||||
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
||||
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
||||
|
||||
## My process
|
||||
|
||||
### Built with
|
||||
|
||||
- Semantic HTML5 markup
|
||||
- CSS custom properties
|
||||
- Flexbox
|
||||
- CSS Grid
|
||||
- Mobile-first workflow
|
||||
- [React](https://reactjs.org/) - JS library
|
||||
- [Next.js](https://nextjs.org/) - React framework
|
||||
- [Styled Components](https://styled-components.com/) - For styles
|
||||
|
||||
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
||||
|
||||
### What I learned
|
||||
|
||||
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
||||
|
||||
To see how you can add code snippets, see below:
|
||||
|
||||
```html
|
||||
<h1>Some HTML code I'm proud of</h1>
|
||||
```
|
||||
```css
|
||||
.proud-of-this-css {
|
||||
color: papayawhip;
|
||||
}
|
||||
```
|
||||
```js
|
||||
const proudOfThisFunc = () => {
|
||||
console.log('🎉')
|
||||
}
|
||||
```
|
||||
|
||||
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
||||
|
||||
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
||||
|
||||
### Continued development
|
||||
|
||||
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
||||
|
||||
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
||||
|
||||
### Useful resources
|
||||
|
||||
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
||||
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
||||
|
||||
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
||||
|
||||
## Author
|
||||
|
||||
- Website - [Add your name here](https://www.your-site.com)
|
||||
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
||||
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
||||
|
||||
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
||||
|
||||
## Acknowledgments
|
||||
|
||||
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
||||
|
||||
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
body {
|
||||
/* -webkit-user-select: none; */
|
||||
/* user-select: none; */
|
||||
/* position: relative; */
|
||||
min-height: 100dvh;
|
||||
|
||||
/* ! TEMP REMOVE */
|
||||
@media (min-width: 50ch) {
|
||||
height: 1955px;
|
||||
}
|
||||
|
||||
display: grid;
|
||||
place-content: center;
|
||||
|
||||
background-color: var(--off-black);
|
||||
}
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
/* Layer architecture */
|
||||
/* Best practice to put @layer at top of the import file for organization */
|
||||
|
||||
@layer reset, base, properties, typography, theme, layouts, components, utilities;
|
||||
|
||||
/* Base */
|
||||
@import "reset.css" layer(reset);
|
||||
/* @import '../css/base/normalize.css' layer(base); */
|
||||
@import "base.css" layer(base);
|
||||
@import "properties.css" layer(properties);
|
||||
@import "theme.css" layer(theme); /* theme variables */
|
||||
@import "typography.css" layer(typography); /* theme typography */
|
||||
@import "utilities.css" layer(utilities);
|
||||
|
||||
/* Layouts */
|
||||
|
||||
@import "layout.css" layer(layouts);
|
||||
|
||||
/* Components */
|
||||
|
||||
@import "recipe-page.css" layer(components);
|
||||
|
||||
/* ! important */
|
||||
/* ? Question */
|
||||
/* * Note */
|
||||
/* TODO todo */
|
||||
|
|
@ -0,0 +1,105 @@
|
|||
:root {
|
||||
/*! @media doesn't support variables, grr */
|
||||
/* --min-width: 45ch; */
|
||||
|
||||
--border-radius-card: 24px;
|
||||
--border-radius-img: 12px;
|
||||
--border-radius-callout: 12px;
|
||||
}
|
||||
|
||||
main {
|
||||
display: grid;
|
||||
place-content: center;
|
||||
}
|
||||
|
||||
article {
|
||||
outline: orange 10px solid;
|
||||
|
||||
padding: 0px 32px;
|
||||
|
||||
@media (min-width: 50ch) {
|
||||
outline: purple 10px solid;
|
||||
max-width: 46rem;
|
||||
|
||||
padding: 40px;
|
||||
|
||||
border-radius: var(--border-radius-card);
|
||||
}
|
||||
}
|
||||
|
||||
article > * + * {
|
||||
margin-top: 2rem;
|
||||
}
|
||||
|
||||
/* might need grid trick to pop the image out */
|
||||
header {
|
||||
/* width: 100vw; */
|
||||
|
||||
@media (min-width: 50ch) {
|
||||
width: 100%;
|
||||
}
|
||||
}
|
||||
|
||||
header img {
|
||||
margin-bottom: 40px;
|
||||
width: 100%;
|
||||
|
||||
@media (min-width: 50ch) {
|
||||
width: 100%;
|
||||
border-radius: var(--border-radius-img);
|
||||
}
|
||||
}
|
||||
|
||||
ul,
|
||||
ol {
|
||||
/*
|
||||
using inside means you can't adjust
|
||||
the padding of both into position
|
||||
|
||||
ended up searching and coming across this article about it https://css-tricks.com/everything-you-need-to-know-about-the-gap-after-the-list-marker/
|
||||
*/
|
||||
|
||||
/* list-style-position: inside; */
|
||||
padding-inline-start: 24px;
|
||||
}
|
||||
|
||||
li {
|
||||
padding-inline-start: 16px;
|
||||
}
|
||||
|
||||
table {
|
||||
border-collapse: collapse;
|
||||
width: 100%;
|
||||
}
|
||||
|
||||
table > * + * {
|
||||
}
|
||||
|
||||
table > tr > td + td {
|
||||
}
|
||||
|
||||
tbody > tr:first-child > td {
|
||||
padding-top: 24px;
|
||||
}
|
||||
|
||||
tr > * + * {
|
||||
padding-block: 12px;
|
||||
}
|
||||
|
||||
td {
|
||||
border-bottom: 1px solid var(--white-coffee);
|
||||
}
|
||||
|
||||
tr td:first-child {
|
||||
padding-inline-start: 2rem;
|
||||
}
|
||||
|
||||
tr td:last-child {
|
||||
padding-inline-end: 2rem;
|
||||
}
|
||||
|
||||
.preparation {
|
||||
@media (min-width: 50ch) {
|
||||
border-radius: var(--border-radius-callout);
|
||||
}
|
||||
}
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
.emphasized,
|
||||
li::marker {
|
||||
font-weight: var(--fw-700);
|
||||
color: var(--brandy-red);
|
||||
}
|
||||
|
|
@ -0,0 +1,96 @@
|
|||
/*
|
||||
Mixture of different resets
|
||||
|
||||
Josh's Custom CSS Reset
|
||||
https://www.joshwcomeau.com/css/custom-css-reset/
|
||||
|
||||
Kevin Powell
|
||||
*/
|
||||
|
||||
/*
|
||||
1. Use a more-intuitive box-sizing model.
|
||||
*/
|
||||
*,
|
||||
*::before,
|
||||
*::after {
|
||||
box-sizing: border-box;
|
||||
}
|
||||
/*
|
||||
2. Remove default margin & padding
|
||||
*/
|
||||
* {
|
||||
margin: 0;
|
||||
padding: 0;
|
||||
}
|
||||
|
||||
/* Set core root defaults */
|
||||
html {
|
||||
scroll-behavior: smooth;
|
||||
}
|
||||
|
||||
/*
|
||||
Typographic tweaks!
|
||||
3. Add accessible line-height
|
||||
4. Improve text rendering
|
||||
*/
|
||||
body {
|
||||
text-rendering: optimizeSpeed;
|
||||
/* line-height: 1.6; KP */
|
||||
line-height: 1.5;
|
||||
-webkit-font-smoothing: antialiased;
|
||||
}
|
||||
/*
|
||||
5. Improve media defaults
|
||||
*/
|
||||
img,
|
||||
picture,
|
||||
video,
|
||||
canvas,
|
||||
svg {
|
||||
display: block;
|
||||
max-width: 100%;
|
||||
}
|
||||
/*
|
||||
6. Remove built-in form typography styles
|
||||
*/
|
||||
input,
|
||||
button,
|
||||
textarea,
|
||||
select {
|
||||
font: inherit;
|
||||
}
|
||||
/*
|
||||
7. Avoid text overflows
|
||||
*/
|
||||
p,
|
||||
h1,
|
||||
h2,
|
||||
h3,
|
||||
h4,
|
||||
h5,
|
||||
h6 {
|
||||
overflow-wrap: break-word;
|
||||
}
|
||||
/*
|
||||
8. Create a root stacking context
|
||||
*/
|
||||
#root,
|
||||
#__next {
|
||||
isolation: isolate;
|
||||
}
|
||||
|
||||
/* Remove all animations, transitions and smooth scroll for people that prefer not to see them */
|
||||
@media (prefers-reduced-motion: reduce) {
|
||||
html {
|
||||
scroll-behavior: auto;
|
||||
}
|
||||
|
||||
*,
|
||||
*::before,
|
||||
*::after {
|
||||
animation-duration: 0.01ms !important;
|
||||
animation-iteration-count: 1 !important;
|
||||
transition-duration: 0.01ms !important;
|
||||
scroll-behavior: auto !important;
|
||||
}
|
||||
}
|
||||
|
|
@ -0,0 +1,43 @@
|
|||
:root {
|
||||
--dark-charcoal: #312e2c;
|
||||
--dark-raspberry: #7a284e;
|
||||
--brandy-red: #854632;
|
||||
--wenge-brown: #5f564d;
|
||||
--eggshell: #f3e5d7;
|
||||
--white-coffee: #e3ddd7;
|
||||
--snow: #fff7fb;
|
||||
--white: #fff;
|
||||
}
|
||||
|
||||
body {
|
||||
color: var(--wenge-brown);
|
||||
background-color: var(--eggshell);
|
||||
}
|
||||
|
||||
article {
|
||||
background-color: var(--white);
|
||||
}
|
||||
|
||||
h1 {
|
||||
color: var(--dark-charcoal);
|
||||
}
|
||||
|
||||
h2 {
|
||||
color: var(--brandy-red);
|
||||
}
|
||||
|
||||
h3 {
|
||||
color: var(--dark-raspberry);
|
||||
}
|
||||
|
||||
li:before {
|
||||
color: var(--brandy-red);
|
||||
}
|
||||
|
||||
hr {
|
||||
color: var(--white-coffee);
|
||||
}
|
||||
|
||||
.preparation {
|
||||
background-color: var(--snow);
|
||||
}
|
||||
|
|
@ -0,0 +1,68 @@
|
|||
@font-face {
|
||||
font-family: "YoungSerif";
|
||||
src: url("../fonts/young-serif/YoungSerif-Regular.ttf");
|
||||
}
|
||||
|
||||
@font-face {
|
||||
font-family: "Outfit";
|
||||
src: url("../fonts/outfit/Outfit-VariableFont_wght.ttf");
|
||||
}
|
||||
|
||||
:root {
|
||||
/* Font Family */
|
||||
--ff-outfit: "Outfit", sans-serif;
|
||||
--ff-young: "YoungSerif", sans-serif;
|
||||
|
||||
/* Font Weights */
|
||||
--fw-400: 400;
|
||||
--fw-600: 600;
|
||||
--fw-700: 700;
|
||||
|
||||
/* Font Sizes */
|
||||
/* * 36px * 375, 40px @ 1440px */
|
||||
--fs-title: clamp(2.25rem, 2.162rem + 0.3756vi, 2.5rem);
|
||||
--fs-16: 1rem;
|
||||
--fs-20: 1.25rem;
|
||||
--fs-28: 1.75rem;
|
||||
|
||||
--fs-default: var(--fs-16);
|
||||
|
||||
/* Line Heights */
|
||||
--lh-100: 1;
|
||||
--lh-150: 1.5;
|
||||
}
|
||||
|
||||
body,
|
||||
h3 {
|
||||
font-family: var(--ff-outfit);
|
||||
font-size: var(--fs-16);
|
||||
font-weight: var(--fw400);
|
||||
|
||||
line-height: var(--lh-150);
|
||||
}
|
||||
|
||||
h1,
|
||||
h2 {
|
||||
font-weight: var(--fw-400);
|
||||
font-family: var(--ff-young);
|
||||
|
||||
line-height: var(--lh-100);
|
||||
}
|
||||
|
||||
h1 {
|
||||
font-size: var(--fs-title);
|
||||
}
|
||||
|
||||
h2 {
|
||||
font-size: var(--fs-28);
|
||||
}
|
||||
|
||||
h3 {
|
||||
font-weight: var(--fw-600);
|
||||
line-height: var(--lh-100);
|
||||
font-size: var(--fs-20);
|
||||
}
|
||||
|
||||
li > span {
|
||||
font-weight: var(--fw-700);
|
||||
}
|
||||
|
|
@ -0,0 +1 @@
|
|||
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
Copyright 2021 The Outfit Project Authors (https://github.com/Outfitio/Outfit-Fonts)
|
||||
|
||||
This Font Software is licensed under the SIL Open Font License, Version 1.1.
|
||||
This license is copied below, and is also available with a FAQ at:
|
||||
http://scripts.sil.org/OFL
|
||||
|
||||
|
||||
-----------------------------------------------------------
|
||||
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
|
||||
-----------------------------------------------------------
|
||||
|
||||
PREAMBLE
|
||||
The goals of the Open Font License (OFL) are to stimulate worldwide
|
||||
development of collaborative font projects, to support the font creation
|
||||
efforts of academic and linguistic communities, and to provide a free and
|
||||
open framework in which fonts may be shared and improved in partnership
|
||||
with others.
|
||||
|
||||
The OFL allows the licensed fonts to be used, studied, modified and
|
||||
redistributed freely as long as they are not sold by themselves. The
|
||||
fonts, including any derivative works, can be bundled, embedded,
|
||||
redistributed and/or sold with any software provided that any reserved
|
||||
names are not used by derivative works. The fonts and derivatives,
|
||||
however, cannot be released under any other type of license. The
|
||||
requirement for fonts to remain under this license does not apply
|
||||
to any document created using the fonts or their derivatives.
|
||||
|
||||
DEFINITIONS
|
||||
"Font Software" refers to the set of files released by the Copyright
|
||||
Holder(s) under this license and clearly marked as such. This may
|
||||
include source files, build scripts and documentation.
|
||||
|
||||
"Reserved Font Name" refers to any names specified as such after the
|
||||
copyright statement(s).
|
||||
|
||||
"Original Version" refers to the collection of Font Software components as
|
||||
distributed by the Copyright Holder(s).
|
||||
|
||||
"Modified Version" refers to any derivative made by adding to, deleting,
|
||||
or substituting -- in part or in whole -- any of the components of the
|
||||
Original Version, by changing formats or by porting the Font Software to a
|
||||
new environment.
|
||||
|
||||
"Author" refers to any designer, engineer, programmer, technical
|
||||
writer or other person who contributed to the Font Software.
|
||||
|
||||
PERMISSION & CONDITIONS
|
||||
Permission is hereby granted, free of charge, to any person obtaining
|
||||
a copy of the Font Software, to use, study, copy, merge, embed, modify,
|
||||
redistribute, and sell modified and unmodified copies of the Font
|
||||
Software, subject to the following conditions:
|
||||
|
||||
1) Neither the Font Software nor any of its individual components,
|
||||
in Original or Modified Versions, may be sold by itself.
|
||||
|
||||
2) Original or Modified Versions of the Font Software may be bundled,
|
||||
redistributed and/or sold with any software, provided that each copy
|
||||
contains the above copyright notice and this license. These can be
|
||||
included either as stand-alone text files, human-readable headers or
|
||||
in the appropriate machine-readable metadata fields within text or
|
||||
binary files as long as those fields can be easily viewed by the user.
|
||||
|
||||
3) No Modified Version of the Font Software may use the Reserved Font
|
||||
Name(s) unless explicit written permission is granted by the corresponding
|
||||
Copyright Holder. This restriction only applies to the primary font name as
|
||||
presented to the users.
|
||||
|
||||
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
|
||||
Software shall not be used to promote, endorse or advertise any
|
||||
Modified Version, except to acknowledge the contribution(s) of the
|
||||
Copyright Holder(s) and the Author(s) or with their explicit written
|
||||
permission.
|
||||
|
||||
5) The Font Software, modified or unmodified, in part or in whole,
|
||||
must be distributed entirely under this license, and must not be
|
||||
distributed under any other license. The requirement for fonts to
|
||||
remain under this license does not apply to any document created
|
||||
using the Font Software.
|
||||
|
||||
TERMINATION
|
||||
This license becomes null and void if any of the above conditions are
|
||||
not met.
|
||||
|
||||
DISCLAIMER
|
||||
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
||||
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
|
||||
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
|
||||
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
|
||||
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
||||
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
|
||||
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
||||
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
|
||||
OTHER DEALINGS IN THE FONT SOFTWARE.
|
||||
Binary file not shown.
|
|
@ -0,0 +1,71 @@
|
|||
Outfit Variable Font
|
||||
====================
|
||||
|
||||
This download contains Outfit as both a variable font and static fonts.
|
||||
|
||||
Outfit is a variable font with this axis:
|
||||
wght
|
||||
|
||||
This means all the styles are contained in a single file:
|
||||
Outfit-VariableFont_wght.ttf
|
||||
|
||||
If your app fully supports variable fonts, you can now pick intermediate styles
|
||||
that aren’t available as static fonts. Not all apps support variable fonts, and
|
||||
in those cases you can use the static font files for Outfit:
|
||||
static/Outfit-Thin.ttf
|
||||
static/Outfit-ExtraLight.ttf
|
||||
static/Outfit-Light.ttf
|
||||
static/Outfit-Regular.ttf
|
||||
static/Outfit-Medium.ttf
|
||||
static/Outfit-SemiBold.ttf
|
||||
static/Outfit-Bold.ttf
|
||||
static/Outfit-ExtraBold.ttf
|
||||
static/Outfit-Black.ttf
|
||||
|
||||
Get started
|
||||
-----------
|
||||
|
||||
1. Install the font files you want to use
|
||||
|
||||
2. Use your app's font picker to view the font family and all the
|
||||
available styles
|
||||
|
||||
Learn more about variable fonts
|
||||
-------------------------------
|
||||
|
||||
https://developers.google.com/web/fundamentals/design-and-ux/typography/variable-fonts
|
||||
https://variablefonts.typenetwork.com
|
||||
https://medium.com/variable-fonts
|
||||
|
||||
In desktop apps
|
||||
|
||||
https://theblog.adobe.com/can-variable-fonts-illustrator-cc
|
||||
https://helpx.adobe.com/nz/photoshop/using/fonts.html#variable_fonts
|
||||
|
||||
Online
|
||||
|
||||
https://developers.google.com/fonts/docs/getting_started
|
||||
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Fonts/Variable_Fonts_Guide
|
||||
https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/variable-fonts
|
||||
|
||||
Installing fonts
|
||||
|
||||
MacOS: https://support.apple.com/en-us/HT201749
|
||||
Linux: https://www.google.com/search?q=how+to+install+a+font+on+gnu%2Blinux
|
||||
Windows: https://support.microsoft.com/en-us/help/314960/how-to-install-or-remove-a-font-in-windows
|
||||
|
||||
Android Apps
|
||||
|
||||
https://developers.google.com/fonts/docs/android
|
||||
https://developer.android.com/guide/topics/ui/look-and-feel/downloadable-fonts
|
||||
|
||||
License
|
||||
-------
|
||||
Please read the full license text (OFL.txt) to understand the permissions,
|
||||
restrictions and requirements for usage, redistribution, and modification.
|
||||
|
||||
You can use them in your products & projects – print or digital,
|
||||
commercial or otherwise.
|
||||
|
||||
This isn't legal advice, please consider consulting a lawyer and see the full
|
||||
license for all details.
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
|
@ -0,0 +1,93 @@
|
|||
Copyright 2023 The Young Serif Project Authors (https://github.com/noirblancrouge/YoungSerif)
|
||||
|
||||
This Font Software is licensed under the SIL Open Font License, Version 1.1.
|
||||
This license is copied below, and is also available with a FAQ at:
|
||||
http://scripts.sil.org/OFL
|
||||
|
||||
|
||||
-----------------------------------------------------------
|
||||
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
|
||||
-----------------------------------------------------------
|
||||
|
||||
PREAMBLE
|
||||
The goals of the Open Font License (OFL) are to stimulate worldwide
|
||||
development of collaborative font projects, to support the font creation
|
||||
efforts of academic and linguistic communities, and to provide a free and
|
||||
open framework in which fonts may be shared and improved in partnership
|
||||
with others.
|
||||
|
||||
The OFL allows the licensed fonts to be used, studied, modified and
|
||||
redistributed freely as long as they are not sold by themselves. The
|
||||
fonts, including any derivative works, can be bundled, embedded,
|
||||
redistributed and/or sold with any software provided that any reserved
|
||||
names are not used by derivative works. The fonts and derivatives,
|
||||
however, cannot be released under any other type of license. The
|
||||
requirement for fonts to remain under this license does not apply
|
||||
to any document created using the fonts or their derivatives.
|
||||
|
||||
DEFINITIONS
|
||||
"Font Software" refers to the set of files released by the Copyright
|
||||
Holder(s) under this license and clearly marked as such. This may
|
||||
include source files, build scripts and documentation.
|
||||
|
||||
"Reserved Font Name" refers to any names specified as such after the
|
||||
copyright statement(s).
|
||||
|
||||
"Original Version" refers to the collection of Font Software components as
|
||||
distributed by the Copyright Holder(s).
|
||||
|
||||
"Modified Version" refers to any derivative made by adding to, deleting,
|
||||
or substituting -- in part or in whole -- any of the components of the
|
||||
Original Version, by changing formats or by porting the Font Software to a
|
||||
new environment.
|
||||
|
||||
"Author" refers to any designer, engineer, programmer, technical
|
||||
writer or other person who contributed to the Font Software.
|
||||
|
||||
PERMISSION & CONDITIONS
|
||||
Permission is hereby granted, free of charge, to any person obtaining
|
||||
a copy of the Font Software, to use, study, copy, merge, embed, modify,
|
||||
redistribute, and sell modified and unmodified copies of the Font
|
||||
Software, subject to the following conditions:
|
||||
|
||||
1) Neither the Font Software nor any of its individual components,
|
||||
in Original or Modified Versions, may be sold by itself.
|
||||
|
||||
2) Original or Modified Versions of the Font Software may be bundled,
|
||||
redistributed and/or sold with any software, provided that each copy
|
||||
contains the above copyright notice and this license. These can be
|
||||
included either as stand-alone text files, human-readable headers or
|
||||
in the appropriate machine-readable metadata fields within text or
|
||||
binary files as long as those fields can be easily viewed by the user.
|
||||
|
||||
3) No Modified Version of the Font Software may use the Reserved Font
|
||||
Name(s) unless explicit written permission is granted by the corresponding
|
||||
Copyright Holder. This restriction only applies to the primary font name as
|
||||
presented to the users.
|
||||
|
||||
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
|
||||
Software shall not be used to promote, endorse or advertise any
|
||||
Modified Version, except to acknowledge the contribution(s) of the
|
||||
Copyright Holder(s) and the Author(s) or with their explicit written
|
||||
permission.
|
||||
|
||||
5) The Font Software, modified or unmodified, in part or in whole,
|
||||
must be distributed entirely under this license, and must not be
|
||||
distributed under any other license. The requirement for fonts to
|
||||
remain under this license does not apply to any document created
|
||||
using the Font Software.
|
||||
|
||||
TERMINATION
|
||||
This license becomes null and void if any of the above conditions are
|
||||
not met.
|
||||
|
||||
DISCLAIMER
|
||||
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
||||
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
|
||||
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
|
||||
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
|
||||
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
||||
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
|
||||
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
||||
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
|
||||
OTHER DEALINGS IN THE FONT SOFTWARE.
|
||||
Binary file not shown.
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 78 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 112 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 77 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 85 KiB |
|
|
@ -0,0 +1,134 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<!-- displays site properly based on user's device -->
|
||||
|
||||
<link rel="icon" type="image/png" sizes="32x32" href="./assets/images/favicon-32x32.png">
|
||||
<link rel="stylesheet" href="./assets/css/index.css">
|
||||
|
||||
<title>Frontend Mentor | Recipe page</title>
|
||||
|
||||
<!-- Feel free to remove these styles or customise in your own stylesheet 👍 -->
|
||||
<style>
|
||||
.attribution {
|
||||
font-size: 11px;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.attribution a {
|
||||
color: hsl(228, 45%, 44%);
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<main>
|
||||
<article>
|
||||
<header>
|
||||
<figure>
|
||||
<img src="./assets/images/image-omelette.jpeg"
|
||||
alt="A folded crepe with on a plate, filled with vegetable matter. Also on the plate is some orange humus">
|
||||
</figure>
|
||||
<h1>Simple Omelette Recipe</h1>
|
||||
<p>An easy and quick dish, perfect for any meal. This classic omelette combines beaten eggs cooked to
|
||||
perfection, optionally filled with your choice of cheese, vegetables, or meats.</p>
|
||||
</header>
|
||||
<section class="preparation">
|
||||
<h3>Preparation time
|
||||
</h3>
|
||||
<ul>
|
||||
<li><span>Total:</span> Approximately 10 minutes
|
||||
</li>
|
||||
<li><span>Preparation:</span> 5 minutes
|
||||
</li>
|
||||
<li><span>Cooking:</span> 5 minutes
|
||||
</li>
|
||||
</ul>
|
||||
</section>
|
||||
<section>
|
||||
<h2>Ingredients
|
||||
</h2>
|
||||
<ul>
|
||||
<li>2-3 large eggs
|
||||
</li>
|
||||
<li>Salt, to taste
|
||||
</li>
|
||||
<li>Pepper, to taste
|
||||
</li>
|
||||
<li>1 tablespoon of butter or oil
|
||||
</li>
|
||||
<li>Optional fillings: cheese, diced vegetables, cooked meats, herbs
|
||||
</li>
|
||||
</ul>
|
||||
</section>
|
||||
<hr>
|
||||
<section>
|
||||
<h2>Instructions
|
||||
</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<span>Beat the eggs:</span> In a bowl, beat the eggs with a pinch of salt and pepper until they are well
|
||||
mixed.
|
||||
You can add a tablespoon of water or milk for a fluffier texture.
|
||||
</li>
|
||||
<li>
|
||||
<span>Heat the pan:</span> Place a non-stick frying pan over medium heat and add butter or oil.
|
||||
</li>
|
||||
<li>
|
||||
<span>Cook the omelette:</span> Once the butter is melted and bubbling, pour in the eggs. Tilt the pan to
|
||||
ensure
|
||||
the eggs evenly coat the surface.
|
||||
</li>
|
||||
<li>
|
||||
<span>Add fillings (optional):</span> When the eggs begin to set at the edges but are still slightly
|
||||
runny in the
|
||||
middle, sprinkle your chosen fillings over one half of the omelette.
|
||||
fillings. Let it cook for another minute, then slide it onto a plate.
|
||||
</li>
|
||||
<li>
|
||||
<span>Fold and serve:</span> As the omelette continues to cook, carefully lift one edge and fold it over
|
||||
the
|
||||
</li>
|
||||
<li>
|
||||
<span>Enjoy:</span> Serve hot, with additional salt and pepper if needed.
|
||||
</li>
|
||||
</ol>
|
||||
</section>
|
||||
<section>
|
||||
<h2>Nutrition</h2>
|
||||
<p>The table below shows nutritional values per serving without the additional fillings.
|
||||
</p>
|
||||
<table>
|
||||
<tr>
|
||||
<td>Calories</td>
|
||||
<td class="emphasized">277kcal</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Carbs</td>
|
||||
<td class="emphasized">0g</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Protein</td>
|
||||
<td class="emphasized">20g</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Fat</td>
|
||||
<td class="emphasized">22g</td>
|
||||
</tr>
|
||||
</table>
|
||||
</section>
|
||||
</article>
|
||||
</main>
|
||||
|
||||
<!-- <div class="attribution">
|
||||
Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank" rel="noopener">Frontend
|
||||
Mentor</a>.
|
||||
Coded by <a href="https://rmcg.dev">Robert McGovern</a>.
|
||||
</div> -->
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,38 @@
|
|||
# Front-end Style Guide
|
||||
|
||||
## Layout
|
||||
|
||||
The designs were created to the following widths:
|
||||
|
||||
- Mobile: 375px
|
||||
- Desktop: 1440px
|
||||
|
||||
## Colors
|
||||
|
||||
### Primary
|
||||
|
||||
- Nutmeg: hsl(14, 45%, 36%)
|
||||
- Dark Raspberry: hsl(332, 51%, 32%)
|
||||
|
||||
### Neutral
|
||||
|
||||
- White: hsl(0, 0%, 100%)
|
||||
- Rose White: hsl(330, 100%, 98%)
|
||||
- Eggshell: hsl(30, 54%, 90%)
|
||||
- Light Grey: hsl(30, 18%, 87%)
|
||||
- Wenge Brown: hsl(30, 10%, 34%)
|
||||
- Dark Charcoal: hsl(24, 5%, 18%)
|
||||
|
||||
## Typography
|
||||
|
||||
### Body Copy
|
||||
|
||||
- Font size (paragraph): 16px
|
||||
|
||||
### Fonts
|
||||
|
||||
- Family: [Young Serif](https://fonts.google.com/specimen/Young+Serif)
|
||||
- Weights: 400
|
||||
|
||||
- Family: [Outfit](https://fonts.google.com/specimen/Outfit)
|
||||
- Weights: 400, 600, 700
|
||||
|
|
@ -0,0 +1,9 @@
|
|||
/** @type {import('tailwindcss').Config} */
|
||||
module.exports = {
|
||||
content: [],
|
||||
theme: {
|
||||
extend: {},
|
||||
},
|
||||
plugins: [],
|
||||
}
|
||||
|
||||
Loading…
Reference in New Issue