Yes, if making a stack each user would have to get an api key, it’s spelled out in the agreement you can’t retrieve info for a third party. It also has to be initiated by an end user action (ie the end user would have to click a button to retrieve the nutrition info)
That being said it’s a pretty standard API. I would use Ajax POST to send the request and JSON, it returns JSON that you would then parse and add to the page using JS to target the page element to write that piece of data to.
I saw a related topic where someone in github has a jQuerry lib going, you may want to give that a search.
No, there is no need to use a CMS when only someone using Rapidweaver updates the site. There are several helpful stacks to publish things like recipes. Have a look at the Poster Stacks https://instacks.com/posterstack/ from Instacks. This allows you to create really impressive pages.
Just went through all the options myself. Ended up with Armadillo. Very happy with it. Just one thing, they need to add to the instructions that the MAIN armdillo stack needs to be on a different page than the main one you are using for your blog (or recipes). I found this in the troubleshooting section of instructions. I know Jonathan is busy, but I hope his response time for support becomes much faster – that’s the only thing. But again the 2 problems I had were solved by reading the troubleshooting section of instructions. A great stack! I recommend it! (also using Sentry for a simpler CMS and like that too). Nice work, Jonathan!
What gave you the impression that you can only post text with poster?
Yes some of the features you listed on the other post don’t exist in the RapidWeaver arena.
It does sound like some of the features would require a membership?
The automatically generated nutritional information API you’re listed is a paid per user product, starting at $299 a month. I’m sure you’d have to “track the user” to determine the licensing needed. Unless you found another product.
The “add to collection” feature would also point to someway for the user to login, and be tracked.
The vote or rating would be more accurate if it was done behind a login
You didn’t mention it but what about reviews? Again, a login to prevent spamming and fake reviews.
You could do something with IP addresses but those change.
Not sure how it would be setup in RW but on other sites for visitors, the collections are automatically stored in their browser for later reuse. For logged in users they are saved in the database and will be accessible from any device, when they are logged in.
I have seen several stacks that allow this but didn’t look at the details. If a login was necessary that would be ok. Doobox has a rating system that would be fine for our needs (actually they make two rating systems). Here is one:
My thinking now is that if I buy either Foundation or Foundry that I should be able to make a template that would work for posting basic recipes, but I also thought that I saw a video that said I could make a template like this with Stakes 4, so today I’m doing research to see if this is the case, and if it is then start working on a sample template to get my feet wet.
I’m also looking into the ‘developing stacks’ stack that was mentioned. If I could make a stack with the basic recipe template, then all I’d have to do is drag the stack to our page, fill in the recipe details, and it should be ready to post. Again, I still have to look into the details of this but at least I am hopeful that there are more options now to accomplish what I need to accomplish with RW. I was dreading having to use WordPress even if the plugins were really nice. Thanks for all of your help to think this process through.
The issue you are going to have with a template type setup is that every recipe will create a static page in the RW project (and on your site.) If you plan on having more than just a few recipes, this will very quickly become unmanageable.
For something like this you really need a CMS of some type that creates Dynamic Pages “on the fly” from data stored on the server in a database or flat file CMS system.
@AngelArs Poster is not a CMS. It’s a regular stack. But it’s kind of like a “master” stack that can help you organize/filter things by taking advantage of the blog structure (tags, categories). But unlike other blog options, for a specific blog post you can use almost all other stacks to create that post. So think of it as a special regular page. If you can create what you want on 1 page in RW (using other stacks, html code, etc.) then you can create it as a Poster blog item.
… here’s the difference: Poster will then organize all your pages via the blog structure. Create one poster item that can serve as the template and the rest will be easy.
The key is: can you create one page that does what you want in RW? If you can, then you can take advantage of Poster to create a much more complex offering of items all using the same template you created.
Sorry, I can’t answer that. Although I’m a big fan of Jannis @instacks, I don’t have Poster so I can’t comment on where/how the data is stored. If he is storing things in a flat-file system or database on the server and generating a dynamic page “on the fly” then it may be your answer. Jannis would be the best one to answer that.
The definition of a CMS is an application (more likely web-based), that provides capabilities for multiple users with different permission levels to manage (all or a section of) content, data or information of a website project, or internet / intranet application.
One of the largest misconceptions about CMS is that it is the main ingredient for a website’s success. That is completely untrue. A CMS should make it easy for a website owner or webmaster(s) to manage and distribute content, but a website’s success has nothing to do with CMS; it has to do with the quality of content, quality of services, marketing and many other factors Continuum 360
Database
A database is an organized collection of data, generally stored and accessed electronically from a computer system. Where databases are more complex they are often developed using formal design and modeling techniques. Wikipedia