i used Array too.
I you want to tweet the very first quote it doesnât work. I tried a few times.
As many have already said, as long as you fulfil the user stories its all good.
Personally I used an API. I think you will learn a lot more doing it with an API. It got very frustrating and a lot of googling was involved but I feel it was time well spent plus it gave me a lot more knowledge for the other API challenges.
All the different APIâs will have their unique challenges and I wouldnât want you to miss out on the fun
I am too having problems with this challenge
I think my issue is with the actual lessons.
For the past set of challenges, I was able to use what I had already learned
I didnât like the JSON and AJAX classes, I was just typing as told and not understanding properly.
While I imagine that as long as you pass the use stories it will be ok, I also imagine the idea is to use the AJAX/JSON/API skills to do this.
I am trying to find non FCC tools to learn those things so I can use them here.
Hello ZackWard,
Can u please share your json file, as I want to try your method for this project.
@sanjana-1604 Sure, you can find it here: https://assets.zackward.net/ron-swanson-quotes.json
One thing never mentioned about this project is the 140 character limit of Twitter. So itâs useful to add some kind of alert when you click your tweet button whenever the quote is too long. Also, your API should preferably come from an HTTPS source. For one thing, if it isnât it wonât work in Codepen.
Hello,
It makes much more sense to use APIs simply because of the large amount of data made available to you through them. Thatâs whatâs so great in using APIs: you can return a large chunk of data through one simple hit. I strongly recommend you get familiar with them as they will benefit you greatly.
On the other hand, the project can surely be built with arrays, but it will somewhat be limited compared to using APIs (think of the limitation of populating/updating your array with a number of quotes).
Whichever way you choose, it is a good opportunity for you to learn how to manipulate and display data. I even recommend you trying both implementations if you have the time and patience so that you can understand the different skills at play.
Cheers and best of luck,
Hanna
It worked just fine for me when I clicked the pen here in the forum. But great job
Haha! Whyyy did you build your portfolio site like this? Please let me pause the music intuitively! I thought the pause icon in the top bar would do it, but not on my end. Then I sought out an iTunes app but couldnât find it.
I agree with the sentiment that itâs a good opportunity to use public APIs to get used to using them. But I also think with these little projects that your interest is going to be much higher if you can make it relevant to something youâre interested in â which if you can do with a public API, great!
I made one using a collection of some artistâs quotes matched with images of their work for the background, and that made the project exciting for me. Now youâve got me rethinking it though and maybe I could do something with the SFMOMA API.
Ultimately â it doesnât matter what you do, so long as whatever you do, you do it the best you can, you enjoy doing it, and you learn something from it.
Haha⌠I was just playing around. Thereâs a Youtube video playing in the PULP Tribute âwindowâ. Scroll down within that window.
Oh! I didnât realize I could scroll in there, haha. Good stuff
I made the random quote machine initially with an api. Then I realized a lot of random quotes wonât fit tweet specifications. So when I went through a week of feeling depressed, I decided to make a random quote machine with an array of motivational quotes. Gave it more of a personal flair by using some quotes that I actually am inspired by.
I felt the second way was better even if you donât have as much access to quotes compared to an API. Thereâs more personality to it.
Had no clue what APIâs were and how to use them so I did the challenge first with arrays. Spent about a month relearning jquery and html to get a better base. Along the way watched a few youtube videos and figured out what in the world these API things were and how to use them. Eventually built a nice little generator. If I have one complaint with FCC itâs how APIâs were taught. Looking back on it, itâs a bit clearer but my first time it just looked like complex gibberish. Ditto for Jquery. Everything else Iâm pretty pleased with.
Now you could challenge yourself to adjust the quote string to make it tweet-ready if someone chooses to tweet it
All the quotes I put are tweet ready.
I can only think of two ways to do that: Filtering all tweets that are two long or cutting some quotes short. Which do you mean?
@wtkwon & @ayembocx I mean implement the truncateString algorithm from the Basic section to chop quotes that are too long, add a trailing ââŚâ before pushing to the tweet.
That would make quite a few quotes look awful. Itâs not hard to implement that, but cutting off quotes can take away their meaning.