HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html>
tag. If you want to add classes there that can affect the whole document, this is the place to do it.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. If you need things in the <head>
of the document, put that code here.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.
To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit-
or -moz-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
Any URLs added here will be added as <link>
s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.
You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
Any URL's added here will be added as <script>
s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.
You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.
If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.
You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
Search for and use JavaScript packages from npm here. By selecting a package, an import
statement will be added to the top of the JavaScript editor for this package.
Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
<h1>Styling a Bootstrap Button for File Uploads with Filestack</h1>
<p>
This CodePen provides an example implementation of the code
mentioned on the Filestack blog post here:
</p>
<p>
<a href="https://blog.filestack.com/tutorials/beautiful-bootstrap-file-upload/"
target="_blank">https://blog.filestack.com/tutorials/beautiful-bootstrap-file-upload/</a>
</p>
<p>
Before you can run the Filestack File Picker, you'll need
to enter your <a target="_blank" href="https://dev.filestack.com/signup/trial/">Filestack API Key</a>.
</p>
<p>
1.
<button id="set">Set my API Key</button>
<br/>
<span id="fsapikey"></span>
</p>
<p>
2. Check out these Bootstrap Buttons!<br/>
<button id="standard_bs_button"
class="btn">A plain Bootstrap Button</button>
<button id="bs_button"
class="btn btn-primary">Primary Bootstrap Button</button>
<button class="btn btn-filestack">We can style it, too!</button>
</p>
<h2>Our final result:</h2>
<p id="final_result">
<button id="final_button"
class="btn btn-filestack btn-widget">Pick a File</button>
</p>
<p>
Read more on the Filestack blog:
<a href="https://blog.filestack.com/">https://blog.filestack.com/</a>
</p>
<p id="clear">
[<a href="#">Clear my APIKEY from localStorage</a>]
</p>
/*
Example Styles
Read these comments for some additional context, or scroll to the bottom of this box to view the styles.
*/
/* Where's Bootstrap?!
CodePen allows you to import external resources via configuration options, and those do not display in the code boxes here. Click on the gear icon next to the words CSS (SCSS) in this code window, and scroll down to where you see "Add External Stylesheets/Pens" in the CSS tab. See that text field with `https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.1.3/css/bootstrap.min.css` listed? That's where Bootstrap is being imported. Well, the CSS at least. That's all we need for this example! The rest of what is here is custom styles to support the blog post here: [link]
*/
// This looks weird!
/* Yup. This isn't CSS, but it is very close. This is SCSS. We didn't go crazy with it, though - you can just substitute the SCSS variables used in the body of the styles with actual colors and you'll have "regular CSS" if desired.
/*
/* Feel free to change the background-color and border-color to fit your website's color scheme */
.btn-filestack {
background-color: black;
border-color: #ee4632;
}
.btn-filestack,
.btn-filestack:hover {
color: #ee4632;
}
.btn-filestack:hover {
//background-color: #330000;
box-shadow: 0 2px 2px 0 rgba(256,256,256,0.24), 0 6px 6px 0 rgba(120,120,120,0.19);
}
.btn.btn-filestack:focus {
color: #fff;
outline: none;
}
.btn-widget, .btn-widget:active {
font-family: "Open Sans", sans-serif;
font-size: 12px;
font-weight: 600;
border-radius: 17px;
padding: 4px 30px 5px 40px;
height: 34px;
/* Set the path of your logo */
background-image: url('https://www.filestack.com/favicon.ico');
background-size: 16px 16px;
background-position: 16px 8px;
background-repeat: no-repeat;
line-height: 23px;
}
.btn-widget::after {
position: relative;
content: "\21a9";
color: rgb(239,74,37);
top: -0px;
right: -11px;
width: 1px;
height: 12px;
background: 0 0 no-repeat;
}
/* Additions */
body {
background: #181325;
color: #ee4632;
font-family: monospace;
padding: 12px 12px 24px 24px;
text-align: center;
width: 80%;
}
h1 {
font-size: x-large;
}
h2 {
font-size: large;
}
h1, h2 {
font-family: Verdana;
padding: 12px;
color: white;
}
#final_result {
margin: auto;
padding: 42px;
width: 80%;
border: solid 1px red;
}
#clear {
font-size: small;
}
// Example JavaScript
/*
These styles and behaviors don't require JS to work.
The File Picker does, so you'll see a little code that
calls that into action.
There's also a little JS code at the end that handles
different Filestack API Keys.
*/
var apiKey = localStorage.getItem("apiKey");
// That line needs to be above the others so your APIKEY gets used
var fs_button = document.querySelector("#final_button");
fs_button.addEventListener("click", function() {
var client = filestack
.init(apiKey) // That's where we're using the localStorage <<--
.picker({
fromSources: [
'local_file_system',
'url',
// 'imagesearch',
'facebook',
'instagram',
'googledrive',
'dropbox'
]
}).open();
});
/*
API Keys are just for you. While security is not based on keeping your API key a secret (there's an actual 'secret' for that), it can be confusing to share code examples that depend on that key when you're supposed to be using your very own key. To help keep that all sorted out, this code creates one step you need to do before this project can run: enter your Filestack API key. It is based on the official recommendations found here:
https://blog.codepen.io/2017/08/10/window-prompt-localstorage-api-keys/
*/
var s_button = document.querySelector("#set");
var div = document.querySelector("#fsapikey");
var apiKey = localStorage.getItem("apiKey");
if (!apiKey) {
div.innerHTML = "";
} else {
div.innerHTML = "My Filestack APIKEY: " + apiKey;
}
s_button.addEventListener("click", function() {
apiKey = prompt("Enter API Key:");
var myApiKey = localStorage.setItem("apiKey", apiKey);
div.innerHTML = "Filestack APIKEY: " + myApiKey;
});
var clearlink = document.querySelector("#clear").addEventListener("click", function(){
if( apiKey ){
localStorage.removeItem("apiKey");
div.innerHTML = "";
}
});
Also see: Tab Triggers