HTML/CSS Questions, Resources, and Discussion (January 2018 Cohort)

HTML/CSS Questions, Resources, and Discussion (January 2018 Cohort)
0

#66

@camper ok if my forum account is the same then no problem


#67

Just press the button and it will unlock. Then press it again to run the code.
I get the same in Firefox Developer Edition browser. :slight_smile:


#68

It’s Visual Studio Code, a free & open-source text editor from Microsoft.


#69

Sorry about using that abbreviation. I thought everyone knew what it was.


#70

A quick question in relation to demo for challenges (landing page, portfolio etc)…
I’ve just set up git-hub pages.

Interested to find out:

Using git-hub (pages) and who is using git-lab …why do you have a preference?

:slight_smile:


#71

@johnhannahdev I prefer GitLab for my projects mostly because it’s Free Software. GitLab Pages is a little bit more complicated to set up, but once it’s running, it’s a set and forget type of thing. I find the Continuous Deployment/Pipeline feedback to be more transparent than GitHub’s interface, as it lets me know when there are problems and when I should re-run the publishing job. With GitHub Pages, sometimes my code takes a long time to update and there’s usually no stated reason why. I also like that GitLab more accurately uses “Merge Requests” instead of GitHub’s “Pull Requests.” It’s the same process, just different names for it.


#72

I need to start using Github, do you have any good tutorials or real life examples how to get comfortable with it? I tries few thing but still i don’t really understand :frowning:


#73

@HaiCia

It took me a couple of goes to:
Sign Up and Build a Repository/ Link the index to a GIT Page.
Here’s what I used.

  1. Sign Up to Github.
    Github Sign Up

  2. Build a repository. (Add a readme and a licence).
    Instructions here - Create a Repo

  3. Set Up A Project or User Organisation Site
    https://pages.github.com/
    A. PROJECT:
    Step by step shows you how to link your index file to a browser if you select ‘project’.
    You end up with a URL - YourUsername.github.io/YourProjectName

Every project can have an index so I’m setting up a basic index page for each challenge right now so they are ready.

B. User Organisation Site:
Step by Step shows you how to set up Github (for me on a Mac) on your desktop.
You’ll have a folder with your files on it …editable from Sublime/VS/Atom/Other text editor.

Then when you update you simply upload the new index file (or other file) and you have a version controlled page/site.

A master branch is the site and you can upload other branches that are works in progress.
When you finish the WIP …you can commit it (move it) to the master branch.

When you set up a project you can choose to have that link to the index file from the master or other branch.

Have a play with steps 1, 2 and 3 and see how far you can get.

It took me 2 hrs and a couple of re runs to get it set up.

Good luck.


#74

thank you! i will try :slight_smile:


#75

And if you are still having trouble, TheNewBoston on YouTube has a great video series on how to use Git and Github.


#76

Hi everyone! I am joining a bit late since I just found out about the cohort. Just to clarify, the goal is to work on the freeCamp and then share ideas and resources here? I had trouble getting the site to work. I had worked through challenges all the way to JavaScript a year ago then life got in the way. I see some changes on the site, but do I need to start from the beginning?


January 2018 fCC Cohort
#77

@Krate2016 Thanks for joining! Your idea of the cohort is correct. I answered your other question here: January 2018 fCC Cohort.


#78

I have a stupid/trivial question. How do you find the proper w3c documentation? I mean…what did you type in the google engine? Did you type sth like ’ w3c the editor’s draft? Or maybe you find it via the navigation directly on the w3c site. It takes me a lot of time to find the proper recommendation. There are a lot of versions, some of them are just recommendations, some of them are just drafts, others are obsolete…


#79

I’d like to join this cohort. Please add me if it’s still possible. I’ve just started with beta version.


#80

I have one remark as for the “Link to Internal Sections of a Page with Anchor Elements” challenge. I don’t like the approach that id=“footer” is used with the . Here’s the direction from the challenge:" The footer tag should have an id attribute set to “footer”. Wouldn’t be better to name it, let’s say, “bottom” instead of “footer”? Does anybody consider that? I know, I’m a camper here, but I couldn’t stop thinking about it!


#81

Its the same in text documents, you have a header and a footer so I dont think bottom would be better


#82

To avoid obsolete info, when you do a Google search, also do this:

  • do a preliminary search for your keywords
  • then click on “Tools” (far right, area under the search field)
  • a drop-down menu will appear toward the left and underneath, look for Any Time and choose Past Year (or other time period)

This will narrow the search results to items dated within the past 12 months.

  • You can also then Sort by Date to get most recent item to the top

HTH.


#83

I’m not sure about ‘avoiding-id-at-any-cost’ approach. I guess, it depends on how you’re going to design your website. I found some interesting discussion on StackOverflow:
[1] (https://stackoverflow.com/questions/9721166/why-should-i-not-use-style-ids-using-css)

*I’ll update my comment if I find more resources.


#84

Just heard about the Cohort a couple days ago so I’m catching up on the curriculum. I’m stuck on the this exercise: https://beta.freecodecamp.org/en/challenges/basic-css/use-attribute-selectors-to-style-elements

Nothing I do seems to be correct. Any suggestions? I know it’s something super simple but I’m not getting it.

Screen Shot 2018-01-28 at 5.05.35 PM


#85

@codenoob What have you tried so far?