Glad that’s out of the way.
Building the site was easy enough but I found working with Git to be a lot of faff and bother here and there. This admittedly means there’s some more work for me to do in getting to know it; with a couple of caveats about a lack of clarity over what was required.
-
Although during the GitHub course we were asked to publish what I half remember as a dancing icecream or similar to our main GitHub .io address, it wasn’t clear if our portfolio page was supposed to be published from that repository or a new one.
-
The task hint said to use GitHub Pages, so I checked GitHub pages and it said users have an allowance of one free domain.
-
Having tried to publish from a new repository and it having not worked out, or hit a dead end to be specific, I inferred that given the wriggle room of one site, already occupied, the only option was to replace its files with the new repository, which I did, and lo, the dancing ice-cream was gone and the personal portfolio site is up and running at drowtaranis.github.io (excuse the silly name, I didn’t realise it was going to be a public username for my site, so picked something daft, never mind).
-
This was a great relief as I’d been faffing about trying up how to publish a repository with little joy. Part of the instructions was badly organised, advising me to go through the process of setting up a repository with no mention of going ahead and creating it, and then referring to the settings menu below the name, when no such menu was present during setting up the repository. I found it after thinking ‘well might as well create it’ and found the settings cog off to the right, east south east from the repository name. This might seem a minor quibble, but it was stretching the usefulness of ‘below’, particularly when combined with the lack of clarity over the settings cog being present during or after setting up the repository (which to my patience-thinning frustration sounded a prissy and long-winded word: a dynasty of eye-rolling tedium chained together into a cat-o-nine tails of syllables).
-
I’d been working in Git Bash to keep track of my changes, but it wasn’t clear (I half remember it saying the project was offline) if we were supposed to link working on our own systems directly GitHub so, for example, updating a change on Visual Studio Code and committing it would automatically update the repo(…that’s enough) on GitHub.
-
Then finally, the project says share your project on the forums and ask for feedback, while advising not to include a username, despite that being part of the only available URL for my site as far as I understood the task, short of buying a domain independently. So that seems like a conflict. Never mind.
Please excuse the slightly whiny ramble but my progress this week was more up and down than last week and it might be someone has had a similar experience and worked it all out. While understanding that a degree of resourcefulness and independence is expected and the rest of the course has felt very slick, I genuinely feel like this task could do with some more clarity, a spot of tidying up, here and there.
Any feedback welcome.
Anyway, it’s the weekend now, so have a good one, and here’s hoping next week’s smoother running.