Page path builder
Uses a page.js-style routing string to build up a path you can link to
Hooks up a click event to all Studio signup links on page, and sets a cookie with the current page path.
Automatically tracks page path changes and creates redirects via Gatsby's createRedirect action from the previous paths to the new paths
PostCSS plugin postcss-page-break to fallback `break-` properties with `page-break-` alias
Access memory using small fixed sized buffers
Simple development http server with live reload capability
Create api documentation for TypeScript projects.
UTF-8 only polyfill for the Encoding Living Standard's API.
Gatsby plugin that automatically creates pages from React components in specified directories
Provides a fallback for non-existing directories so that the HTML 5 history API can be used.
fast string hashing function
Wrapper for the Page Visibility API
Turbolinks makes navigating your web application faster
A React utility belt for function components and higher-order components
Material Design Icons DX
just the global object
Library to find elements in a dynamic web page
A utility to time how long a user interacts with a page, disregarding time spent on other tabs, minimized, or idle time.
simple development http server with live reload capability
Scrape documentation frameworks to Mintlify docs
Gatsby library that helps creating pages
PostHog Node.js integration
Index generator for Hexo.
Provides a tag that can be used in gollum to output descedants of the current page
Easy collect source paths of all images on HTML page
Authorizes server to server account and returns X number of most viewed pages by path
Accounts::Server defines the following paths for your web-app: * POST '/logon' * POST '/register' * POST '/forgot-password' * POST '/change-password' * POST '/change-email' Your app must provide the pages and forms that will post to these paths.
A boilerplate is a markdown file you place under the `_boilerplates/` folder to generate new pages for jekyll. It can automatically timestamp and title new pages. It will also replacing any `{{ boilerplate.xxx }}` tags with content. Available tags include `.time, .title, .date, .random`. You can also provide custom tags with `boilerplate post nav_order=1` > `{{ boilerplate.nav_order }}`. In the boilerplate header you can specify options like the path to generate pages under and if filenames should be timestamped. `_boilerplate: > path: '_posts/'`
Convert statement HTML from the Co-operative bank's online banking system to OFX for import into financial apps. = Usage For a Current Account: 1. Save the HTML source of the statement page. coop_to_ofx --current /path/to/statement.html Will produce /path/to/statement.ofx For a Credit Card: 1. Save the HTML source of the statement page coop_to_ofx /path/to/statement.html Or coop_to_ofx --credit /path/to/statement.html Will produce /path/to/statement.ofx To produce OFX 1 SGML (rather than OFX 2 XML): coop_to_ofx --ofx1 /path/to/statement.html coop_to_ofx --ofx1 --current /path/to/statement.html To show all the options: coop_to_ofx --help == To do XML / SGML validation of output against the specs
RailStat generator creates a real-time web site statistics system. Features: - Page views paths on each session - Number of total hits / unique hits - Operating system and browser - Countries and languages - Referrers and search strings - Flash / JavaVM / Javascript / ScreenWidth / ColorDepth
I know you're always always in the middle of doing something with HTML, js and CSS, but want to use real server-side paths. I know how it bothers you to set up Apache, nginx, IIS, SOMETHING, just to see your pages and apps blossom. volna lets you run a server for a given path on a fixed port, no sweat. You're left with the clackety sound, now.
A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.
Sinatra::Head provides class methods and helpers for dynamically controlling the fields in your <HEAD> element that are usually preset in your layout: the page title, stylesheet and javascript assets, etc. Asset lists are inherited throughout superclasses, subclasses, and within action methods, and basic asset path management is supported.
If you're running a javascript single-page-app with html5 routing, you may notice that deep links will 404 unless your web front-end is configured to rewrite all non-asset paths to index.html. If you'd like to achieve the same rewrite using rack, this is the gem for you!
One important feature of DHTML is it's ability to move elements around the page freely, without having to be tied down to one single spot on the page. "Virtual Max" took full advantage of this feature and created his cool "floating images" script for our Dynamic Drive surfers to use and enjoy. It's a cross-browser script that moves any number of images around the page (by wrapping the images inside <div>s, and animating each <div>), each following a randomly determined path. Furthermore, the images are clickable, making this script not only insanely cool, but practical as well!.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.