#CSS Frameworks

[apaintingfortheartist]

A collection of CSS Frameworks for HTML, CSS and JS for easier web development. Sourced under a creative commons. This list will be updated regularly.

[nixcraft]

Do you need to build a static website for fun or profit?

Try the Simple.css Framework. It is a CSS framework that makes semantic HTML look good.

A good-looking sans-serif local font stack.

Typographic best practices.

Automagic flipping to dark mode.

Fully responsive.

Sensible defaults that format standard + HTML elements.

Super lightweight (10k css).

Give it a try @ https://simplecss.org/ (my home page https://vivekgite.com for live demo).

[kokoasci]

im asking here bc i feel like people here maybe have more experience with this. does anyone know where i could set up a personal blog? i considered tumblr but id like this to be more of a personal experiment rather than tied to a social media site. i dont want to have to pay for a custom domain and dont have enough frontend experience to build something from scratch though,, ;__;

no worries if not, just wanted to ask if anyone has done this! <3

[learningthefullstack]

Fellow programmers:

[qrevo]

uh can someone. threaten to beat me with a large rock. if i don't finish up my uni work in time. really needing that "fighting for my life" energy to finish these up lol

[mydevdiary]

The plan: Introductory Post

Hello everyone!

I'm mostly writing this post to pin it to my blog page for those who visit.

The heart of this blog is tracking a website I will build from the ground up. This includes the front-end, back-end, UX/UI design, and any other planning/work that pops up.

For some context, around a year ago, I started practicing web development to make it my career. However, things turned out differently than expected. I got another job after having horrendous luck finding work. I really enjoy it, so it snuffed out my drive to find a career in web development.

However, I've always liked web development and programming in general. I've always wanted to use it, but I just didn't have any ideas I wanted to commit to. Now, I have a site that I feel I can turn into a full-fledged application, and I'd like to track it here for those interested and connect with others interested.

I've been on a six-month hiatus, so I'm pretty rusty, but I've decided I want to build the site using Svelte and Supabase. Svelte has always been the framework I wanted to learn, so this website is the perfect excuse. I also have experience with Firebase, but I wanted to challenge myself by learning Supabase. Most of my experience is with React and Next.js. I've used them for volunteer work and for freelancing gigs in the past.

I'll also give a brief summary of my website for common understanding. The MVP will start as a blog, but I plan to expand it to turn it into an informative database (sort of like Wikipedia) and have some interactive elements. I won't get into the meat of the idea, but that's what to expect with my posts. But before that, my posts will mostly be centered around a summary of my learning. Since I'm learning Svelte, my current posts will be based on that.

Thanks for stopping by, and I look forward to hearing your comments or insights moving forward! If you have any questions, feel free to ask!

[bf-rally]

felt like i was going crazy yesterday trying to set up a login system for this website 😭 it was like i was back in college again!

[piratesexmachine420]

Somebody needs to go talk to the W3C and inform them that, frankly, the document metaphor is dead. Nobody* has made a webpage designed to be a page of hypertext in twenty years. It doesn't, hasn't, won't happen. We gotta find something better.

*Within a reasonable margin of error, and with exception to Wikipedia and similar projects

[rustyscreech]

idk when tech bros say frameworks like tailwind or sass make css "finally fun to develop" I cannot fucking relate. I love vanilla css I don't understand how people don't like it

[borealing]

"learn to code" as advice is such bullshit. i have learned and used four and a half different coding languages through my career (html/css, java, python+sql, c++) and when i say used i mean I've built things in every one but the things that i actually used these languages for??? these earn zero money (with the caveat of until you have seniority in, e.g. front end web dev) what people really mean when they say learn coding is "learn to code. go into investment banking or finance startups." coding does not inherently have money in it. my absolute favourite part of coding? my peak enjoyment? was when i was developing for a visual coding language (you put it together like a flowchart, so say youre using a temperature sensor and you want it to log the temperature once every four hours, you can put the blocks together to make it do that. i was writing the code behind the blocks for new sensors) and i was earning £24k a year and that wasn't even part of my main role. it was an extra voluntary thing i was doing (i was working as a research assistant in biosensors - sort of - at a university, and was developing the visual code for students who didnt want to learn c++) like. i want people to learn to code, i want people to know how their electrical equipment works and how coding works, but dont believe the myth that there is inherently money in coding. the valuable things, the things people are passionate about are still vulnerable to the passion tax (if you want to do it you dont have to be paid for it). skills arent where the money is, money is where the money is.

[officialkrubs]

i work in tech. and i get real annoyed when im trying to have beers and chat with my fellow colleagues and say 'yeah i think this is wild how the 'net's going and i wanna work on something new' and they're like "yeah something new will come up soon" and it's like.

ugh, no. you're not getting me. I want to be part of that something new. i want to try even imagine what something new could look like. why don't you wanna play the game with me. why don't you want to imagine

[nextskilltechnologies]

Certificate Course in PHP Full Stack Developer at Nextskill Technologies, Coimbatore

In today's rapidly evolving digital landscape, the demand for skilled web developers is at an all-time high. Among the various programming languages, PHP Full Stack has emerged as a powerful and widely-used scripting language for web development. If you are keen on exploring a career in this exciting field, look no further than the Certificate Course in PHP Full Stack Developer offered by Nextskill Technologies in Coimbatore. This comprehensive program is designed to equip you with the knowledge and practical skills necessary to excel in the world of web development. Let's dive into the details of this exceptional course.

Why Certificate Course in PHP Full Stack Developer?

Before delving into the specifics of the course, let's understand why PHP Full Stack Developer is a lucrative and sought-after skill in the tech industry.

Versatility: PHP Full Stack can be seamlessly integrated with various databases, frameworks, and content management systems, making it a versatile language for developing dynamic web applications.

High Demand: Many popular websites, including Facebook and WordPress, are built using PHP Frameworks. The language's prevalence ensures a steady demand for skilled PHP Full Stack developers.

Open Source Advantage: Being an open-source language, PHP Frameworks is constantly updated and enriched by a vibrant community of PHP developers, providing access to a vast array of libraries and tools.

Career Growth: PHP developers can explore various career paths, such as PHP full-stack developers,PHP backend developers, or even specialize in PHP-based frameworks like Laravel or CodeIgniter.

Nextskill Technologies: Empowering Your Journey

Located in the heart of Coimbatore, Nextskill Technologies has earned a reputation as a leading IT training institute with a focus on cutting-edge technologies. Their Certificate Course in PHP Full Stack Developer is a well-structured program that caters to both beginners and experienced professionals looking to enhance their web development skills.

Course Curriculum Certificate Course in PHP Full Stack Developer at Nextskill Technologies is designed to provide a comprehensive understanding of web development principles and practical hands-on experience. The well-organized curriculum includes:

Introduction to Web Development: An overview of web development, its technologies, and the role of PHP Full Stack Developer.

HTML, CSS, and JavaScript Fundamentals: Building a strong foundation in front-end development.

PHP Programming Basics: Learning PHP syntax, variables, operators, and control structures.

MySQL Database Integration: Understanding database design and integration with PHP frameworks.

Object-Oriented PHP: Mastering object-oriented PHP programming concepts and their implementation in PHP.

PHP Frameworks: Exploring popular PHP frameworks like Laravel for efficient development.

Front-end Frameworks: Implementing front-end frameworks like Bootstrap for responsive design.

Project Work: Applying the learned concepts to real-world projects under the guidance of experienced mentors.

Key Features of the Course

Experienced Faculty: The course is taught by industry experts with extensive experience in PHP Full Stack Developer, ensuring a quality learning experience.

Hands-on Training: Practical exercises and real-world projects provide students with valuable hands-on experience.

Placement Assistance: The institute offers placement support and guidance to help students kickstart their careers.

Certification: Upon successful completion of the course, participants receive a recognized certificate, adding value to their resumes.

Conclusion

The Certificate Course in PHP Full Stack Developer at Nextskill Technologies, Coimbatore, is an excellent opportunity for aspiring web developers to gain the skills and knowledge required to thrive in the competitive tech industry. With a well-structured curriculum, experienced faculty, and a supportive learning environment, this course serves as a stepping stone towards a successful career in PHP Full Stack Developer. Embrace this opportunity, and let Nextskill Technologies be your guide on this rewarding journey.

For More Details: https://nextskilltechnologies.com/

[genderfluid-druid]

[ID: Photo of an ancient floppy drive with a sticker that says, "Works, but makes Sad Noises". End ID]

me_irl

[aakashweb]

Want to add self-hosted social sharing icons on your website ? Check out "Socializer.css", a #CSS #framework to create social sharing buttons/icons. 🟢 55+ social networks 🟢 6 button shapes 🟢 8 hover styles 🟢 5 text styles 🟢 3 layout types 🔗 https://www.aakashweb.com/css-libraries/socializer-css/

[jcmarchi]

What on Earth is the `types` Descriptor in View Transitions?

New Post has been published on https://thedigitalinsider.com/what-on-earth-is-the-types-descriptor-in-view-transitions/

What on Earth is the `types` Descriptor in View Transitions?

Have you ever stumbled upon something new and went to research it just to find that there is little-to-no information about it? It’s a mixed feeling: confusing and discouraging because there is no apparent direction, but also exciting because it’s probably new to lots of people, not just you. Something like that happened to me while writing an Almanac’s entry for the @view-transition at-rule and its types descriptor.

You may already know about Cross-Document View Transitions: With a few lines of CSS, they allow for transitions between two pages, something that in the past required a single-app framework with a side of animation library. In other words, lots of JavaScript.

To start a transition between two pages, we have to set the @view-transition at-rule’s navigation descriptor to auto on both pages, and that gives us a smooth cross-fade transition between the two pages. So, as the old page fades out, the new page fades in.

@view-transition navigation: auto;

That’s it! And navigation is the only descriptor we need. In fact, it’s the only descriptor available for the @view-transition at-rule, right? Well, turns out there is another descriptor, a lesser-known brother, and one that probably envies how much attention navigation gets: the types descriptor.

What do people say about types?

Cross-Documents View Transitions are still fresh from the oven, so it’s normal that people haven’t fully dissected every aspect of them, especially since they introduce a lot of new stuff: a new at-rule, a couple of new properties and tons of pseudo-elements and pseudo-classes. However, it still surprises me the little mention of types. Some documentation fails to even name it among the valid  @view-transition descriptors. Luckily, though, the CSS specification does offer a little clarification about it:

The types descriptor sets the active types for the transition when capturing or performing the transition.

To be more precise, types can take a space-separated list with the names of the active types (as <custom-ident>), or none if there aren’t valid active types for that page.

Name: types

For: @view-transition

Value: none | <custom-ident>+

Initial: none

So the following values would work inside types:

@view-transition navigation: auto; types: bounce; /* or a list */ @view-transition navigation: auto; types: bounce fade rotate;

Yes, but what exactly are “active” types? That word “active” seems to be doing a lot of heavy lifting in the CSS specification’s definition and I want to unpack that to better understand what it means.

Active types in view transitions

The problem: A cross-fade animation for every page is good, but a common thing we need to do is change the transition depending on the pages we are navigating between. For example, on paginated content, we could slide the content to the right when navigating forward and to the left when navigating backward. In a social media app, clicking a user’s profile picture could persist the picture throughout the transition. All this would mean defining several transitions in our CSS, but doing so would make them conflict with each other in one big slop. What we need is a way to define several transitions, but only pick one depending on how the user navigates the page.

The solution: Active types define which transition gets used and which elements should be included in it. In CSS, they are used through :active-view-transition-type(), a pseudo-class that matches an element if it has a specific active type. Going back to our last example, we defined the document’s active type as bounce. We could enclose that bounce animation behind an :active-view-transition-type(bounce), such that it only triggers on that page.

/* This one will be used! */ html:active-view-transition-type(bounce) &::view-transition-old(page) /* Custom Animation */ &::view-transition-new(page) /* Custom Animation */

This prevents other view transitions from running if they don’t match any active type:

/* This one won't be used! */ html:active-view-transition-type(slide) &::view-transition-old(page) /* Custom Animation */ &::view-transition-new(page) /* Custom Animation */

I asked myself whether this triggers the transition when going to the page, when out of the page, or in both instances. Turns out it only limits the transition when going to the page, so the last bounce animation is only triggered when navigating toward a page with a bounce value on its types descriptor, but not when leaving that page. This allows for custom transitions depending on which page we are going to.

The following demo has two pages that share a stylesheet with the bounce and slide view transitions, both respectively enclosed behind an :active-view-transition-type(bounce) and :active-view-transition-type(slide) like the last example. We can control which page uses which view transition through the types descriptor.

The first page uses the bounce animation:

@view-transition navigation: auto; types: bounce;

The second page uses the slide animation:

@view-transition navigation: auto; types: slide;

You can visit the demo here and see the full code over at GitHub.

The types descriptor is used more in JavaScript

The main problem is that we can only control the transition depending on the page we’re navigating to, which puts a major cap on how much we can customize our transitions. For instance, the pagination and social media examples we looked at aren’t possible just using CSS, since we need to know where the user is coming from. Luckily, using the types descriptor is just one of three ways that active types can be populated. Per spec, they can be:

Passed as part of the arguments to startViewTransition(callbackOptions)

Mutated at any time, using the transition’s types

Declared for a cross-document view transition, using the types descriptor.

The first option is when starting a view transition from JavaScript, but we want to trigger them when the user navigates to the page by themselves (like when clicking a link). The third option is using the types descriptor which we already covered. The second option is the right one for this case! Why? It lets us set the active transition type on demand, and we can perform that change just before the transition happens using the pagereveal event. That means we can get the user’s start and end page from JavaScript and then set the correct active type for that case.

I must admit, I am not the most experienced guy to talk about this option, so once I demo the heck out of different transitions with active types I’ll come back with my findings! In the meantime, I encourage you to read about active types here if you are like me and want more on view transitions: