Responsive Web Design Updates

freeCodeCamp Support
108

You can toggle on and off the html/css tabs in the freeCodeCamp editor as well though?

2 Likes
109

You’re missing my point. I said in my original post that toggling html and css on and off is too confusing when I’m trying to reference thing in both parts of the code. What I said about codepen’s console is different - having them both to the side of the preview allows all three to be viewed simultaneously without overcrowding.

1 Like
110

Like this?

image
image1914×892 30.8 KB

That’s about a crowded as Codepen is for me

1 Like
111

Anyway, I’m sharing real time accessibility feedback from my actual experience of trying to code in both editors. Others’ mileage may vary. However, I would hope that FCC is open to considering its neurodivergent and chronically ill users’ feedback, especially when making updates to better the interface.

2 Likes
112

Yep. We take neurodiverent users feedback. I’m neurodivergent myself. I’m just trying to actually understand your feedback and translate it into something actionable. “It is crowded” doesn’t provide a clear avenue for a fix.

1 Like
113

Have you used the new text editor to code a complete project, while constantly referencing the instructions and tests as well in a separate column? It doesn’t seem like it. 4 vertical columns side by side, all squished, is simply not accessible from my standpoint. Maybe for more experienced coders it wouldn’t matter. However, the Responsive Web Design module is intended, I assume, for people new to coding like me who actually need to go back and forth a lot.

2 Likes
114

I can’t translate “it is all squished” into actionable feedback that generates a change. We aren’t going back to Codepen. We have the same number of panels as Codepen. You can toggle them like Codepen. You can open the instructions in a separate tab like you would with Codepen. So in what way are you looking for this editor to be different? Is it just that the HTML and CSS tabs can be stacked in Codepen?

1 Like
115

Here are all concise and actionable things that could be done:

  1. Put the instructions and user stories on a separate page, or have the option to pop them out to a separate tab.

  2. Allow the tests to be minimized when not being run.

  3. Consider having multiple stacking options for the code, as well as a full page preview.

If the reasons for any of that is confusing, reread my original post. I believe I wrote out my feedback with detailed explanations. It is hardly just “it’s overwhelming” or “it’s all squished”. Honestly, your simplified interpretations of what I am saying while I am trying to explain my needs reads as pretty ableist and dismissive. I am out of spoons for trying to explain further. I hope someone else can jump in here if needed.

3 Likes
116

I think being able to stack the code panels would be a nice feature and I agree that having 4 panels side-by-side doesn’t really work all that great. I’m sure improvements can and will be made as users give their feedback.

I’d suggest you open an issue on GitHub for it. You are more like to get feedback from the developers and user feedback is important.

3 Likes
117

You can do that on your own. You can open the same challenge in two tabs and change the panel sizes to control what’s visible independently in each tab. But I think adding the ability to toggle that panel is likely technically feasible. This is something I can put into a GitHub issue.

The instructions and test output are in the same panel, so the above applies.

I’m honestly not sure how hard it is to swap between horizontal and vertical arrangements of the panel, but this is something I can put into a GitHub issue as well.

Dude. I’m neurodivergent too. Us being neurodivergent doesn’t change that if people don’t understand what change we want, then they can’t make it happen. This most recent explanation is something that I can translate into issues for the team to consider. It provides specific things for the team to consider. Thank you for honing in on specific things that would improve the experience.

2 Likes
118

Thank you. I’ve got to learn how to use GitHub first :slight_smile: but it’s on my list!

1 Like
119

I appreciate you considering the issues and putting them in GitHub. After taking a step back to cool down, I think our neurodivergence was clashing in this conversation, actually. It was hard for me after saying “hey X doesn’t work as well as Y” to hear “well they’re basically the same for me, what’s the problem?”, which felt like an invalidation of my original feedback. I felt pressured to translate my initial concerns as if I had to prove to you that they were real concerns. At the same time, I can see you were wanting to clarify what was going on to try to come up with specific issues to address. Glad we got to a place where we made sense.

3 Likes
120

Just make an account and use the Issues like you use the forum. There isn’t really much to it. At least not for creating an issue with feedback and suggestions. But don’t feel pressured to do it. I’m sure the devs also read this thread.

4 Likes
121

Thanks, you’re right - I poked around and realized this aspect of GitHub isn’t that hard to use so I’m working on an Issue now :slight_smile: it’s the rest of git that I have to catch up on.

1 Like
122

Freecode camp has done a fantastic job with this new way of teaching. I hope you can do the same with the javascript course as well. So much easier to learn the language. thanks and keep you the good work.

1 Like
123

Hi, I was mid way through a project when I tried to log in and got a message stating that the server was down for maintenance. When I tried to log in the next day today, I can no longer find the curriculum and my log in appears to have been deleted. Any ideas on what has happend?

1 Like
124

make sure you are using the same email address

if you are sure, maybe try reaching out to support@freecodecamp.org

1 Like
125

This version is much better than the previous one. Congrats and thank you.

2 Likes
126

Thanks, I am sure I am using the correct address. I will try the support address.

127

Thank you for this content! Very well detailed and informative!

1 Like