Use Form to create new page - html

I am trying to find a way for a user to come to my site and fill in a form and when they submit the form a new webpage is made. I want to make it create a new webpage in an admin area so I can view what they have submitted without having to troll my databases. I am assuming this is possible because the concept is hardly new, but hours of scanning google has left me empty handed on any remotely close tutorial or anything of that nature. Perhaps I simply do not know how to word it, I am very new at forms but I am assuming this has something to do with the form action. Are there tutorials for this that someone can link me to or can someone give me a quick explanation? I can figure out the work for myself, I just need a point in the right direction. Thank you.

You're going to need to learn about 1) persistant storage (a database), 2) a server side programming language (HTML is purely for creating the structure of a web page), and ... I dunno, a lot more. I would suggest you actually look at a CMS (content management system) and see if that gets you where you want to go.
Databases don't interact with HTML in that way without some sort of application sitting between the site and the database. It doesn't have to be a PHP application, but something is going to have to store and get data from the db, and something is going to have to dynamically create these pages you want. And that's going to be some sort of programming language -- or a content management system like Drupal.
(Also, don't forget about security, support, etc. You write the app, you have to support it. =)

Related

Where to begin for filtering user's inputs to give result

I'm creating a website to be able to find the best result after a user has added their input. I'm newer to programming with only a few months in HTML/CSS and very light Javascript. Due to this, I am unable to properly word my question due to the lack of education so far, thus why I'm seeking advice here!
Best way to describe my idea is by an example:
User is looking for a dish recommendation to cook.
User inputs data (what they are craving, allergies, their cooking experience level, etc..)
Database filters through user's inputs to find the best result, giving them the dish they should cook.
Result is displayed on page for user to see.
If this is a hard to follow idea, let me know what the issue is and I will try to elaborate. I'm just unsure as to where to begin with this, what code-language to use, and how to go about to make my idea a reality.
Thank you in advance for any help/criticism sent my way!
You can go ahead with following steps:
Create mock up/ have an idea of how the screen will look.
Try to create that lay out in html css, css frameworks such as bootstrap can help you to quickly build that user interface.
Create some dummy data JSON and pull the data form that and make app working with Dummy data.
As you know JavaScript you can write backend code in node.js, identify the db you want to work on.
create a table structure / Schema for you data, as per database of your choice, you can use any freeware here, like mongodb, mysql etc.
Once this is done try to connect db with backend code of node.js
Code service/API in node to send data to front end view to display.

How do you incorporate Node.js/passport into my website?

I'm new to webdev and I'm trying to use passport for registration/authentication on a site I'm setting up. I'm also going to write an application in node later on that will be using some of the user data (users will need to provide an API key for an account on another site that I will use to pull data into the application).
At the moment, the main issue I'm having is figuring out what goes where. I've found plenty of resources that explain how to create an app using passport, but nothing shows how it would be incorporated into your website or where the files should be in relation to your website. I'm relatively new to Node.js, and while I've written a few small applications I have never hosted them anywhere.
Bonus question: I'm using MongoDB with passport and I was also planning to use it to store some JSON my application will be receiving from API calls. However, I wanted to use MySQL to store some data as well. More specifically, I'm planning to save the raw JSON then I'll create a relational database out of the data I need from the JSON and then keep the rest in MongoDB for easy access. Is this common/smart, or should I focus on keeping everything in my MongoDB? I'm relatively new to NoSQL.
Thanks in advance for any help.
I would reference this tutorial. I just recently used this to help myself with a new application. Also there is an example of the same thing but in SQL here. So not sure what you mean by " where the files should be in relation to your website". The information related to to authentication should go in your database.
To your "bonus question" you can use two databases. The key here is to ask yourself why and what are the true needs for data, and how is this data accessed and used. From ground up I would like one and stick with it. If at some point later you realize a certain type of data would be better in a different database then you can add it.
Side note: look into an IDE such as webstorm to help you out.

Accessing database content based on /variable

So I am a bit new to MYSQL and I've been learning allot more about relational databases but I am a bit stumped with one subject in mind. I notice allot of sites have things like domain.tld/variable. I understand how this works by using /?variable=name but most users would never use that. So how does one go about letting users pull content based on the principal listed?
Actually, that has nothing to do with databases.
When the url is accessed, url rewriting is used to change the url behind the scenes. While the user enters domain.com/data, the php script (or anything else) at domain.com?variable=data is opened.

HTML Update News Page

I have a site which is basically a few HTML Pages. I no have a requirement to create a facility where a site admin can create and maintain a News section.
I am just pondering what my options are? It needs to be a fairly simple process to maintain news items and ideally not be database driven. Although I'm struggling to see how I can achieve this.
Any help is much appreciated.
Thanks
CuteNews should do what you want. It uses a flat file to store the news items so you don't need a database.
Not sure I understood well, but if you mean you have news in static HTML pages and you want to update them, without doing it by hand, you would have to write a script that creates new ones or updates the existing ones, but that's all too complicated in my oppinion.
The way to go is Server-side language (PHP, ASP etc) and database (MySQL, PostgreSQL etc).

Sharepoint - Can You Output Unfiltered HTML from a Database?

Our customers have asked for Sharepoint and, of course, we are having to implement features for which Sharepoint wasn't really designed. We are first trying to stretch the in-house webparts as far as we can, so we are doing a lot of the work in stored procedures, user defined functions, and custom views in the MSSQL DB.
I am generating html links from fields in the database and wish to display them in something like a Data View web part. Of course, all of the data being displayed is being filtered so that it shows up as unrendered HTML. Is there a way around this?
Alternatively, is there any type of web part that can connect to another webpart or Data source and display unfiltered text/html from that source?
You need to use the XSLT in the dataview webpart to control the rendering.
You have full control over what html is created. disable-output-escaping if necessary.
I get a feeling you’re customizing SharePoint the wrong way. Either that your I don’t really understand the description of your question. I would appreciate a more detailed description of exactly what you are trying to accomplish.
As far as I know you should NEVER touch the SharePoint database directly. I think you should focus on creating lists, field types, WebParts and whatever SharePoint components you might need; instead of messing around in the content database.
SharePoint got a decent development API. It takes some time to learn, but in the end it’s probably worth it.
You can connect your custom made WebParts in SharePoint, here is a sample.