Commit 4f4b0be2 authored by MarijaV's avatar MarijaV
Browse files

Added css file

parent 53969f82
No related merge requests found
Showing with 370 additions and 92 deletions
+370 -92
{
"liveServer.settings.port": 5501
}
\ No newline at end of file
File added
File added
File added
File added
CSS Challenge 01/screenshots/detail-page.png

4.55 MB

CSS Challenge 01/screenshots/overview-page.png

4.34 MB

File added
File added
This image diff could not be displayed because it is too large. You can view the blob instead.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Posts Overview</title>
<link rel="stylesheet" href="./style.css">
<!-- Latest Font-Awesome CDN -->
<script src="https://kit.fontawesome.com/b4ce455260.js" crossorigin="anonymous"></script>
<!-- Google font Poppins -->
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Poppins:wght@400;700&display=swap">
</head>
<!-- header -->
<body>
<header>
<img src="./images/main.png" alt="Magazines">
<h1>InsightsHub: Explore, Learn, and Stay Inspired</h1>
<div class="search-bar">
<input type="text" placeholder="...">
<br>
<button>Search</button>
</div>
</header>
<div class="content">
<!-- featured posts -->
<section class="featured-posts">
<h2>Featured Posts</h2>
<div class="post">
<h3><a href="post-detail.html">The Art of Blogging</a></h3>
<div class="post-meta">March 5, 2024 by John Doe - <i class="fa-solid fa-clock"></i> 8 min read</div>
<p>Unlock the secrets of creating engaging and successful blog content. From choosing the right topics to mastering SEO, this comprehensive guide will help you become a blogging master. Explore the artistry of storytelling and discover tips for building a loyal readership.</p>
<div class="post-actions">
<button><i class="fa-solid fa-thumbs-up"></i> Like</button>
<button><i class="fa-solid fa-comment"></i> Comment</button>
</div>
<hr>
</div>
<div class="post">
<h3><a href="#">Exploring Virtual Reality</a></h3>
<div class="post-meta">February 20, 2024 by Jane Smith - <i class="fa-solid fa-clock"></i> 10 min read</div>
<p>Dive into the immersive world of virtual reality and discover its endless possibilities. From gaming to education, this post explores the various applications of VR technology. Learn about the latest advancements, must-try experiences, and how virtual reality is reshaping industries and entertainment.</p>
<div class="post-actions">
<button><i class="fa-solid fa-thumbs-up"></i> Like</button>
<button><i class="fa-solid fa-comment"></i> Comment</button>
</div>
</div>
</section>
<br>
<br>
<!-- recent posts -->
<section class="recent-posts">
<h2>Recent Posts</h2>
<div class="post">
<h3><a href="#">The Future of AI in Healthcare</a></h3>
<div class="post-meta">March 10, 2024 by Alex Johnson - <i class="fa-solid fa-clock"></i> 7 min read</div>
<p>Explore the groundbreaking advancements and transformative potential of artificial intelligence in the healthcare industry. This comprehensive post dives into the current applications of AI in diagnostics, personalized medicine, and patient care.</p>
<div class="post-actions">
<button><i class="fa-solid fa-thumbs-up"></i> Like</button>
<button><i class="fa-solid fa-comment"></i> Comment</button>
</div>
</div>
<hr>
<div class="post">
<h3><a href="#">The Rise of 5G Technology</a></h3>
<div class="post-meta">February 28, 2024 by Chris Williams - <i class="fa-solid fa-clock"></i> 9 min read</div>
<p>Embark on a journey through the evolution of mobile communication with the advent of 5G technology. This in-depth exploration delves into the capabilities and impact of 5G on various industries. Discover how faster speeds, lower latency, and increased connectivity are transforming the way we live, work, and innovate. From smart cities to IoT applications, explore the limitless possibilities that 5G brings to the forefront of the digital era.</p>
<div class="post-actions">
<button><i class="fa-solid fa-thumbs-up"></i> Like</button>
<button><i class="fa-solid fa-comment"></i> Comment</button>
</div>
</div>
</section>
</div>
<!-- footer -->
<footer>
<div class="social-media">
<a href="www.facebook.com"><i class="fa-brands fa-facebook-f"></i></a>
<a href="www.twitter.com"><i class="fa-brands fa-twitter"></i></a>
<a href="www.instragram.com"><i class="fa-brands fa-instagram"></i></a>
<a href="www.linkedin.com"><i class="fa-brands fa-linkedin-in"></i></a>
</div>
<p>&copy; 2024 Blog Title. All rights reserved.</p>
</footer>
</body>
</html>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Post Detail</title>
<link rel="stylesheet" href="./style.css">
<!-- Latest Font-Awesome CDN -->
<script src="https://kit.fontawesome.com/b4ce455260.js" crossorigin="anonymous"></script>
<!-- Google font Poppins -->
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Poppins:wght@400;700&display=swap">
</head>
<body>
<!-- header -->
<header>
<img src="./images/main.png" alt="Magazines">
<h1>The Art of Blogging</h1>
</header>
<!-- details -->
<div class="content">
<article class="post-detail">
<p>Welcome to "The Art of Blogging" – a space where creativity meets expression and where words have the power to shape ideas, connect minds, and inspire action. Whether you're a seasoned blogger or just starting your journey, this guide is designed to help you navigate the intricacies of successful blogging. Let's delve into ten essential tips that can elevate your blogging experience and make your content stand out in the vast digital landscape:</p>
<hr>
<div class="post-action">
<ul>
<li><i class="fa-solid fa-thumbs-up"></i></li>
<li><i class="fa-regular fa-comment"></i></li>
<li><i class="fa-regular fa-bookmark"></i></li>
<li><i class="fa-solid fa-file-arrow-down"></i></li>
</ul>
</div>
<hr>
<ol>
<li>Define Your Niche</li>
<li>Create Quality Content</li>
<li>Engage with Your Audience</li>
<li>Optimize for SEO</li>
<li>Use Compelling Visuals</li>
<li>Promote on Social Media</li>
<li>Network with Other Bloggers</li>
<li>Consistency is Key</li>
<li>Monitor Analytics</li>
<li>Stay Updated on Trends</li>
</ol>
<p>Remember, blogging is not just about writing; it's about creating a connection with your readers and providing value to them.</p>
<ul>
<li>Experiment with different writing styles</li>
<li>Share personal anecdotes and experience</li>
<li>Show your personality to make your blog more relatable</li>
<li>Interact with your audience through comments and social media</li>
<li>Respond to feedback, questions, and suggestions</li>
<li>Build a community around your blog for increased loyalty</li>
<li>Stay informed about the latest industry trends and technology updates</li>
<li>Use knowledge to generate relevant and timely content</li>
<li>Position yourself as an authority in your niche</li>
</ul>
<p>These additional practices will further enhance your blogging experience and help you establish a strong online presence.</p>
<p>Additionally, consider experimenting with different writing styles to keep your content fresh and engaging. Share personal anecdotes, opinions, and experiences to make your blog more relatable. Don't be afraid to show your personality; authenticity resonates with readers.</p>
<p>Moreover, interact with your audience through comments and social media. Respond to their feedback, questions, and suggestions. Building a community around your blog can foster loyalty and increase your reach.</p>
<p>Stay informed about the latest industry trends and technology updates. This knowledge will not only help you generate relevant content but also position yourself as an authority in your niche.</p>
</article>
</div>
<!-- footer -->
<footer>
<div class="social-media">
<a href="www.facebook.com"><i class="fa-brands fa-facebook-f"></i></a>
<a href="www.twitter.com"><i class="fa-brands fa-twitter"></i></a>
<a href="www.instragram.com"><i class="fa-brands fa-instagram"></i></a>
<a href="www.linkedin.com"><i class="fa-brands fa-linkedin-in"></i></a>
</div>
<p>&copy; 2024 Blog Title. All rights reserved.</p>
</footer>
</body>
</html>
* {
box-sizing: border-box;
}
body {
margin: 0;
}
body {
align-content: center;
font-family: 'Poppins', sans-serif;
margin: 0;
padding: 0;
background-color: #f4f4f4;
color: #333;
}
header {
background-color: #333;
color: white;
text-align: center;
position: relative;
padding: 0 0 20px 0;
}
header img {
width: 100%;
height: auto;
object-fit: cover;
display: block;
}
header h1 {
margin: 0;
font-size: 2.5em;
background: #333;
padding: 30px 0 0;
}
.content {
align-content: center;
margin: auto;
padding: 20px 360px;
background-color: #f0ecec;
}
.featured-posts{
background-color: #fff;
padding: 20px;
border-radius: 10px;
box-shadow: #333;
}
.recent-posts{
background-color: #fff;
padding:20px;
border-radius: 10px;
box-shadow:#333;
}
.post-detail p{
line-height: 1.6;
margin: 10px 0;
}
.post-actions{
display: inline-block;
margin: 20px 0;
gap: 20px;
}
.post-actions:hover{
cursor: pointer;
}
.post-action li:hover{
display: inline-block;
cursor: pointer;
color: yellow;
transition-duration: 1s;
}
.post-actions i {
margin-left: 5px;
align-items: center;
}
ol {
padding-left: 20px;
}
ul {
padding-left: 20px;
list-style: none;
}
ul li {
margin: 5px 0;
position: relative;
}
footer {
text-align: center;
padding: 20px 0;
background-color: #333333;
border-top: 1px solid #eaeaea;
}
footer .social-media {
margin-bottom: 10px;
}
footer .social-media a {
color:yellow;
text-decoration: none;
margin: 0 10px;
font-size: 1.2em;
}
footer p {
margin: 0;
color:white;
}
.search-bar{
display: block;
margin: auto;
width: 400px;
padding: 30px;
}
.search-bar input {
height: 30px;
width: 100%;
border-radius: 5px;
border-color: #fff;
margin-bottom: 5px;
border-width: 0;
}
.search-bar button{
height: 30px;
width: 100%;
background-color: #bbb;
border-width: 0;
border-radius: 5px;
color: white;
}
.search-bar button:hover{
cursor: pointer;
background-color: #555;
transition-duration: 1s;
}
a {
color: rgb(217, 217, 16);
}
.post-actions button{
background-color: #333333;
color: #fff;
padding: 5px 10px;
border-radius: 5px;
}
.post-actions button:hover{
cursor: pointer;
background-color:#555;
transition-duration: 1s;
}
.post-meta{
color:grey;
}
.post-action {
align-self: center;
color: #333;
font-size: 1em;
width: 150px;
margin: auto;
}
.post-action ul {
padding: 3px;
display: inline-block;
list-style: none;
list-style-position:inside;
}
.post-action :not(:last-child){
margin-right:10px;
}
.post-action ul li {
display: inline-block;
}
\ No newline at end of file
# Brainster-Challenges
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://git.brainster.co/Marija.Velkovska/brainster-challenges.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://git.brainster.co/Marija.Velkovska/brainster-challenges/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
File added
File added
File added
File added
File added
File added
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment