html-react-parser VS Portfolio2.0

using libraries like html-react-parser but it did not work see: https://github.com/remarkablemark/html-react-parser/discussions/1015

I was thinking about some sanitization library but found this: https://github.com/remarkablemark/html-react-parser which i have reviewed to deeply yet.

I'm glad I could help! Please be careful though and check the FAQ section of the library. It says that it does not sanitize and it's not XSS safe. This is the issue where they explain: https://github.com/remarkablemark/html-react-parser/issues/94

I then switched to html-react-parser, but same result.

by using dangerouslySetInnerHTML, entire html in the string is preserved. Other alternative would be to use a html-react-parser library.

However, when I insert the body_html field into my JSX map, it's just displaying a string with a bunch html tags in it. One quick google showed me html-react-parser and after the easiest install and application, my blogs are loading beautifully with pictures and links. All I had to add was the import (import parse from 'html-react-parser';) and a couple lines to my blogList map:

You can check out all the code for this app in my portfolio repo.

To update my favicon, I need to update two tags in my index.html file. Because of how React works, the two paths in my href="" attributes start with %PUBLIC_URL% before the /, but here's the code with a more universal path:

, because I want it to be visually hidden, I'll be fixing that when I get to this Github issue. WAVE mostly returned errors I had already vetted. It did actually catch one of the many broken links that I'll be fixing in this Github issue. It returned 27 long alt-text warnings on my blog page, but they're all less than 150 characters. I also got false positive contrast errors for my visually hidden skip links. ARC is down to primarily false positives. There were a couple I had to look up to make sure they were ok, like buttons with transparent backgrounds and using images with alt-text or an aria-label instead of text in links. The IBM Equal Access Accessibility checker just stopped working. It refused to scan even after I restarted Chrome, uninstalled and reinstalled it in Chrome, and installed it in Firefox. I saw something about the ruleset being undefined, so hopefully they fix that soon. Luckily, I ran it multiple times in Part 5 so I'm comfortable with moving on. The Microsoft Accessibility Insights Fast Pass didn't find anything that wasn't already on my radar, but I will be using the Assessment option as a guide for my manual testing again.

This blog will focus on making the blog preview component code on the main page of my site more accessible.

My portfolio Github repository has all the toggle component code and the toggle CSS. The structure of the toggle looks like this:

If I wanted these to be the most accessible, I would also add another visual cue that showed "this link will open in a new tab" on hover or focus. This would be ideal for the links attached to the Github and Chrome SVGs and for keyboard and unassisted users that don't know what the external icon link means. However, I would want to spend time I don't have today designing a nice-looking version of that, so I've added this to my Github repository as my first backlog issue for this site.

When I found out DEV has an API that will send you the HTML of each of your blogs, I made a branch in my portfolio site repo, rewrote my FullBlog component, and attempted to call the API from within the established Blog React component. No dice. CORS error. Now I knew that I needed a server so I could use a CORS package or another solution. At this point, I also noticed I'd have to call the DEV API /articles/me endpoint to get the ids of each of my blogs and then call the /articles/{id} endpoint with the id to get the HTML version or find a solution for the markdown version.

Next, I added the toggle component to my navigation bar component. I styled the toggle following Chris Bongers’ Tutorial based on Katia De Juan’s Dribbble. Then I adjusted the size and flipped it to default to dark mode. While this toggle is so cute that you could die, this tutorial will work with any or clickable . First, I set up the basic JSX, the local state, and a variable to hold the theme we get from localStorage: import React, { useEffect, useState } from 'react'; import '../styles/toggle.css'; import { setTheme } from '../utils/themes'; function Toggle() { const [togClass, setTogClass] = useState('dark'); let theme = localStorage.getItem('theme'); return (

) } export default Toggle; Enter fullscreen mode Exit fullscreen mode When a user clicks the toggle, I want the theme on the page to change and the toggle to change with it. I added the imported setTheme() function and setTogClass() from the local state to a handleOnClick function. You can see where it is passed to the clickable part of the toggle in the JSX above. const handleOnClick = () => { if (localStorage.getItem('theme') === 'theme-dark') { setTheme('theme-light'); setTogClass('light') } else { setTheme('theme-dark'); setTogClass('dark') } } Enter fullscreen mode Exit fullscreen mode I used this component’s useEffect() to make sure the local state togClass always loads with the correct theme. useEffect(() => { if (localStorage.getItem('theme') === 'theme-dark') { setTogClass('dark') } else if (localStorage.getItem('theme') === 'theme-light') { setTogClass('light') } }, [theme]) Enter fullscreen mode Exit fullscreen mode Because my toggle is a checkbox, the dark theme should show the unchecked (moon) state and the light theme should show the checked (sun) state. I couldn’t get defaultChecked to work how I wanted, so I replaced the unchecked with this conditional rendering ternary operator (conditional operator): { togClass === "light" ? : } Enter fullscreen mode Exit fullscreen mode If you used a , you could easily use conditional rendering like this to change the className attribute within the tag and get the same effect. Put all together, the code for the toggle component looks like this: import React, { useEffect, useState } from 'react'; import '../styles/toggle.css'; import { setTheme } from '../utils/themes'; function Toggle() { const [togClass, setTogClass] = useState('dark'); let theme = localStorage.getItem('theme'); const handleOnClick = () => { if (localStorage.getItem('theme') === 'theme-dark') { setTheme('theme-light'); setTogClass('light') } else { setTheme('theme-dark'); setTogClass('dark') } } useEffect(() => { if (localStorage.getItem('theme') === 'theme-dark') { setTogClass('dark') } else if (localStorage.getItem('theme') === 'theme-light') { setTogClass('light') } }, [theme]) return (

{ togClass === "light" ? : }

) } Enter fullscreen mode Exit fullscreen mode Finally, my favorite part: the color switching SVGs! CSS variables work in SVG code too! I got my SVG code for the Github and Chrome icons from DEVICON. For the Github icon all I had to change was one fill attribute in a : fill="var(--dark-text)"> Enter fullscreen mode Exit fullscreen mode The Chrome icon had a fill attribute in a and a : fill="var(--dark-text)" cx="63.624" cy="64.474" r="22.634"> fill="var(--dark-text)" ...> Enter fullscreen mode Exit fullscreen mode The result looks like this: Conclusion I tried to include all of the relevant code, but you can also see the full code for my site in its Github repository. If you enjoyed this article or are left with questions, please leave a comment below! I would also love to see anything built following this tutorial.