I18NMixin
--
-
- - Install the mixin via yarn or npm: yarn add @lrnwebcomponents/i18n-manager - -
- - create a folder in your element called /locales - -
- create a file called my-element.es.json for the spanish translation of your element. Japanese would be my-element.ja.json for example. -
This invokes a dependency on our manager which you might not want to have in your element. If you want to do a similar approach but without dependencies, you just have to feed a custom event to our manager. You'll still have to use the convention for translatable text, but here's how you can invoke the event needed
-Using the vanilla approach, you'll still need to have a /locales directory and the same naming convention. Our mixin just simplifies the integration a bit as well as the timing of what it's initiated but this event registration method will still work within any element that's going to arrive in HAX/HAXcms or any property you make that isn't using HAX at all.
- ]]> -Because of the simplicity and power of - haxHooks - this may not be an exhaustive list and - - the internal code documentation on this should be consulted - (or open an issue to ensure we document a missing hook!). You can search the lrnwebcomponents monorepo for usage of haxHooks - in order to discover additional implementations beyond what is pointed to below.
-- Blog posts about this topic -
--
-
-
- haxHooks(): How elements can supply their own editing experience in HAX now!
-
-
- -
- haxHooks: webcomponents that ship their own editing UX
-
-
-
-Code example
-- This is a basic example in which each of the strings you'd then implement as their own async - callbacks. async - / await - allows HAX to safely defer to your element to do whatever it wants to the DOM / internal structure of that callback, without disrupting element activation or conversion of DOM structure to HAX Element Schema, what it uses to virtualize the body for sanitation - purposes at the time of save / adding new things to the page. -
-- gizmoRegistration(store) -
-The most powerful hook in haxHooks. This fires whenever an element is read in via the appStore and it's definition loaded for use. This hook supplies an instance of the HAXStore which is the internal state management of HAX (written in MobX). You can use this object to do whatever you want to HAX. While seemingly too powerful, here are some examples of past things to leverage this super power for good
--
-
- - code-sample - - the code-sample tag uses this hook in order to inject additional shortcut logic. If the tag is supplied, things like - ```js - will convert to a JS based code-sample. It also hijacks the baked in support for - ``` - in order to inject a code-sample tag instead of the default - code - tag - -
- supplying "apps" based on tag - - wikipedia-query - and - github-preview - supply custom public API search endpoints based on their tag being loaded. This way you can use the "Media" menu in order to search Github or Wikipedia in HAX just by including these tags in your autoloader block of the appstore. - -
- supplying translatable haxProperties - - meme-maker - and - twitter-embed - supply custom translations for their haxProperties. This means that if you were to edit these elements using the editor in Spanish (es), you would see the fields and example inputs in Spanish (es) as opposed to their English (en) default text supplied by the - static get haxProperties() - method. - -
- activeElementChanged(element, value) -
-This runs whenever a user activates / selects an element to modify in HAX. This supplies an instance of the element / DOM node that is active as well as if we are active (true) or inactive (false). This hook can be used to modify state / functional aspects of your elements just prior to it receiving activation by hax. An example use-case for this could be preventing default behavior for an element that is a clickable link (see: - ebook-button -). Another possible usage is making pieces of the internal - shadowRoot - - contenteditable -, only while activated (see: - meme-maker -). -
-- editModeChanged(value) -
-This runs on all active nodes in the - hax-body - tag when the editing state of the HAX editor itself changes. If we are now editing, value is - true -, when we go to save / are no longer editing, it is - false -.
-- inlineContextMenu(ceMenu)
-This hook runs after element activation in order to allow elements to supply custom editing buttons and operations to the in-context menu that hovers above active elements. You have access to the instance of the custom elements hax menu element (hax-ce-context) and can add whatever buttons you want at this time with custom callbacks. See multiple-choice - for an example of how you can leverage this. multiple-choice - uses this to add quick buttons for adding and removing potential answers quickly.
-- preProcessNodeToContent(node)
-This runs right before nodes are converted to content in the entire hax-body. This happens when the user has triggered a save event and we are converting the DOM from real nodes into the HTML text that is to be saved / returned to a backend. This hook allows you to do any known data clean up to the element prior to it being converted to HTML. See multiple-choice - for an example of taking a complex data property and converting it to innerHTML children at the time of save for progressive enhancement purposes.
-progressiveEnhancement(element)
-This hook runs WHILE the node is being converted to text and should return a string that will be appended into the innerHTML area of the element. This is an alternative to what you could accomplish during preProcessNodeToContent but want to work with a string based response. See meme-maker - for an example of using this to inject innerHTML which only is for SEO purposes.
-- postProcessNodeToContent(content)
-This hook runs after preProcessNodeToContent and progressiveEnhancement and before the element is returned in the hax-save event. This runs AFTER the node has been converted to content. This is useful for forcible content clean up like regex'ing output for specific words to not leak into output. See video-player - for ensuring there are no internal empty arrays for data is not a required field.
-- preProcessInsertContent(detail)
-This is a hax schema element, our virtual dom node, that is about to be inserted into the hax-body. This allows for custom modification to the data that's about to be converted to a DOM node. See multiple-choice - for an example of ensuring that answer data doesn't bleed through to the page. This hook runs on duplication as well as inserting a node by the user selecting the block.
- ]]> -Create a new repository from hax11ty -
-It even has github actions support built in! Meaning you can check out the mini-doc site for HAX11ty - which is self-updated when we update the docs / repo for HAX11ty.
-This video shows - early work on HAX11ty by Michael Potter
-Normal HTML Paragraph Tag
-
Meme Tag
-
Notice with the meme element that it now has additional fields which when changed are reflected in the page instantly!
- ]]> -
]]>
- This roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements and next steps for the different projects in our wheel house.
-
As you can see, there's a lot of planned enhancements to HAXeditor and HAXcms with a lot of additional future capabilities in ELMS:LN as a result of these projects. It's important to understand these relationships through and how innovations flow between them.
-Relationships of major pieces
-HAX has many different parts detailed here, so let's look at the relationship between these pieces before getting into the roadmap. HAX projects are part of the ELMS:LN organization and so ELMS:LN is also included in these roadmap details.
-HAXiam, HAXcms, HAXeditor are three projects that make up the "HAX" name space, all of which benefit from being built on web components. HAXiam is a server technology while HAXcms is a mix of server and front end assets. HAXeditor is fully front-end code which then requires a backend to save and load pages from.
-Below is an image consolidating information found on this site with arrows illustrating flow of innovation. Web components are always our building blocks, usually bubbling up as a need in either ELMS:LN, HAXcms or HAXeditor. From there, HAXeditor influences and improves ELMS:LN and HAXcms. ELMS:LN has a copy of HAXcms inside of it so sees improvements from both platforms. HAXiam just makes sure that copies of HAXcms are generated.
-
Now with this foundation you can dig into the different pieces of the project roadmaps.
- ]]> --
-
- Get the HAX plugin - from the wordpress registry -
- Go to edit / create a page/post and you are HAXing -
Installation video
-This shows installing it manually if you can't get it from the wordpress store!
-HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web components.
-
-Features
-- Micro-site manager, so manage multiple sites from a single HAXcms install -
- Each site is powered by static files which live in version control -
- Every change is executed by the front end via HAX / Outline tools -
- Every change is automatically tracked in version control (zip the folder and send it to a friend and it'll work) -
- The "database" is powered by a site.json file that lives with the site -
- All operations write to static files so every change is as if you editing HTML by hand (but you didn't... HAX did) -
- Ability to serve up as a static site on CDNs (this site is on GH pages + a CDN) via Publishing which makes a purely static copy with a service worker and the whole jazz for offline / installable capability (0 config) -
- Build your own themes via custom front end dev if you like or use one of our baked in ones -
It is a flat file generator with a UI and the UI contextually loads based on if you should see it. It's weird, we know, and that's also why we have trouble describing what it is. It's a flat file CMS without tooling required. It's a sustainable way of building and maintaining a "CMS" as it has multiple pages, can handle custom fields, custom themes, but yet it doesn't require infrastructure to keep running beyond PHP / node / Beaker browser to act as a back end to edit the static files.
-It's an organic CMS. A living yet permanent website. It's hacking the limitations of content authoring capabilities. It's why we say, we're HAX The Web.
-Core Principles
-- Support all platforms and devices (CMS, App, etc) -
- Empower authors to write code without ever looking at code -
- All content produced must work with or without HAXeditor available -
- Support older markup, regardless of structure, as best we can -
- HAX will learn the rules of producing elements, it won't dictate them -
- Decentralize all the things, empower all the peoples -
Cross platform
-Because we've adopted the web component - - standard in the development of both HAX (authoring system) and HAXCMS (content management), everything we create and compile via our open tooling - can support about 98.4% of all browser traffic globally without server side rendering. HAXcms also employs a progressive enhancement methodology meaning that it can hit 100% of all browsing traffic with content.
-This means that you can use the latest and greatest of the web and not have to constantly worry about a library changing! The dawn of the age of web components is now, join the revolution!
-Platform support
-- Evergreen
- browsers
- (93+% of traffic) - no polyfills!
- IE 11 / Edge <18 / legacy browsers - polyfills with simplified design -
- See F.A.Q. - for a more detailed break out of stats -
No content lock-in
-The elements that make up HAX can be delivered via a CDN or installed locally. This means that the functionality is tied to the browser - - and NOT - - to the platform itself (huh?). Well, think of all the complex functionality of any site you've ever built or used. Then add content to that site. Now move that site (in your mind) to another server. What has to be migrated to maintain the content functioning that isn't actually content?
-For example, take this quiz:
-*by wearing a cool jersey - - - - -
We're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next event to join the movement!
-Past winners rocking their merch from completing the hunt!
-- @onelittlebecca - - - - - at DrupalGovCon '19 - - - -
- @JProffitt - - - - - at DrupalGovCon '19 - - -
- @natefollmer
-
-
- - IRL Aug '19
- page load, should it be no-js or a web component delivered, preflight -
- haxcms-site-builder loads site.json, reads JSON Outline Schema and starts to bootstrap that into a theme, items, title, etc -
- Appends a haxcms-editor-builder tag which checks for "context" -
- Context is established based on global values for php, nodejs, beaker, etc
- Uses a login end point to check if there's a JWT in the user's local data -
- When it finds a backend, it injects a tag to bridge that backend - -
- HAXeditor gets injected into the correct place in the theme which then all of that unpacks and does its thing -
Event driven architecture
-HAXcms allows for jumping in at different core operational steps and reacting to these changes based on an event driven design pattern. This means that an event "fires" in PHP, much like it does in JavaScript and code written to react to it can make changes at that point in the operation.
-Here is an example from HAXiam which implements custom configuration event listeners
-Core listeners
-Core listeners to influence how the data is constructed. You can add these to your _config/config.php file
-- haxcms-init - - just after HAXcms bootstraps its initial configuration -
- haxcms-site-metadata - - when constructing metadata block at the top of the document -
- haxcms-connection-settings - - for authorized users, this is the block of end points for connecting to and modifying HAXcms logic as far as where data flows. -
Enterprise integrations and SSO
-The following hooks allow for supplanting the HAXcms (intentionally) simplistic login system. This allows you to do custom integrations for your organization. HAXiam implements many of these - if you need specific examples.
-- haxcms-login-test - - when a login didn't pass our simplistic built in checks. Useful for enterprise integrations and other SSO methods of access -
- haxcms-validate-user - - same as login-test except this fires to validate every transaction to ensure the user name matches when decoding the JWT -
- haxcms-jwt-get - - when we ask for the JWT. This allows SSO to supply the token manually via a different methodology than our core one -
- haxcms-refresh-token-get - - when our connection is deemed needing to refresh, this supplies the refresh token for when and what that looks like -
I installed HAXcms and forgot my password
-Your username and password can be found in _config/config.php on the server (assuming local development)
-I clicked login and nothing happened and now I'm locked out.
-- Clear your browser cache. A cookie is set that might be invalid. - -
- Open a new browser and try to login again -
I clicked publish and nothing happened
-- Publishing can take up to a minute or so at times since it's creating a commit, rewriting files and then the front end is waiting on the push to github before it triggers a successful response. -
- If it did fail to publish, you might not have git setup. Click the gear icon on the dashboard (site listing) and ensure you've setup github / git integration correctly. -
Realize that everything is just a file and that our json outline schema is very easy to read. So if there's an issue with something related to publishing, check _sites/mysite/site.json for publishing, then _config/config.json. All settings and variables cascade in this way. Settings are stored globally, then replicated locally to allow them to be pealed off and more easily imported / exported into other setups.
- ]]> -Workflow
-- Make a new site in the HAXcms UI - -
- Select "Custom theme" as your theme -
- In the file system go to _sites/mynewsite -/theme -
- Edit theme.html to modify the structure -
- Edit theme.css to modify the design -
This is the easiest way to skin HAXcms to your liking. It's able to ship and work in CDNs and is the minimal barrier to entry for those used to seeing HTML and CSS files that they can touch and see the change. It requires no tooling to utilize either!
-- All custom theme work happens in your _config directory - -
- Make my-theme.js, pull everything together, either in this directory or in a wcfactory - catalog of elements you've made -
- Reference this in you _config/my-custom-elements.js element -
- Update the _config/config.json block that says themes - to include something like... -
This tells HAXcms UI that you can now select the theme (but don't yet, it won't be valid)
-Local development workflow during theme development
-We use polymer cli to serve up and work on web components locally and while you don't have to, it's recommended as part of the WCFactory workflow.
-- Make a new site in the HAXcms UI - -
- Go to _sites/mynewsite and run polymer serve --npm --open --entrypoint dist/dev.html - - -
- Adjust the URL that opens to only be the IP address with no path after it -
- You'll see your site open up for local development work, which will be leveraging any assets referenced in your node_modules directory at the HAXcms project root. -
- To add / install new assets run yarn (or npm) add @what/ever-you-want --save -, just like you would any other project you work on in FE dev -
- edit your site's site.json manually to update the theme to point to the theme location your actively working on -
- Develop away until it is to your liking -
Shipping the theme
-To ship the theme, you'll need to do a polymer build routine
-important note
-This currently forks you from the original source of HAXcms core (because it will recompile the assets). If you're ok with this cool, just know we're trying to find ways around this involving rollup -.
-- Go to the HAXcms project root - -
- run polymer build - - -
- Copy the build directory and go to your site -
- Delete the symlink and replace it with your build directory -
- Now you can publish via the UI so long as you do not leverage a CDN -
The future
-Admittedly, the full on custom theme / web component development workflow is rough. It's hard to maintain a built copy in a modular system without tooling. In the future we plan on having tooling workflows built directly into WCFactory that allow you to streamline the development and creation of HAXcms themes.
-Current limitations
-You can't leverage existing CDNs (like webcomponents.psu.edu and whatever else is out there) that are pegged to the HAXcms project's source. You'll be creating a custom theme which then creates a custom build in effect so you'll want to ensure that you have some place that you can host the assets in order to power your site.
- ]]> -A note about @apply
-Unlike normal css variables, Polymer (the library we build our theme layer on) supports a convention for CSS variables that operate a bit more like Saas mixins. You can write blocks of code like @apply --my-variable-blob; - which will then allow someone to mix in and apply whatever valid CSS attributes they want at that level. You can see several implemented below (both CSS variables and @apply blocks).
-Example
-This is an example from the haxcms-basic-theme -which forms a clean baseline for most sites.
-Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that now. The site- - - - - query elements are incredibly powerful aspects of HAXcms theming that deserve their own section anyway.
-site-query - -
-Code Example
-Spoken Example
-"Give me all of the
-When it's useful
-Always. This is by far the most powerful element in our library. It can query the site structure and effectively return anything, anywhere that matches the criteria. It is for exact criteria matching though so you won't be getting children of page X unless you specifically requested them.
-This is great for getting things like getting all the pages that don't have parents (top level items) which is exactly how the site-top-menu - - tag does it in conjunction with a dom-repeat tag (in that example).
-Caveats
-- This doesn't render anything by itself - - -
- You have to then know how to do a two way template bind (Polymer convention looking like {{result}} - -or know how to use javascript in order to bind the results to visual output - -
- Its incredibly powerful - -
A menu slice query is one which takes part of a hierarchy and chops it out to return the items.
-Spoken example
--that are 2 to 4 levels deep. -
Delivered results
-Dynamic leveling
-The dynamic leveling flag would allow you to create a query that analyzes the current active item (as example). And then say "Always give me 2-3 levels below this". In that instance you've got a dynamic sub-set of children being returned.
-When it's useful
-This can be useful for a block that always shows the children of the current page in a documentation site.
-site-render-query - -
-A site render query attempts to standardize the practice of wiring site-query up to something visual. It requires you supply something visual to get going and has the unfortunate limitation though that what you render must not be dynamic in nature.
-Example
-
-
-
-
-
-
-
- description: [[item.description]]
- location: [[item.location]]
- changed: [[item.metadata.updated]]
-
- Set as active
-
- When it's useful
-When you have a static set of items you want to query once and have it be dynamic based on site infrastructure yet not be changing dynamically during site view.
-Possible usage
-As we haven't rolled this into any themes at the time, this could be useful for placing a "latest posts" block or "upcoming events" block. Anything that's dynamic based on the data being passed in but yet unchanging once it's loaded. Think of this as a simple "views" construct if you are from the Drupal worldview.
- ]]> -Import classes / web components
-As you can see this theme imports a few basic components helpful in the development of most themes. First we import PolymerElement and the HAXCMSTheme mix-in from our theme wiring library. Theme wiring provides a basis for wiring any custom element into the state management of HAXcms, typically without having to deal with any concepts of state!
-Mix-ins
-Next we get the mix-in statement. Note how HAXCMSTheme wraps the PolymerElement class, thereby giving us a mix of the two together.
-HAXCMSTheme mix-in class
-You can learn more about what the mix-in class provides by digging into the HAXCMSThemeWiring.js - - class. This class bridges the HAXcms store (written in mobx) with the design layer. This way you can leverage anything in the store by writing the polymer convention for referencing a data bound variable in the template.
-Here's the variables you'll commonly see - - in our themes, direct from the store with an example of what a dom bind of that would look like in a template
-[[siteTitle]]
-[[ancestorTitle
-[[parentTitle]]
-[[activeTitle]]
-
- [[activeItemFields.images.0.url]]
-
-That last line with activeItemFields is part of the raw power under the hood of this approach. You can use HAXcms to create field definitions (in HAXschema - -) that then extend the capabilities of your pages.
-Required CSS
-There is one small required block of CSS when doing web component / theme development for HAXcms. It is the following:
-This helps ensure that when your user clicks the edit button that they see the HAXeditor as opposed to the body of content they are currently working with. Then when they hit save, the HAXeditor sends the content to the backend which then updates the front end and they see the changes. This CSS ensures that it isn't visible during editing.
-Required HTML
-
-
-Related to the CSS, the following block of HTML must appear in your template somewhere (or in the case of simple-blog -, an element leveraged by your theme). You can make this look like whatever you want beyond this but this ensures the HAXeditor can correctly target and be integrated using the HAXCMSTheme mix-in. There are ways to position and reposition the HAXeditor dynamically that will not be covered here but can be seen in simple-blog -.
-From there, design away. Write whatever CSS and HTML and JS you want! The example themes referenced in our docs all provide blue prints for different ways of leveraging our template system.
-Next we'll discuss our Core template elements which you'll want to leverage in order to make theme development even cleaner!
- ]]> -- Join us on the HAXTheWeb Slack - channel -
- Join us for HAXcamp Un-code - every Friday 3 pm - 5 pm (EST) -
- Follow / use the #HAXTheWeb hash tag - -
Join our projects
-- HAXcms - - That which powers this website -
- Unbundled-Webcomponents - - A methodology for building and deploying web components to CDNs that we use in all our projects -
- Web components monorepo - - That which powers our editing experience (and all our other tags for that matter) -
- WCFactory
- - Build and maintain your own web component library, why should we be special.
- Check out our integrations page - for platform specific repos -
Organization that wants to get involved?
-Great! Here's some of the best ways for organizations to try "HAX" and get involved in the project.
-- Reach out to any of the members of the core project team on our slack -. We're happy to do conference calls to forge partnerships especially around HAX or OER production solution though it has implications for any public site! -
- Try out the HAXcms live demo - (reset hourly) -
- Reach out in the issue queue - with questions -
- Bring this website to developers in your organization or other code junkies and tell them to explore -
- Host a HAX camp - (ask for more details) -
HAX makes up multiple projects across hundreds of web components and various other repos. It can be a bit overwhelming but we want you to imagine something... Imagine being a developer on HAX.
-Step 'ight up
- 
- urz te next contrib
Because all it takes to get involved in HAX is, that's right, showing up in our repos and getting involved! Yes you too can be just as meme-able as we are!
-All things HAX are powered by people just like you, wanting to make the web a better, more accessible, easier to use, less painful to develop for... place.Help us make that a reality and you too could have Snoop Dawg escorting you over to a brand new car*
-Anything is possible with HAXTheWeb. The only limit...is yourself -.
-*Claims vs reality may vary. Just help us out and we'll see where it goes.. -
- ]]> -This playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists related to all things ELMS:LN, WCFactory, HAXcms and web components in general.
- ]]> -HAXcms seeks to apply the SDS pattern, a technique we made up just for this sentence, for dramatic effect -. As everyone knows who is about to read the next heading, SDS stands for:
-So. Damn. Semantic.
-
Whew, I need an ice cold drink to wash away the semantic sweats.
-Yes, that's right, HAXcms allows you to theme a complex state managed system without needing to understand state management... like... at all.
-"But I understand state management and it's important to me"
-That's awesome, four people on twitter, but most designers just want to design! They don't need or want to understand the intricacies of making a collapsed field area expand relative to what item has been dictated as active in the store*.
-*an intentionally confusing worded sentence - - -
-We use MobX to do our state management if that's something you care about and some of our themes directly implement and interface with the state management layer. See Simple Blog's footer element - - - for a great example of why state management is a PITA. - -
-Back to the elements jerk
-Ok fine, here they are. Here's the list of ES module imports to get them
-Now here's what each of them provide you (pretty self explanatory because #SDS)
-- site-active-title -
-the title of the active item wrapped in a h1 tag
-
- site-children-block - - all child menu items based on a criteria match -
- site-outline-block - - part of the outline based on criteria match -
- site-footer - - a basic footer with license element based on site details -
- site-modal - - a basic modal with button that can house other elements -
- site-breadcrumb - - - a breadcrumb trail for the active menu item -
- site-dot-indicator - - site links but as a simple line of dots -
- site-menu-button
- - buttons for navigating through the active items in the menu. This is next, previous, parent and first child kinds of options.
- site-menu - - - A visualization of the hierarchy of your site, complete with checkmarks given per page the user goes to (optional) as well as a lot of styling options and a highlighted bar that scrolls the menu into view for small screens. It's fantastic and one line. -
- site-top-menu - - Top level menu links with indicator that scrolls to focus -
- site-print-button
- - print button with support for 4 levels of printing the site
- site-rss-button
- - a button that displays a link (opened in a new window) to get the RSS feed in RSS 2.0 or Atom 1.0 format (also applies correct semantic values for bots to discover)
- site-title
- - a link to the homepage of the site wrapped in an h1 tag
See the elements themselves for more details API examples and check out our themes as we leverage them heavily across the core themes.
-A word about style
-We use CSS variables to style all the bits inside of our custom elements. So if you don't like the styling, look at the CSS variables we make available and style away. The "Learn 2 theme" - - - is a great example implementing multiple levels of styling against multiple HAXcms site elements. You can always you know, go back and reread the CSS variables section -.
-Setting up publishing
-From the HAXcms site listing - page, click the settings gear in the top right corner.
-
Next you'll see a modal that has options for plugging in your github credentials. We don't save your password and this aspect is optional. If you do enter your password, a one time API call is made on your behalf from your container which will setup an ssh key pair. This allows for all future requests to publish to happen automatically on your behalf. Your password is not stored. If you don't want to set this part up, you can plug in the rest of the git settings, save, and then manually publish files after using the UI (see last heading on this page).
Publishing from your sites / new sites
-When you want to share your site with people or update your website, hitting the Publish button inside of your site is how to do this. Click the settings gear in the bottom right to get started.
Currently GitHub is the only provider supported in the local installation method (or from DDEV / one of the supported container providers). In the future hitting publish will have additional development flexibility.
-
Understanding what's actually happening
-When you hit publish, a few things happen to make your site "web ready". This is the general order of those operations:
-- HAXcms takes the underlying files and commits them all to version control (though they already should be) - - -
- It then pushes these to the origin of the git repository (likely github) - -
- Then it switches to the branch you do your publishing from. In github, this is the gh-pages - - branch, but can deviate as needed. - -
- Next it deletes symlinks and replaces them with the correct references as needed and leverages the "cdn provider" you specified when setting up HAXcms in order to super charge your files for end users. - -
- It uses twig - - to step through and correctly rewrite references in the index.html of your site to match the paths of where it's going to be sent - -
- Then it adds all this to version control and sends it up to your gh-pages branch. - -
- It does some local file clean up and sets things back to master branch for the next time you go to work on everything - -
When this is all done, in the UI you'll see a link to your site after it's indicated a successful publish (meaning it pushed the files up there). Depending on where you host your content it may take a few minutes to see the change, though GitHub is usually up within about 2 minutes.
-Once about 2 minutes or so has passed, refresh your live site address or type in the URL of the site. If you've been there previously, you'll probably see the same content / theme as the last time you were there. After about 5 seconds, a message will pop up indicating "new content available" and clicking it (or refreshing the browser) will give you your updated content.
-This last step happens because of what's called a "service worker". This enables your site to be 100% offline capable and ensures that your site only uses traffic and data when it's absolutely necessary.
-A note on non UI publishing workflows
-You might not have (or want to) setup the credentials between HAXcms and github / your git repo. That's ok. After you hit publish go to terminal / a Git GUI and run the following to publish your site:
-HAXcms will have made sure that the gh-pages and master branches are valid for distribution, even if it wasn't able to actually send these files to their publishing destination.
-Difference from past static generators
-Unlike solutions like Jekyll - -, HAXcms is for anyone to publish a website, not just those that understand command line. HAXcms is intended to be installed and then allow users to entirely use a UI to create, publish and manage micro-sites.
-Visualization
-
]]>
- The key directories / files include:
-- files - any files you've uploaded through the HAX interface - -
- pages - folders named by their content uri that have index.html in it, no structure other then what you created when hitting save -
- site.json - JSON Outline Schema object that defines the pages in your site and their relationship to each other
- index.html - front page of the PWA that stitch it all together -
- service-worker.js - makes it a PWA, no need to edi this -
Screen grab of a microsite
-
]]>
- Have PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is to create two basic folders). If all goes well you'll see some ASCii art telling you what your password is. HAXcms seeks to be a 0 config installation so if anything didn't work or make sense, just drop us a line in the issue queues.
-Or from Command Line...
-Just run this one command and you'll be HAXing the web in no time! This will step you through prompts (which can be scripted via arguments) to feed the backend what it needs to create the few configuration files it uses to load.
-A note on bash - - -
- -If you're having issues installing via the bash script, ensure you are on bash version 4.x. Some OS flavors start at 3.x which won't work. - - -
- -MAMP
-MAMP - - - - - - - allows Mac and PC users to rapidly install a working webdev stack on their machine. Here's the steps you need to take if using this (or on similar site hosting).
-Download the latest copy of HAXcms from github - - - - and place this in MAMP/htdocs - -either at the root level (as in copying the files you download into htdocs as shown in the image below) or by placing the folder in the directory (in the case where you have MAMP already installed / want to keep things tidy).
-Open MAMP and hit the Start Servers Button - - - -
-Click MY WEBSITE in MAMP start page to get started - - - -
-
Now you can build website organically off of MAMP!
-DDEV / Docksal / Lando / Vagrant
-We recommend using HAXcms in a docker container manager like ddev - - - - - - -, though based on above you can see basically we're just downloading and running one command to get going. We support all of the above methods so pick the one you work with most often.
--
-
- Clone this repo:
git clone https://github.com/elmsln/haxcms.git- - - - - - - -
-
-
-
-
-
-
-
-
- - install docker - - - - - - - - - - - - - - - - -
- install ddev - - - - - - - - or install docksal - - - - - - - - or install lando - - - - - - - - or install vagrant - - - - - - - - (We support 'em all!) - - - - - - - - -
- open a terminal window, go to the directory and type
ddev start- - - - - - - - (for ddev) orfin init- - - - - - - - (for docksal) orlando start && lando magic- - - - - - - - (for lando) orvagrant up- - - - - - - - (for vagrant)
-
-
-
-
-
-
-
-
- - go to the link any of them give you in a browser - - - - - - - - -
- username/password is
admin- - - - - - - -/admin- - - - - - - - to get building out static sites locally that you can push up anywhere!
-
-
-
-
-
-
-
-
- - Click the icon in the top right and you're off and running! - - - - - - - - -
Apache gotchas
-If installing on an existing server it might already have apache configurations that would cause HAXcms to have issues out of the gate - (or any CMS for that matter). Make sure local overrides are allowed with something like the following:
-Some words and phrases worth understanding in HAXcms
-- HAXeditor - the HAX editor -
- microsite - An individual site that's been created by a user -
- Outline - All sites are an outline, we use JSON Outline Schema to manage this -
- Theme - A single web component based theme that's agnostic of content -
- Elements / web components - design assets that work anywhere -
Click load file to load some HTML from your file system
+
+
+
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/atom.xml b/github-pages-deploy-action-temp-deployment-folder/atom.xml
new file mode 100644
index 0000000..ded1267
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/atom.xml
@@ -0,0 +1,12 @@
+
+Outdated browser detected
+ + ++ Upgrade your browser to the latest version or download one of these browsers: +
+ + +- \n
- Any journal is fine. I recommend the Moleskine Cahier Journal, Large, Squared, Kraft Brown, Soft Cover (5 x 8.25) Amazon purchase link\n\n\n \n\n\n\n
- \n
- Any that you already own are fine, you do not need to purchase special ones for this course. However, the following recommendations are professional grade if you are so inclined to invest in quality drawing tools.\n\n
- \n
- Pencil: Palomino Blackwing 602 \n\n\n\n
- Pen: Copic Multiliner Marker 0.5 - Black \n\n\n\n
- Marker: Copic N2 \n\n\n\n
\n\n\n\n
Name for this provided (github currently supported)<\/div>"
+ }
+ },
+ "branch": {
+ "title": "Branch",
+ "type": "string",
+ "value": "gh-pages",
+ "component": {
+ "name": "paper-input",
+ "valueProperty": "value",
+ "slot": "
Project code branch (like master or gh-pages)<\/div>"
+ }
+ },
+ "url": {
+ "title": "Repo url",
+ "type": "string",
+ "value": "git@github.com:elmsln",
+ "component": {
+ "name": "paper-input",
+ "valueProperty": "value",
+ "slot": "
Base address \/ organization that new sites will be saved under<\/div>"
+ }
+ },
+ "user": {
+ "title": "User \/ Org",
+ "type": "string",
+ "value": "btopro",
+ "component": {
+ "name": "paper-input",
+ "valueProperty": "value",
+ "slot": "
Set, to change this manually edit _config\/config.json.<\/div>",
+ "attributes": {
+ "disabled": "disabled"
+ }
+ }
+ },
+ "email": {
+ "title": "Email",
+ "type": "string",
+ "value": "bto108@psu.edu",
+ "component": {
+ "name": "paper-input",
+ "valueProperty": "value",
+ "slot": "
Set, to change this manually edit _config\/config.json.<\/div>",
+ "attributes": {
+ "disabled": "disabled"
+ }
+ }
+ },
+ "cdn": {
+ "title": "CDN",
+ "type": "string",
+ "value": "webcomponents.psu.edu",
+ "component": {
+ "name": "paper-input",
+ "valueProperty": "value",
+ "slot": "
A CDN address that supports HAXCMS<\/div>"
+ }
+ }
+ }
+ },
+ "apis": {
+ "title": "API Connectivity",
+ "type": "object",
+ "properties": {
+ "youtube": {
+ "title": "YouTube",
+ "type": "string",
+ "value": "AIzaSyAF9zKXv-fxus9GNqn40SHzTn6F8A7h-Yo",
+ "component": {
+ "slot": "
See YouTube developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "googlepoly": {
+ "title": "Google Poly",
+ "type": "string",
+ "value": "AIzaSyDiSvloa49gHUJG0YAt3Ys_I6IEoiscPUM",
+ "component": {
+ "slot": "
See Google Poly developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "memegenerator": {
+ "title": "Meme generator",
+ "type": "string",
+ "value": "e7fbcd7f-8d76-4513-9698-e20de4362d99",
+ "component": {
+ "slot": "
See Meme generator developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "vimeo": {
+ "title": "Vimeo",
+ "type": "string",
+ "value": "0a718b853bad87571d52e9fb554e0a43",
+ "component": {
+ "slot": "
See Vimeo developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "giphy": {
+ "title": "Giphy",
+ "type": "string",
+ "value": "mr3blNkTT0HeTvtyPPT4TIftqUSgyHoO",
+ "component": {
+ "slot": "
See Giphy developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "unsplash": {
+ "title": "Unsplash",
+ "type": "string",
+ "value": "0e1fa3a203724415c10c03581e8db8a43e8bc8906ad934e0f321d28be16281ff",
+ "component": {
+ "slot": "
See Unsplash developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "flickr": {
+ "title": "Flickr",
+ "type": "string",
+ "value": "43ccc969703b7afd4e2a1b16f02ce84e",
+ "component": {
+ "slot": "
See Flickr developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ },
+ "pixabay": {
+ "title": "Pixabay",
+ "type": "string",
+ "value": "7839766-f49bb4174cd49cb587944a5f7",
+ "component": {
+ "slot": "
See Pixabay developer docs.<\/a><\/div>",
+ "name": "paper-input",
+ "valueProperty": "value"
+ }
+ }
+ }
+ }
+ }
+ },
+ "values": {
+ "themes": {
+ "haxcms-dev-theme": {
+ "element": "haxcms-dev-theme",
+ "path": "@lrnwebcomponents\/haxcms-elements\/lib\/haxcms-dev-theme.js",
+ "name": "Developer theme"
+ },
+ "outline-player": {
+ "element": "outline-player",
+ "path": "@lrnwebcomponents\/outline-player\/outline-player.js",
+ "name": "Outline player"
+ },
+ "simple-blog": {
+ "element": "simple-blog",
+ "path": "@lrnwebcomponents\/simple-blog\/simple-blog.js",
+ "name": "Simple blog"
+ },
+ "haxcms-slide-theme": {
+ "element": "haxcms-slide-theme",
+ "path": "@lrnwebcomponents\/haxcms-elements\/lib\/haxcms-slide-theme.js",
+ "name": "Slide player"
+ }
+ },
+ "appStore": {
+ "apiKeys": {
+ "youtube": "",
+ "googlepoly": "",
+ "memegenerator": "",
+ "vimeo": "",
+ "giphy": "",
+ "unsplash": "",
+ "flickr": "",
+ "pixabay": ""
+ }
+ },
+ "publishing": {
+ "git": {
+ "vendor": "github",
+ "branch": "gh-pages",
+ "url": "git@github.com:elmsln",
+ "user": "",
+ "email": "",
+ "cdn": "webcomponents.psu.edu"
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/fake/dev/getNodeFieldsPath.json b/github-pages-deploy-action-temp-deployment-folder/fake/dev/getNodeFieldsPath.json
new file mode 100644
index 0000000..495506f
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/fake/dev/getNodeFieldsPath.json
@@ -0,0 +1,122 @@
+{
+ "status": 200,
+ "data": {
+ "fields": [{
+ "property": "node",
+ "inputMethod": "tabs",
+ "properties": [
+ {
+ "property": "configure",
+ "title": "Configure",
+ "description": "Change node settings",
+ "properties": [
+ {
+ "property": "node-configure-title",
+ "description": "Title of the page",
+ "inputMethod": "textfield",
+ "required": true,
+ "icon": "editor:title"
+ },
+ {
+ "property": "node-configure-location",
+ "description": "Location used in the URL",
+ "inputMethod": "textfield",
+ "required": true,
+ "disabled": true,
+ "icon": "device:gps-fixed"
+ },
+ {
+ "property": "node-configure-description",
+ "description": "Description for the post",
+ "inputMethod": "textfield",
+ "required": false,
+ "icon": "editor:short-text"
+ },
+ {
+ "property": "node-configure-images",
+ "description": "List of images",
+ "required": false,
+ "icon": "image:collections",
+ "title": "Other sources",
+ "inputMethod": "array",
+ "properties": [
+ {
+ "property": "src",
+ "title": "Source",
+ "description": "The URL for the image",
+ "inputMethod": "textfield"
+ },
+ {
+ "property": "alt",
+ "title": "Alt",
+ "description": "Alt text",
+ "inputMethod": "textfield"
+ }
+ ]
+ },
+ {
+ "property": "node-configure-subtitle",
+ "title": "Subtitle",
+ "description": "An additional subtitle",
+ "inputMethod": "textfield",
+ "icon": "editor:text-fields"
+ },
+ {
+ "property": "node-configure-accentColor",
+ "title": "Accent color",
+ "description": "Select the accent color for the player.",
+ "inputMethod": "colorpicker",
+ "icon": "editor:format-color-fill"
+ }
+ ]
+ },
+ {
+ "property": "advanced",
+ "title": "Advanced",
+ "description": "less common node settings",
+ "properties": [
+ {
+ "property": "node-advanced-created",
+ "description": "Created timestamp",
+ "inputMethod": "textfield",
+ "required": true,
+ "icon": "device:access-time"
+ },
+ {
+ "property": "node-advanced-theme",
+ "description": "Page theme",
+ "inputMethod": "select",
+ "required": false,
+ "icon": "editor:format-paint",
+ "options": {
+ "odl-haxtheme": "Eberly ODL",
+ "key": "haxcms-theme-developer",
+ "learn-two-theme": "Learn",
+ "outline-player": "Documentation",
+ "simple-blog": "Simple blog",
+ "haxcms-basic-theme": "Basic site",
+ "haxcms-minimalist-theme": "Minimalist site",
+ "haxcms-slide-theme": "Slide deck",
+ "haxcms-dev-theme": "DEVELOPER: Test theme",
+ "haxcms-theme-developer": "EXPERIMENTAL: HAX Theme Maker"
+ }
+ }
+ ]
+ }
+ ]}
+ ],
+ "value": {
+ "node": {
+ "configure": {
+ "node-configure-title": "Functions",
+ "node-configure-location": "functions",
+ "node-configure-description": ""
+ },
+ "advanced": {
+ "node-advanced-created": 1552651607,
+ "node-advanced-theme": "haxor-slevin"
+ }
+ }
+ }
+ }
+}
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/fake/dev/getSiteFieldsPath.json b/github-pages-deploy-action-temp-deployment-folder/fake/dev/getSiteFieldsPath.json
new file mode 100644
index 0000000..3918dff
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/fake/dev/getSiteFieldsPath.json
@@ -0,0 +1,377 @@
+{
+ "status": 200,
+ "data": {
+ "fields": [{
+ "property": "manifest",
+ "inputMethod": "tabs",
+ "properties": [
+ {
+ "property": "site",
+ "title": "Site",
+ "description": "Settings directly related to the internals of the site",
+ "properties": [
+ {
+ "property": "manifest.title",
+ "title": "title",
+ "description": "Name of the site",
+ "inputMethod": "textfield",
+ "required": true,
+ "icon": "editor:title"
+ },
+ {
+ "property": "manifest.metadata.site.domain",
+ "title": "Domain",
+ "description": "Domain of this website",
+ "inputMethod": "textfield",
+ "required": false,
+ "icon": "icons:open-in-browser"
+ },
+ {
+ "property": "manifest.description",
+ "title": "Description",
+ "description": "Simple description of the site",
+ "inputMethod": "textfield",
+ "required": false,
+ "icon": "editor:short-text"
+ }
+ ]
+ },
+ {
+ "property": "author",
+ "title": "Author",
+ "description": "Author details",
+ "properties": [
+ {
+ "property": "manifest.license",
+ "title": "License",
+ "description": "The source url for the element this is citing.",
+ "inputMethod": "select",
+ "options": {
+ "by": "Attribution",
+ "by-nc": "Attribution non-commercial",
+ "by-nc-nd": "Attribution Non-commercial No derivatives",
+ "by-nc-sa": "Attribution non-commercial share a like",
+ "by-nd": "Attribution No derivatives",
+ "by-sa": "Attribution Share a like"
+ },
+ "icon": "link"
+ },
+ {
+ "property": "manifest.metadata.author.image",
+ "title": "Image",
+ "description": "Photo",
+ "inputMethod": "haxupload"
+ },
+ {
+ "property": "manifest.metadata.author.name",
+ "title": "Name",
+ "description": "Name",
+ "inputMethod": "textfield"
+ },
+ {
+ "property": "manifest.metadata.author.socialLink",
+ "title": "Social media link",
+ "description": "A primary social space \/ point of contact",
+ "inputMethod": "textfield"
+ }
+ ]
+ },
+ {
+ "property": "theme",
+ "title": "Theme",
+ "description": "Theme and design settings for the site",
+ "properties": [
+ {
+ "property": "manifest.metadata.theme.name",
+ "title": "Theme",
+ "description": "Page theme",
+ "inputMethod": "select",
+ "required": false,
+ "icon": "editor:format-paint",
+ "options": {
+ "learn-two-theme": "Learn",
+ "haxor-slevin": "Coder blog",
+ "outline-player": "Documentation",
+ "simple-blog": "Simple blog",
+ "haxcms-basic-theme": "Basic site",
+ "haxcms-user-theme": "User theme",
+ "haxcms-minimalist-theme": "Minimalist site",
+ "haxcms-slide-theme": "Slide deck",
+ "haxcms-dev-theme": "DEVELOPER: Test theme",
+ "haxcms-theme-developer": "EXPERIMENTAL: HAX Theme Maker"
+ }
+ },
+ {
+ "property": "manifest.metadata.theme.variables.image",
+ "title": "Banner",
+ "description": "Image for the site",
+ "inputMethod": "haxupload",
+ "required": false,
+ "icon": "image:image"
+ },
+ {
+ "property": "manifest.metadata.theme.variables.cssVariable",
+ "title": "Color",
+ "description": "A base accent color for the site",
+ "inputMethod": "colorpicker",
+ "required": true,
+ "icon": "editor:format-color-fill"
+ },
+ {
+ "property": "manifest.metadata.theme.variables.icon",
+ "title": "Icon",
+ "description": "Icon to represent the site",
+ "inputMethod": "iconpicker",
+ "required": false,
+ "icon": "icons:send"
+ }
+ ]
+ },
+ {
+ "property": "fields",
+ "title": "Fields",
+ "description": "Custom fields for nodes in the site",
+ "properties": [
+ {
+ "property": "manifest.metadata.node.fields",
+ "title": "Custom Fields",
+ "description": "Store relational data about nodes and other properties",
+ "required": false,
+ "icon": "icons:group-work",
+ "inputMethod": "array",
+ "properties": [
+ {
+ "property": "formgroup",
+ "title": "Form group",
+ "description": "Which tab will users input values",
+ "inputMethod": "select",
+ "required": true,
+ "options": {
+ "configure": "Configure",
+ "advanced": "Advanced"
+ },
+ "icon": "link"
+ },
+ {
+ "property": "inputMethod",
+ "title": "Input method",
+ "description": "How users can enter data for this field",
+ "inputMethod": "select",
+ "options": {
+ "textfield": "Textfield",
+ "number": "Number",
+ "boolean": "Checkbox",
+ "haxupload": "File upload",
+ "colorpicker": "Color picker",
+ "iconpicker": "Icon picker",
+ "code-editor": "Code editor",
+ "alt": "Alt text",
+ "datepicker": "Date picker",
+ "textarea": "Text area",
+ "flipboolean": "Checkbox (inverted)",
+ "select": "Select list",
+ "array": "Array"
+ },
+ "icon": "link"
+ },
+ {
+ "property": "property",
+ "title": "Machine name",
+ "description": "Field machine name for storage",
+ "inputMethod": "textfield",
+ "required": true
+ },
+ {
+ "property": "title",
+ "title": "Name",
+ "description": "Readable name of the field",
+ "inputMethod": "textfield",
+ "required": true
+ },
+ {
+ "property": "description",
+ "title": "Description",
+ "description": "additional details about the field data",
+ "inputMethod": "textfield",
+ "required": false
+ },
+ {
+ "property": "required",
+ "title": "Required",
+ "description": "Is this field required",
+ "inputMethod": "boolean",
+ "required": false
+ },
+ {
+ "property": "icon",
+ "title": "Icon",
+ "description": "Optional icon to represent this field",
+ "inputMethod": "iconpicker",
+ "required": false
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "property": "seo",
+ "title": "SEO",
+ "description": "Search engine and detailed internal path handling",
+ "properties": [
+ {
+ "property": "manifest.metadata.site.settings.pathauto",
+ "title": "Pathauto",
+ "description": "Automatically maintain and update page paths",
+ "inputMethod": "boolean",
+ "icon": "icons:link"
+ },
+ {
+ "property": "manifest.metadata.site.settings.publishPagesOn",
+ "title": "Show unpublished pages",
+ "description": "Whether to hide unpublished pages or not",
+ "inputMethod": "boolean",
+ "icon": "icons:link"
+ }
+ ]
+ },
+ {
+ "property": "static",
+ "title": "Publishing",
+ "description": "Publishing options",
+ "properties": [
+ {
+ "property": "manifest.metadata.site.static.cdn",
+ "title": "CDN",
+ "description": "CDN to use for published assets",
+ "inputMethod": "select",
+ "required": true,
+ "options": {
+ "https:\/\/webcomponents.psu.edu\/cdn\/": "Penn State CDN",
+ "https:\/\/cdn.waxam.io\/": "Waxam CDN",
+ "build\/": "Local (no CDN)"
+ },
+ "icon": "link"
+ },
+ {
+ "property": "manifest.metadata.site.static.offline",
+ "title": "Offline",
+ "description": "Published site will work when completely offline",
+ "inputMethod": "boolean",
+ "required": false
+ }
+ ]
+ },
+ {
+ "property": "git",
+ "title": "Version control",
+ "description": "Store relational data about fields",
+ "properties": [
+ {
+ "property": "manifest.metadata.site.git.branch",
+ "title": "Default branch",
+ "description": "Branch to publish on (master is common)",
+ "inputMethod": "textfield",
+ "required": true
+ },
+ {
+ "property": "manifest.metadata.site.git.staticBranch",
+ "title": "Static branch",
+ "description": "Branch to publish on (gh-pages is common)",
+ "inputMethod": "textfield",
+ "required": true
+ },
+ {
+ "property": "manifest.metadata.site.git.url",
+ "title": "Git url",
+ "description": "location of the git repository to sync up to",
+ "inputMethod": "textfield",
+ "required": true
+ },
+ {
+ "property": "manifest.metadata.site.git.vendor",
+ "title": "Vendor",
+ "description": "Vendor used for internal publishing flexibility",
+ "inputMethod": "select",
+ "options": {
+ "github": "Github"
+ },
+ "required": true
+ },
+ {
+ "property": "dangerzone",
+ "title": "Dangerzone",
+ "description": "",
+ "inputMethod": "markup"
+ }
+ ]
+ }
+ ]
+ }],
+ "value": {
+ "manifest": {
+ "site": {
+ "manifest.title": "btopro",
+ "manifest.description": "Crazy, abrasive, caring, dreaming the future into existence.",
+ "manifest.metadata.site.domain": "https:\/\/btopro.com"
+ },
+ "author": {
+ "manifest.license": "by-sa",
+ "manifest.metadata.author.image": "files\/headshot.jpg",
+ "manifest.metadata.author.name": "Bryan Ollendyke",
+ "manifest.metadata.author.socialLink": "https:\/\/twitter.com\/btopro"
+ },
+ "theme": {
+ "manifest.metadata.theme.name": "Coder blog",
+ "manifest.metadata.theme.variables.image": "assets\/banner.jpg",
+ "manifest.metadata.theme.variables.hexCode": "#da004e",
+ "manifest.metadata.theme.variables.cssVariable": "pink",
+ "manifest.metadata.theme.variables.icon": "icons:record-voice-over"
+ },
+ "fields": {
+ "manifest.metadata.node.fields.configure": [
+ {
+ "inputMethod": "array",
+ "property": "images",
+ "title": "Other sources",
+ "description": "List of images",
+ "required": false,
+ "icon": "image:collections"
+ },
+ {
+ "inputMethod": "textfield",
+ "property": "subtitle",
+ "title": "Subtitle",
+ "description": "An additional subtitle",
+ "required": false,
+ "icon": "editor:text-fields"
+ },
+ {
+ "inputMethod": "array",
+ "property": "tags",
+ "title": "Tags",
+ "description": "Tags for the page",
+ "required": false,
+ "icon": "image:collections"
+ }
+ ],
+ "manifest.metadata.node.fields.advanced": null
+ },
+ "seo": {
+ "manifest.metadata.site.settings.pathauto": true,
+ "manifest.metadata.site.settings.publishPagesOn": true
+ },
+ "static": {
+ "manifest.metadata.site.static.cdn": "cdn.waxam.io",
+ "manifest.metadata.site.static.offline": true
+ },
+ "git": {
+ "manifest.metadata.site.git.vendor": "github",
+ "manifest.metadata.site.git.branch": "master",
+ "manifest.metadata.site.git.staticBranch": "gh-pages",
+ "manifest.metadata.site.git.url": "git@github.com:btopro\/blog.git",
+ "dangerzone": "HAXcms
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ {
+// info about the source of this integration
+"details": {
+ // title to display in the UI
+ "title": "Flickr",
+ // icon to represent it in UIs
+ "icon": "image:collections",
+ // an optional image to present it
+ "image": "flickr.jpg",
+ // color to accent it in UIs
+ "color": "pink",
+ // author of the app (future)
+ "author": "Yahoo",
+ // description (future)
+ "description": "The original photo sharing platform on the web.",
+ // status (future)
+ "status": "available",
+ // rating (future)
+ "rating": "0",
+ // tags for grouping sources (future)
+ "tags": ["images", "creative commons", "crowdsourced"]
+},
+// the connection object declares how to connect to this service
+"connection": {
+ "protocol": "https",
+ "url": "api.flickr.com",
+ // any additional headers that need added
+ "headers": {
+ "Authorization": "Bearer POTENTIALLYSOMEBIGSIGNATUREHERE"
+ },
+ // any data to send with the API call, usually for authorization or querying
+ "data": {
+ "api_key": "SOMEBIGKEYHERE"
+ },
+ // supported operations include, browse, read, edit, add, delete
+ "operations": {
+ "browse": {
+ "method": "GET",
+ "endPoint": "services/rest",
+ // pagination methodology (future)
+ "pagination": {
+ "style": "page",
+ "props": {
+ "per_page": "photos.perpage",
+ "total_pages": "photos.pages",
+ "page": "photos.page"
+ }
+ },
+ // data needed in order to search this
+ "search": {
+ // JSON schema of key to search with, label to supply and input field type
+ "text": {
+ "title": "Search",
+ "type": "textfield"
+ },
+ "license": {
+ "title": "License type",
+ "type": "select",
+ "options": {
+ "1": "Public domain",
+ "2": "CC attribution",
+ "3": "CC Zero",
+ "4": "CC Share-alike"
+ }
+ }
+ },
+ // data to send on requests
+ "data": {
+ "method": "flickr.photos.search",
+ "text": "",
+ "safe_search": "1",
+ "per_page": "20",
+ "page": "1",
+ "format": "json",
+ "nojsoncallback": "1",
+ "extras": "license,description,url_l,url_s"
+ },
+ // a map of the information coming across the wire
+ "resultMap": {
+ // what type of gizmo to match results to
+ "defaultGizmoType": "video",
+ // the location where the items are found in the response
+ "items": "resource.items.collection",
+ // what data to map to in a preview
+ "preview": {
+ "title": "Stuff",
+ "details": "Details",
+ "image": "whatever.jpg",
+ "id": "meta.id"
+ },
+ // the fields and what they map to off the API
+ "gizmo": {
+ "type": "",
+ "title": "",
+ "description": "",
+ "source": "",
+ "citation": "",
+ "alt": "",
+ "caption": "",
+ "color": ""
+ }
+ }
+ },
+ // reading individual nodes off the API
+ "read": {
+ "method": "GET",
+ "endPoint": "node/<%= id %>",
+ "data": {
+ "deep-load-refs": "node"
+ }
+ },
+ // editing inputs (future)
+ "edit": {
+ "method": "PUT",
+ "endPoint": "node/<%= id %>/update"
+ },
+ // adding / uploading connection details
+ "add": {
+ "method": "POST",
+ "endPoint": "node",
+ "data": {
+ "title": "A new item",
+ "img": "This is the image"
+ }
+ },
+ // delete request details
+ "delete": {
+ "method": "DELETE",
+ "endPoint": "node/<%= id %>/delete"
+ }
+ }
+}
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/autoloader/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/autoloader/index.html
new file mode 100644
index 0000000..6d9deff
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/autoloader/index.html
@@ -0,0 +1,87 @@
+
+ "autoloader": {
+ "meme-maker": "@lrnwebcomponents/meme-maker/meme-maker.js",
+ "another-tag": {
+ "import": "some-other-location/bare-import-name/whatever.js"
+ },
+ "vaadin-upload": {
+ "import": "@vaadin/vaadin-upload/vaadin-upload.js",
+ "haxProperties": {
+ "canScale": false,
+ "canPosition": false,
+ "canEditSource": true,
+ "gizmo": {
+ "title": "Vaadin upload button",
+ "icon": "upload",
+ "color": "orange",
+ "groups": ["upload", "community"],
+ "meta": {
+ "author": "Vaadin Elements"
+ }
+ },
+ "settings": {
+ "configure": [
+ {
+ "property": "label",
+ "title": "Label",
+ "description": "Label for the upload button",
+ "inputMethod": "textfield"
+ }
+ ]
+ },
+ "saveOptions": {
+ "wipeSlot": true
+ }
+ }
+ }
+}
+
+
{
+"blox": [ {
+ // details for displaying this visually in the UI
+ "details": {
+ "title": "33 / 66 columns",
+ "author": "ELMS:LN",
+ "icon": "hax:4/8",
+ "status": "available",
+ "layout": "4/8"
+ },
+ // the definition of this layout piece which is a series of hax element schema definitions as an array
+ "blox": [
+ {
+ "tag": "place-holder",
+ "properties": {
+ "slot": "col-2",
+ "type": "text"
+ },
+ "content": ""
+ },
+ {
+ "tag": "place-holder",
+ "properties": {
+ "slot": "col-1",
+ "type": "image"
+ },
+ "content": ""
+ },
+ {
+ "tag": "place-holder",
+ "properties": {
+ "slot": "col-1",
+ "type": "image"
+ },
+ "content": ""
+ },
+ {
+ "tag": "place-holder",
+ "properties": {
+ "slot": "col-1",
+ "type": "image"
+ },
+ "content": ""
+ }
+}]
+},
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/index.html
new file mode 100644
index 0000000..061fdc5
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/index.html
@@ -0,0 +1,37 @@
+ "stax": [
+{
+"details": {
+"title": "Example Lesson",
+"image": "",
+"author": "ELMS:LN",
+"description": "An example of what HAX can do",
+"status": "available",
+"rating": "0",
+"tags": [
+"example"
+]
+},
+"stax": [
+{
+"tag": "h2",
+"properties": {},
+"content": "Introduction to ELMS: Learning Network"
+},
+{
+"tag": "p",
+"properties": {},
+"content": "What is ELMS: Learning Network? How is it fundamentally different from other learning technologies? Why is it your reading this when it's example text that you've just added to see how to make a really solid introduction to a new unit of instruction? Let's keep reading to find out!"
+},
+{
+"tag": "video-player",
+"properties": {
+"style": "width: 75%; margin: 0px auto; display: block;",
+"source": "https://www.youtube.com/watch?v=pKLPQ4ufo64",
+"src": "https://www.youtube-nocookie.com/embed/pKLPQ4ufo64?showinfo=0&controls=1&rel=0",
+"iframed": true,
+"sandboxed": false,
+"width": "560",
+"height": "315",
+"responsive": true,
+"caption": "What is ELMS:LN? Why is it fundamentally different from any other educational technology that's ever existed? What is sustainable innovation? Why is this so ...",
+"secondaryColor": "#fff9c4",
+"textColor": "#000000",
+"secondaryColorClass": "yellow lighten-4",
+"textColorClass": "black-text",
+"ytNocookie": true,
+"ytSuggested": false,
+"ytControls": true,
+"ytTitle": false,
+"vimeoTitle": false,
+"vimeoByline": false,
+"vimeoPortrait": false,
+"videoColor": "FF031D",
+"resource": "#86bfd28d-8b57-a3b9-b2e5",
+"prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+},
+"content": ""
+},
+{
+"tag": "h3",
+"properties": {},
+"content": "Pretest"
+},
+{
+"tag": "self-check",
+"properties": {
+"style": "width: 50%; float: right;",
+"title": "Self-Check",
+"image": "https://farm1.staticflickr.com/642/21641107852_3602f9c1a8_b.jpg",
+"alt": "A few stickers associated with ELMS:LN are shown presented on the back of a laptop.",
+"correct": false,
+"textColor": "#000000",
+"textColorClass": "black-text",
+"backgroundColor": "#b2dfdb",
+"backgroundColorClass": "teal lighten-4",
+"resource": "#08d09967-a7c9-3d02-8935",
+"prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+},
+"content": " True or False. ELMS:LN is a traditional learning management system.\n\n FALSE. ELMS: Learning Network is considered to be a Next Generation Digital Learning Environment.\nLearn more about NGDLE in this blog post on Educause\n.\n\n"
+},
+{
+"tag": "p",
+"properties": {},
+"content": "If you think you already know about ELMS:LN, let's find out ahead of time! Take the self-check on the right to find out if ELMS:LN is a traditional Learning Management system or something more"
+},
+{
+"tag": "hr",
+"properties": {
+"style": "width: 75%;"
+},
+"content": ""
+},
+{
+"tag": "h3",
+"properties": {},
+"content": "History Review"
+},
+{
+"tag": "p",
+"properties": {},
+"content": "Now that we've read about what ELMS:LN is (and is not). Let's take a different kind of self-check to illustrate the flexibility of the HAX authoring platform."
+},
+{
+"tag": "multiple-choice",
+"properties": {
+"style": "width: 75%; margin: 0px auto; display: block;",
+"checkLabel": "Check guess",
+"resetLabel": "Clear",
+"hideTitle": true,
+"question": "Who founded the ELMS:LN Platform?",
+"answers": [
+{
+"correct": true,
+"label": "Bryan Ollendyke"
+},
+{
+"correct": false,
+"label": "Mythic Elves"
+},
+{
+"correct": false,
+"label": "Michael Potter"
+},
+{
+"correct": false,
+"label": "Nikki Massaro Kauffman"
+},
+{
+"correct": false,
+"label": "Charles Lavera"
+}
+],
+"correctText": "Great job!",
+"incorrectText": "Try again",
+"randomize": true,
+"typeof": "oer:Assessment",
+"resource": "#97ffed48-c928-39ae-1bea",
+"prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+},
+"content": ""
+},
+{
+"tag": "multiple-choice",
+"properties": {
+"style": "width: 75%; margin: 0px auto; display: block;",
+"title": "ELMS Development team",
+"checkLabel": "Check your guess",
+"resetLabel": "Clear answers",
+"hideTitle": false,
+"question": "Who is responsible for ELMS:LN existing? Who improves it and wants it to be the best NGDLE solution to transform education and the world?",
+"answers": [
+{
+"correct": true,
+"label": "Nikki Massaro Kauffman"
+},
+{
+"correct": true,
+"label": "Michael Potter"
+},
+{
+"correct": true,
+"label": "Charles Lavera"
+},
+{
+"correct": true,
+"label": "Bryan Ollendyke"
+},
+{
+"correct": true,
+"label": "Anyone, ELMS:LN is an open community developed by multiple organizations!"
+}
+],
+"displayedAnswers": [
+{
+"correct": true,
+"label": "Nikki Massaro Kauffman"
+},
+{
+"correct": true,
+"label": "Michael Potter"
+},
+{
+"correct": true,
+"label": "Charles Lavera"
+},
+{
+"correct": true,
+"label": "Bryan Ollendyke"
+},
+{
+"correct": true,
+"label": "Anyone, ELMS:LN is an open community developed by multiple organizations!"
+}
+],
+"correctText": "Great job! You got our trick question!",
+"incorrectText": "Try again, there's some more answers...",
+"randomize": true,
+"typeof": "oer:Assessment",
+"resource": "#59426af4-ecf2-f49d-06a6",
+"prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+},
+"content": ""
+}
+]
+}
+]
+}
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-element-schema/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-element-schema/index.html
new file mode 100644
index 0000000..9bafee0
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-element-schema/index.html
@@ -0,0 +1,46 @@
+ {
+"tag": "h2",
+"properties": {},
+"content": "Introduction to ELMS: Learning Network"
+}
+
+ {
+"tag": "p",
+"properties": {},
+"content": "What is ELMS: Learning Network? How is it fundamentally different from other learning technologies? Why is it your reading this when it's example text that you've just added to see how to make a really solid introduction to a new unit of instruction? Let's keep reading to find out!"
+}
+
+ {
+"tag": "video-player",
+"properties": {
+"style": "width: 75%; margin: 0px auto; display: block;",
+"source": "https://www.youtube.com/watch?v=pKLPQ4ufo64",
+"src": "https://www.youtube-nocookie.com/embed/pKLPQ4ufo64?showinfo=0&controls=1&rel=0",
+"iframed": true,
+"sandboxed": false,
+"width": "560",
+"height": "315",
+"responsive": true,
+"caption": "What is ELMS:LN? Why is it fundamentally different from any other educational technology that's ever existed? What is sustainable innovation? Why is this so ...",
+"secondaryColor": "#fff9c4",
+"textColor": "#000000",
+"secondaryColorClass": "yellow lighten-4",
+"textColorClass": "black-text",
+"ytNocookie": true,
+"ytSuggested": false,
+"ytControls": true,
+"ytTitle": false,
+"vimeoTitle": false,
+"vimeoByline": false,
+"vimeoPortrait": false,
+"videoColor": "FF031D",
+"resource": "#86bfd28d-8b57-a3b9-b2e5",
+"prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+},
+"content": ""
+}
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-schema/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-schema/index.html
new file mode 100644
index 0000000..d3990bf
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-schema/index.html
@@ -0,0 +1,270 @@
+
+// can this item be scaled in the UI, will it have a slider for % width
+canScale: true,
+// can you position the item left or center justified
+canPosition: true,
+// can you edit the raw source of this element (future)
+canEditSource: false
+
+
+gizmo: {
+// title to display
+title: "Example hax-element",
+// description
+description:
+ "Provide an example to pick apart of a working HAX element",
+// icon to represent this in selection displays
+icon: "icons:android",
+// color to tint this when in displays
+color: "green",
+// grouping data for filtering in displays (future)
+groups: ["Hax"],
+// handlers allow HAX to stitch together sources of information with gizmos to render that information
+// example: Youtube supplies a source value that points to a url of the video
+// if the user picks a video from youtube, things that match
+// 'video' as a type and then match on any 1 additional field
+// will be presented to the user as the way to render the video
+// in the case of YouTube this presents a video-player or QR code
+// in default implementations with these tags.
+// This is because the match is on source, which the key of source
+// in the handles block => points to the property to insert into
+// it is an array of objects so you can map to multiple types
+// type is a reserved key and can be anything so long as
+// a source of data is looking for something matching that "type"
+handles: [
+{
+ // what it can present
+ type: "video",
+ // the property coming from the app on the left => property in the element on the right
+ source: "source",
+ // this pulls the title off the API and sticks it in the caption field of the element
+ title: "caption",
+ // fallback matches
+ caption: "caption",
+ description: "caption",
+ // ability to pull color across though this would be rare from an API
+ color: "primaryColor"
+}
+],
+// any metadata you wish to ship along
+meta: {
+ author: "You",
+ owner: "Your Company"
+}
+},
+ 
+ 
+
+
+settings: {
+quick: [
+ {
+ property: "accentColor",
+ title: "Accent color",
+ description: "Select the accent color for the player.",
+ inputMethod: "colorpicker",
+ icon: "editor:format-color-fill"
+ },
+ {
+ attribute: "dark",
+ title: "Dark theme",
+ description: "Enable dark theme for the player.",
+ inputMethod: "boolean",
+ icon: "invert-colors"
+ }
+],
+
+configure: [
+{
+ property: "source",
+ title: "Source",
+ description: "The URL for this video.",
+ inputMethod: "textfield",
+ icon: "link",
+ required: true,
+ validationType: "url"
+},
+{
+ property: "track",
+ title: "Closed captions",
+ description: "The URL for the captions file.",
+ inputMethod: "textfield",
+ icon: "link",
+ required: true,
+ validationType: "url"
+},
+{
+ property: "thumbnailSrc",
+ title: "Thumbnail image",
+ description: "Optional. The URL for a thumbnail/poster image.",
+ inputMethod: "textfield",
+ icon: "link",
+ required: true,
+ validationType: "url"
+},
+{
+ property: "mediaTitle",
+ title: "Title",
+ description: "Simple title for under video",
+ inputMethod: "textfield",
+ icon: "av:video-label",
+ required: false,
+ validationType: "text"
+},
+{
+ property: "accentColor",
+ title: "Accent color",
+ description: "Select the accent color for the player.",
+ inputMethod: "colorpicker",
+ icon: "editor:format-color-fill"
+},
+{
+ attribute: "dark",
+ title: "Dark theme",
+ description: "Enable dark theme for the player.",
+ inputMethod: "boolean",
+ icon: "invert-colors"
+}
+],
+
+advanced: [
+{
+ property: "darkTranscript",
+ title: "Dark theme for transcript",
+ description: "Enable dark theme for the transcript.",
+ inputMethod: "boolean"
+},
+{
+ property: "hideTimestamps",
+ title: "Hide timestamps",
+ description: "Hide the time stamps on the transcript.",
+ inputMethod: "boolean"
+},
+{
+ property: "preload",
+ title: "Preload source(s).",
+ description:
+ "How the sources should be preloaded, i.e. auto, metadata (default), or none.",
+ inputMethod: "select",
+ options: {
+ preload: "Preload all media",
+ metadata: "Preload media metadata only",
+ none: "Don't preload anything"
+ }
+},
+{
+ property: "stickyCorner",
+ title: "Sticky Corner",
+ description:
+ "Set the corner where a video plays when scrolled out of range, or choose none to disable sticky video.",
+ inputMethod: "select",
+ options: {
+ none: "none",
+ "top-left": "top-left",
+ "top-right": "top-right",
+ "bottom-left": "bottom-left",
+ "bottom-right": "bottom-right"
+ }
+},
+{
+ property: "sources",
+ title: "Other sources",
+ description: "List of other sources",
+ inputMethod: "array",
+ properties: [
+ {
+ property: "src",
+ title: "Source",
+ description: "The URL for this video.",
+ inputMethod: "textfield"
+ },
+ {
+ property: "type",
+ title: "Type",
+ description: "Media type data",
+ inputMethod: "select",
+ options: {
+ "audio/aac": "acc audio",
+ "audio/flac": "flac audio",
+ "audio/mp3": "mp3 audio",
+ "video/mp4": "mp4 video",
+ "video/mov": "mov video",
+ "audio/ogg": "ogg audio",
+ "video/ogg": "ogg video",
+ "audio/wav": "wav audio",
+ "audio/webm": "webm audio",
+ "video/webm": "webm video"
+ }
+ }
+ ]
+},
+{
+ property: "tracks",
+ title: "Track list",
+ description: "Tracks of different languages of closed captions",
+ inputMethod: "array",
+ properties: [
+ {
+ property: "kind",
+ title: "Kind",
+ description: "Kind of track",
+ inputMethod: "select",
+ options: {
+ subtitles:
+ "subtitles" /*,
+ Future Features
+ 'description': 'description',
+ 'thumbnails': 'thumbnails',
+ 'interactive': 'interactive',
+ 'annotation': 'annotation'*/
+ }
+ },
+ {
+ property: "label",
+ title: "Label",
+ description:
+ 'The human-readable name for this track, eg. "English Subtitles"',
+ inputMethod: "textfield"
+ },
+ {
+ property: "src",
+ title: "Source",
+ description: "Source of the track",
+ inputMethod: "textfield"
+ },
+ {
+ property: "srclang",
+ title:
+ 'Two letter, language code, eg. \'en\' for English, "de" for German, "es" for Spanish, etc.',
+ description: "Label",
+ inputMethod: "textfield"
+ }
+ ]
+}
+]
+}
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hello-world-element/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hello-world-element/index.html
new file mode 100644
index 0000000..a5d74ed
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hello-world-element/index.html
@@ -0,0 +1,63 @@
+
+// import the reference to HAXWiring to use in your element
+import { HAXWiring } from "@lrnwebcomponents/hax-body-behaviors/lib/HAXWiring.js";
+// connectedCallback is a life cycle hook in the web component specification
+// we tie into it so that when this element is appended to the DOM
+// it can tell HAX it exists
+connectedCallback() {
+// establish the wiring
+this.HAXWiring = new HAXWiring();
+// call setup which will ensure that it is setup when hax-store is ready
+this.HAXWiring.setup(
+ {
+ canScale: true,
+ canPosition: true,
+ canEditSource: false,
+ gizmo: {
+ title: "Example hax-element",
+ description:
+ "Provide an example to pick apart of a working HAX element",
+ icon: "icons:android",
+ color: "green",
+ groups: ["Hax"],
+ handles: [
+ {
+ type: "todo:read-the-docs-for-usage"
+ }
+ ],
+ meta: {
+ author: "You",
+ owner: "Your Company"
+ }
+ },
+ settings: {
+ quick: [],
+ configure: [
+ {
+ property: "title",
+ description: "",
+ inputMethod: "textfield",
+ required: false,
+ icon: "icons:android"
+ },
+ {
+ property: "available",
+ description: "",
+ inputMethod: "boolean",
+ required: false,
+ icon: "icons:android"
+ }
+ ],
+ advanced: []
+ }
+ },
+ 'example-hax-element',
+ this
+ );
+}
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/index.html
new file mode 100644
index 0000000..81a9f7f
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/index.html
@@ -0,0 +1,18 @@
+ # get the code
+npm install --save @lrnwebcomponents/h-a-x
+yarn add @lrnwebcomponents/h-a-x
+
+# reference it in your project
+import "@lrnwebcomponents/h-a-x/h-a-x.js";
+
+# use it in your template with an appstore definition if you like
+< h-a-x >
+
+ $ yarn global add @wcfactory/cli
+
+
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/concepts/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/concepts/index.html
new file mode 100644
index 0000000..829995c
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/concepts/index.html
@@ -0,0 +1,9 @@
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html
new file mode 100644
index 0000000..b1913fc
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html
@@ -0,0 +1,228 @@
+ # HAX the web and answer the prompts
+bash scripts/haxtheweb.sh
+
+ # /etc/apache2/apache2.conf
+
+<directory var/www/haxlocation>
+ Options Indexes FollowSymLinks
+ AllowOverride All
+ Require all granted
+</directory>
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/life-cycle/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/life-cycle/index.html
new file mode 100644
index 0000000..bf4fb27
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/life-cycle/index.html
@@ -0,0 +1,56 @@
+// file included which has the class in question
+include_once str_replace('_iamConfig/HAXcmsConfig.php', '', __FILE__) . '/system/lib/IAM.php';
+// in the configuration file HAXcmsConfig.php
+// this adds an event listener for the haxcms-jwt-get event
+// and then says to pass the data in question to class $IAM->getJwtUser();
+$HAXCMS->addEventListener('haxcms-jwt-get', array($IAM, 'getJwtUser'));
+// later on in additionally included code
+class IAM {
+/**
+ * Callback for event: haxcms-jwt-get
+ */
+ public function getJwtUser(&$token) {
+ if ($this->enterprise->userVar) {
+ $token['user'] = $this->enterprise->userVar;
+ }
+ }
+}
+// this ensures that there is a global $IAM object
+// it also ensures there's an instance so that when our above
+// listener fires it'll correctly associate to this code
+global $IAM;
+$IAM = new IAM();
+ cd haxcms/_sites/YOURSITE
+git checkout gh-pages
+git push origin gh-pages
+git checkout master
+git push origin master
+
+ {
+ "dependencies": {
+ "@lrnwebcomponents/haxcms-elements": "latest"
+ }
+}
+
+ import "@lrnwebcomponents/haxcms-elements/lib/ui-components/active-item/site-active-title.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/blocks/site-children-block.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/blocks/site-outline-block.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/layout/site-footer.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/layout/site-modal.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-breadcrumb.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-dot-indicator.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-top-menu.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-query-menu-slice.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-query.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-render-query.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-print-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-rss-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-title.js";
+
+ Hold up there. You didn't cover any of the query tags in that last section!
+
+ < site-query
+result="{{result}}"
+conditions='{"metadata.tag": "funny"}'
+>
+< /site-query>
+
+
+
+
+ Give me all of the pages who have a tag "Funny"
+
+ <
+ site-query-menu-slice
+ result="{{__items}}"
+ dynamic-methodology="[[dynamicMethodology]]"
+ start="[[start]]"
+ end="[[end]]"
+ parent="[[parent]]"
+ fixed-id="[[fixedId]]"
+ >
+ < /site-query-menu-slice>
+
+
+
+
+
+
+ Give me all child pages
+that are 2 to 4 levels deep. +
+ What type of query is this leveraging again?
+ site-query-menu-slice
+
+
+
+
+
+ // this is from the haxcms-basic-theme
+site-top-menu {
+ --site-top-menu-bg: #37474f;
+ --site-top-menu-link-color: #ffffff;
+ --site-top-menu-indicator-color: #ffffff;
+ --site-top-menu-link-active-color: var(
+ --haxcms-basic-theme-accent-color
+ );
+ --site-top-menu-indicator-arrow: 8px;
+}
+site-children-block {
+ --site-children-block-button: {
+ color: #ffffff;
+ }
+ --site-children-block-button-active: {
+ background-color: #37474f;
+ color: var(--haxcms-basic-theme-accent-color);
+ }
+}
+.left-col {
+ min-height: 250px;
+ border: 2px solid black;
+ background-color: #37474f;
+ color: white;
+ padding: 16px;
+}
+site-active-title {
+ display: inline-flex;
+ --site-active-title-heading: {
+ font-family: "Montserrat", "Helvetica", "Tahoma", "Geneva", "Arial",
+ sans-serif;
+ font-size: 16px;
+ line-height: 32px;
+ margin-bottom: 8px;
+ text-rendering: optimizelegibility;
+ font-weight: 600;
+ color: white;
+ }
+}
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/dev-workflows/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/dev-workflows/index.html
new file mode 100644
index 0000000..a1c3810
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/dev-workflows/index.html
@@ -0,0 +1,50 @@
+ "themes": {
+ "odl-haxtheme": {
+ "element": "odl-haxtheme",
+ "path": "@myorganization/odl-haxtheme/odl-haxtheme.js",
+ "name": "Eberly ODL"
+ }
+ },
+
+
+
+ /**
+ * Copyright 2019 The Pennsylvania State University
+ * @license Apache-2.0, see License.md for full text.
+ */
+import { html, PolymerElement } from "@polymer/polymer/polymer-element.js";
+import { HAXCMSTheme } from "@lrnwebcomponents/haxcms-elements/lib/core/HAXCMSThemeWiring.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-breadcrumb.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/active-item/site-active-title.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-title.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-rss-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-print-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu-button.js";
+import "@lrnwebcomponents/simple-colors/simple-colors.js";
+import "@polymer/app-layout/app-drawer/app-drawer.js";
+import "@polymer/app-layout/app-drawer-layout/app-drawer-layout.js";
+import "@polymer/paper-icon-button/paper-icon-button.js";
+
+/**
+ * `learn-two-theme`
+ * `Learn2 theme for HAXcms`
+ *
+ * @microcopy - language worth noting:
+ * -
+ *
+ * @customElement
+ * @polymer
+ * @demo demo/index.html
+ */
+class LearnTwoTheme extends HAXCMSTheme(PolymerElement) {
+ // render function
+ static get template() {
+ return html`
+ <style>
+ :host {
+ display: block;
+ font-family: "Muli", "Helvetica", "Tahoma", "Geneva", "Arial",
+ sans-serif;
+ letter-spacing: -0.03rem;
+ font-weight: 400;
+ background: #fafafa;
+ }
+ h1,
+ h2,
+ h3,
+ h4,
+ h5,
+ h6 {
+ font-family: "Montserrat", "Helvetica", "Tahoma", "Geneva", "Arial",
+ sans-serif;
+ font-weight: 400;
+ text-rendering: optimizeLegibility;
+ line-height: 150%;
+ letter-spacing: 0;
+ }
+ :host([hidden]) {
+ display: none;
+ }
+ :host([edit-mode]) #slot {
+ display: none;
+ }
+ #contentcontainer {
+ background: #fafafa;
+ padding: 48px 96px;
+ }
+ .header {
+ background: #747474;
+ color: #fafafa;
+ text-align: center;
+ padding: 0rem 1rem 2rem 1rem;
+ }
+ site-active-title {
+ --site-active-title-heading: {
+ font-family: "Montserrat", "Helvetica", "Tahoma", "Geneva", "Arial",
+ sans-serif;
+ font-size: 52px;
+ letter-spacing: -3px;
+ line-height: 78px;
+ margin-bottom: 27.2px;
+ margin-top: 13.6px;
+ text-align: center;
+ text-rendering: optimizelegibility;
+ font-weight: 100;
+ }
+ }
+ site-title {
+ position: relative;
+ overflow: hidden;
+ --site-title-link: {
+ display: inline-block;
+ color: #fafafa;
+ text-decoration: none;
+ }
+ --site-title-heading: {
+ font-family: "Montserrat", "Helvetica", "Tahoma", "Geneva", "Arial",
+ sans-serif;
+ font-size: 28px;
+ margin: 0;
+ padding: 0;
+ letter-spacing: -3px;
+ line-height: 78px;
+ text-align: center;
+ text-rendering: optimizelegibility;
+ font-weight: 100;
+ }
+ }
+ site-menu {
+ background-color: #383f45;
+ color: #ffffff;
+ padding: 0;
+ overflow: scroll;
+ max-height: calc(100vh - 200px);
+ --site-menu-active-color: #ffffff;
+ --site-menu: {
+ background-color: #383f45;
+ color: #ffffff;
+ }
+ --site-menu-container: {
+ padding: 0;
+ background-color: #2d3237;
+ }
+ --site-menu-item-active-item: {
+ color: #2d3237;
+ }
+ }
+ site-menu::-webkit-scrollbar-track {
+ -webkit-box-shadow: inset 0 0 4px rgba(56, 63, 69, 0.9);
+ border-radius: 0;
+ background-color: #383f45;
+ }
+ site-menu::-webkit-scrollbar {
+ width: 2px;
+ background-color: #383f45;
+ }
+ site-menu::-webkit-scrollbar-thumb {
+ border-radius: 1px;
+ -webkit-box-shadow: inset 0 0 4px #747474;
+ background-color: #383f45;
+ }
+ app-drawer-layout {
+ min-height: 100vh;
+ min-height: -moz-available;
+ min-height: -webkit-fill-available;
+ min-height: fill-available;
+ --app-drawer-width: 300px;
+ --app-drawer-scrim-background: rgba(80, 80, 80, 0.8);
+ --app-drawer-width: 300px;
+ --app-drawer-content-container: {
+ overflow: hidden;
+ background-color: #383f45;
+ }
+ }
+ .rss-buttons {
+ justify-content: space-evenly;
+ display: flex;
+ }
+ site-print-button {
+ --site-print-button-button: {
+ color: white;
+ }
+ }
+ app-drawer {
+ box-shadow: 0 0 6px -3px var(--haxcms-color, black);
+ overflow: hidden;
+ width: 300px;
+ }
+ app-drawer-layout[narrow] #contentcontainer {
+ padding: 0 16px;
+ }
+ #menubutton,
+ #menubutton2 {
+ display: none;
+ }
+ app-drawer-layout[narrow] #menubutton {
+ display: block;
+ }
+ app-drawer-layout[narrow] #menubutton2 {
+ display: block;
+ position: absolute;
+ z-index: 1;
+ }
+ app-drawer-layout[narrow] .header {
+ padding: 0;
+ }
+ site-menu-button {
+ position: fixed;
+ top: 0;
+ bottom: 0;
+ left: 300px;
+ --site-menu-button-icon: {
+ width: 64px;
+ height: 64px;
+ color: #2d3237;
+ }
+ --site-menu-button-button: {
+ background-color: rgba(0, 0, 0, 0);
+ width: 64px;
+ height: 100vh;
+ border-radius: 0;
+ transition: 0.4s all ease-in-out;
+ transition-delay: 0.2s;
+ margin: 0;
+ padding: 0;
+ opacity: 0.8;
+ -webkit-transition: 0.4s all ease-in-out;
+ -moz-transition: 0.4s all ease-in-out;
+ -ms-transition: 0.4s all ease-in-out;
+ -o-transition: 0.4s all ease-in-out;
+ }
+ }
+ site-menu-button:not([disabled]):hover,
+ site-menu-button:not([disabled]):active,
+ site-menu-button:not([disabled]):focus {
+ opacity: 1;
+ background-color: rgba(0, 0, 0, 0.1);
+ }
+ app-drawer-layout[narrow] site-menu {
+ max-height: calc(100vh - 160px);
+ }
+ app-drawer-layout[narrow] site-menu-button {
+ bottom: 0;
+ top: unset;
+ --site-menu-button-button: {
+ background-color: transparent !important;
+ width: 64px;
+ height: 64px;
+ }
+ }
+ site-menu-button[type="next"] {
+ right: 0;
+ left: unset;
+ }
+ app-drawer-layout[narrow] site-menu-button[type="prev"] {
+ left: unset;
+ }
+ :host([opened]) app-drawer-layout[narrow] site-menu-button[type="prev"],
+ :host([opened])
+ app-drawer-layout[narrow]
+ site-menu-button[type="next"] {
+ display: none;
+ }
+ </style>
+
+ <style>
+ html,
+ body {
+ background-color: #fafafa;
+ }
+ </style>
+
+ <style></style>
+
+
+
+
+ `;
+ }
+
+ // properties available to the custom element for data binding
+ static get properties() {
+ return {};
+ }
+
+ /**
+ * Store the tag name to make it easier to obtain directly.
+ * @notice function name must be here for tooling to operate correctly
+ */
+ static get tag() {
+ return "learn-two-theme";
+ }
+ /**
+ * Mix in an opened status
+ */
+ static get properties() {
+ let props = super.properties;
+ props.opened = {
+ type: Boolean,
+ reflectToAttribute: true
+ };
+ return props;
+ }
+ toggleDrawer(e) {
+ this.$.drawer.toggle();
+ }
+}
+window.customElements.define(LearnTwoTheme.tag, LearnTwoTheme);
+export { LearnTwoTheme };
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/skin-a-site/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/skin-a-site/index.html
new file mode 100644
index 0000000..0e82504
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/skin-a-site/index.html
@@ -0,0 +1,12 @@
+ import { html, PolymerElement } from "@polymer/polymer/polymer-element.js";
+import { HAXCMSTheme } from "@lrnwebcomponents/haxcms-elements/lib/core/HAXCMSThemeWiring.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-title.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-print-button.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/active-item/site-active-title.js";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-dot-indicator";
+import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu-button.js";
+import "@polymer/paper-icon-button/paper-icon-button.js";
+import "@polymer/iron-icons/iron-icons.js";
+import "@polymer/paper-tooltip/paper-tooltip.js";
+import "@lrnwebcomponents/simple-colors/simple-colors.js";
+import "@lrnwebcomponents/hax-body/lib/hax-shared-styles.js";
+
+ class HAXCMSSlideTheme extends HAXCMSTheme(PolymerElement) {
+
+
+ /**
+ * Hide the slotted content during edit mode. This must be here to work.
+ */
+:host([edit-mode]) #slot {
+ display: none;
+}
+
+
+
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/related-technologies/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/related-technologies/index.html
new file mode 100644
index 0000000..8faa138
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/related-technologies/index.html
@@ -0,0 +1,141 @@
+ // from https://www.tutorialspoint.com/json/json_schema.htm
+{
+ "$schema": "http://json-schema.org/draft-04/schema#",
+ "title": "Product",
+ "description": "A product from Acme's catalog",
+ "type": "object",
+
+ "properties": {
+
+ "id": {
+ "description": "The unique identifier for a product",
+ "type": "integer"
+ },
+
+ "name": {
+ "description": "Name of the product",
+ "type": "string"
+ },
+
+ "price": {
+ "type": "number",
+ "minimum": 0,
+ "exclusiveMinimum": true
+ }
+ },
+
+ "required": ["id", "name", "price"]
+}
+
+ {
+ "id": "unique-id-of-the-item-1",
+ "indent": "1",
+ "location": "name-of-some-file-or-location.html",
+ "order": "0",
+ "parent": "unique-id-of-the-parent",
+ "title": "Name of some file or location",
+ "metadata": {}
+}
+
+ {
+ "id": "123-ddc-d321d-d2e-dd2",
+ "title": "My outline",
+ "author": "LRNWebComponents",
+ "description": "A series of related material to teach you about the structure of content.",
+ "license": "by-sa",
+ "metadata": {},
+ "items": [
+ {
+ "id": "item-1",
+ "indent": "1",
+ "location": "outline.html",
+ "order": "0",
+ "parent": null,
+ "title": "Outline",
+ "description": "A description at a glance of this item potentially",
+ "metadata": {
+ "icon": "icons:view-quilt"
+ }
+ },
+ {
+ "id": "item-2",
+ "indent": "2",
+ "location": "introduction.html",
+ "order": "0",
+ "parent": "item-1",
+ "title": "Introduction to outlines",
+ "description": "A description at a glance of this item potentially",
+ "metadata": {}
+ },
+ {
+ "id": "item-3",
+ "indent": "2",
+ "location": "files/a-2nd-page-item.html",
+ "order": "1",
+ "parent": "item-1",
+ "title": "An item in an outline",
+ "description": "A description at a glance of this item potentially",
+ "metadata": {}
+ }
+ ]
+}
+
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html
new file mode 100644
index 0000000..544941f
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html
@@ -0,0 +1,3 @@
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html
new file mode 100644
index 0000000..ef95f78
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html
@@ -0,0 +1,6 @@
+
+
+
+
+<script></script>
+(function ($) {
+ $(document).ready(function () {
+ // HAX the Press
+ var haxThePress = document.createElement('wysiwyg-hax');
+ var temp = document.createElement('template');
+ // target the TinyMCE area
+ const content = document.querySelector('textarea#content');
+ // replicate what it was providing to the light DOM
+ haxThePress.fieldClass = 'wp-editor-area';
+ haxThePress.fieldName = 'content';
+ haxThePress.fieldId = 'content';
+ haxThePress.openDefault = true;
+ haxThePress.elementAlign = 'left';
+ haxThePress.saveButtonSelector = document.querySelector('input[type="submit"]#publish');
+ if (window.haxThePressConnector) {
+ haxThePress.appStoreConnection = window.haxThePressConnector;
+ }
+ // set the template tag to the content previously in the textarea
+ temp.innerHTML = content.value;
+ // append the template tag into the wysiwyg
+ haxThePress.appendChild(temp.cloneNode(true));
+ // insert the field exactly where the tinymce was
+ content.parentNode.insertBefore(haxThePress, content);
+ // HAX the web
+ content.parentNode.removeChild(content);
+ });
+})(jQuery);
+
+
+
+ 
+
+
+
+ 
+
+
+
+
+haxHooks() {
+ return {
+ activeElementChanged: "haxactiveElementChanged",
+ editModeChanged : "haxeditModeChanged",
+ inlineContextMenu: "haxinlineContextMenu",
+ gizmoRegistration: "haxgizmoRegistration",
+ preProcessNodeToContent : "haxpreProcessNodeToContent",
+ postProcessNodeToContent : "haxpostProcessNodeToContent",
+ progressiveEnhancement: "haxprogressiveEnhancement",
+ preProcessInsertContent : "haxpreProcessInsertContent"
+ };
+}
+
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/item-aa589faa-e860-4221-82fa-df6d57328ac2/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/item-aa589faa-e860-4221-82fa-df6d57328ac2/index.html
new file mode 100644
index 0000000..bc88559
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/item-aa589faa-e860-4221-82fa-df6d57328ac2/index.html
@@ -0,0 +1,2 @@
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html
new file mode 100644
index 0000000..32477e4
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html
@@ -0,0 +1,46 @@
+
+ import { I18NMixin } from "@lrnwebcomponents/i18n-manager/lib/I18NMixin.js";
+class MyElement extends I18NMixin(HTMLElement) {
+ constructor() {
+ this.t = {
+ stuff: "Stuff"
+ };
+ this.registerLocalization({
+ context: this,
+ basePath: import.meta.url,
+ locales: ["es", "ja"],
+ });
+ connectedCallback() {
+ this.render();
+ }
+ render() {
+ this.innerHTML = `${this.t.stuff}`;
+ }
+ }
+}
+
+
+ window.dispatchEvent(
+ new CustomEvent("i18n-manager-register-element", {
+ detail: {
+ namespace: "my-element.haxProperties",
+ localesPath: decodeURIComponent(import.meta.url) + "/../locales",
+ locales: ["es"],
+ },
+ })
+ );
+
+Become part of our dynasty franchise *
+
+
+# HAX editor stand alone for use in apps
+yarn add @lrnwebcomponents/h-a-x
+# or Integrate with a textarea like older wysiwyg editors
+yarn add @lrnwebcomponents/wysiwyg-hax
+
+
+# the video-player tag works with HAX but works ANYWHERE regardless of it
+yarn add @lrnwebcomponents/video-player
+
+ 
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxiam/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxiam/index.html
new file mode 100644
index 0000000..de95af0
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxiam/index.html
@@ -0,0 +1,5 @@
+
+
+<meme-maker
+ alt="mother of god shades GIF"
+ image-url="https://media2.giphy.com/media/3cB7aOM6347PW/giphy.gif"
+ top-text="Web components"
+ bottom-text="It's "the" platform"
+ style="width: 50%;">
+</meme-maker>
+
+ 
+
+
+
+
+
+
+
+
+
+ hax-the-web
+ https://haxtheweb.org//rss.xml
+ Project home and documentation for all things HAX
+ Copyright (C) 2024 https://haxtheweb.org/
+ en-us
+ 1970-01-20T23:35:16.452Z
+
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/service-worker.js b/github-pages-deploy-action-temp-deployment-folder/service-worker.js
new file mode 100644
index 0000000..48dda06
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/service-worker.js
@@ -0,0 +1,290 @@
+/**
+ * Copyright 2016 Google Inc. All rights reserved.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+*/
+
+// DO NOT EDIT THIS GENERATED OUTPUT DIRECTLY!
+// This file should be overwritten as part of your build process.
+// If you need to extend the behavior of the generated service worker, the best approach is to write
+// additional code and include it using the importScripts option:
+// https://github.com/GoogleChrome/sw-precache#importscripts-arraystring
+//
+// Alternatively, it's possible to make changes to the underlying template file and then use that as the
+// new base for generating output, via the templateFilePath option:
+// https://github.com/GoogleChrome/sw-precache#templatefilepath-string
+//
+// If you go that route, make sure that whenever you update your sw-precache dependency, you reconcile any
+// changes made to this original template file with your modified copy.
+
+// This generated service worker JavaScript will precache your site's resources.
+// The code needs to be saved in a .js file at the top-level of your site, and registered
+// from your pages in order to be used. See
+// https://github.com/googlechrome/sw-precache/blob/master/demo/app/js/service-worker-registration.js
+// for an example of how you can register this script and handle various service worker events.
+
+/* eslint-env worker, serviceworker */
+/* eslint-disable indent, no-unused-vars, no-multiple-empty-lines, max-nested-callbacks, space-before-function-paren, quotes, comma-spacing */
+'use strict';
+
+var precacheConfig = {{ swhash|json_encode(constant('JSON_PRETTY_PRINT'))|raw }};
+var cacheName = 'sw-precache-v3--' + (self.registration ? self.registration.scope : '');
+
+
+var ignoreUrlParametersMatching = [/^utm_/];
+
+
+
+var addDirectoryIndex = function (originalUrl, index) {
+ var url = new URL(originalUrl);
+ if (url.pathname.slice(-1) === '/') {
+ url.pathname += index;
+ }
+ return url.toString();
+};
+
+var cleanResponse = function (originalResponse) {
+ // If this is not a redirected response, then we don't have to do anything.
+ if (!originalResponse.redirected) {
+ return Promise.resolve(originalResponse);
+ }
+
+ // Firefox 50 and below doesn't support the Response.body stream, so we may
+ // need to read the entire body to memory as a Blob.
+ var bodyPromise = 'body' in originalResponse ?
+ Promise.resolve(originalResponse.body) :
+ originalResponse.blob();
+
+ return bodyPromise.then(function (body) {
+ // new Response() is happy when passed either a stream or a Blob.
+ return new Response(body, {
+ headers: originalResponse.headers,
+ status: originalResponse.status,
+ statusText: originalResponse.statusText
+ });
+ });
+};
+
+var createCacheKey = function (originalUrl, paramName, paramValue,
+ dontCacheBustUrlsMatching) {
+ // Create a new URL object to avoid modifying originalUrl.
+ var url = new URL(originalUrl);
+
+ // If dontCacheBustUrlsMatching is not set, or if we don't have a match,
+ // then add in the extra cache-busting URL parameter.
+ if (!dontCacheBustUrlsMatching ||
+ !(url.pathname.match(dontCacheBustUrlsMatching))) {
+ url.search += (url.search ? '&' : '') +
+ encodeURIComponent(paramName) + '=' + encodeURIComponent(paramValue);
+ }
+
+ return url.toString();
+};
+
+var isPathWhitelisted = function (whitelist, absoluteUrlString) {
+ // If the whitelist is empty, then consider all URLs to be whitelisted.
+ if (whitelist.length === 0) {
+ return true;
+ }
+
+ // Otherwise compare each path regex to the path of the URL passed in.
+ var path = (new URL(absoluteUrlString)).pathname;
+ return whitelist.some(function (whitelistedPathRegex) {
+ return path.match(whitelistedPathRegex);
+ });
+};
+
+var stripIgnoredUrlParameters = function (originalUrl,
+ ignoreUrlParametersMatching) {
+ var url = new URL(originalUrl);
+ // Remove the hash; see https://github.com/GoogleChrome/sw-precache/issues/290
+ url.hash = '';
+
+ url.search = url.search.slice(1) // Exclude initial '?'
+ .split('&') // Split into an array of 'key=value' strings
+ .map(function (kv) {
+ return kv.split('='); // Split each 'key=value' string into a [key, value] array
+ })
+ .filter(function (kv) {
+ return ignoreUrlParametersMatching.every(function (ignoredRegex) {
+ return !ignoredRegex.test(kv[0]); // Return true iff the key doesn't match any of the regexes.
+ });
+ })
+ .map(function (kv) {
+ return kv.join('='); // Join each [key, value] array into a 'key=value' string
+ })
+ .join('&'); // Join the array of 'key=value' strings into a string with '&' in between each
+
+ return url.toString();
+};
+
+
+var hashParamName = '_sw-precache';
+var urlsToCacheKeys = new Map(
+ precacheConfig.map(function (item) {
+ var relativeUrl = item[0];
+ var hash = item[1];
+ var absoluteUrl = new URL(relativeUrl, self.location);
+ var cacheKey = createCacheKey(absoluteUrl, hashParamName, hash, false);
+ return [absoluteUrl.toString(), cacheKey];
+ })
+);
+
+function setOfCachedUrls(cache) {
+ return cache.keys().then(function (requests) {
+ return requests.map(function (request) {
+ return request.url;
+ });
+ }).then(function (urls) {
+ return new Set(urls);
+ });
+}
+
+self.addEventListener('install', function (event) {
+ event.waitUntil(
+ caches.open(cacheName).then(function (cache) {
+ return setOfCachedUrls(cache).then(function (cachedUrls) {
+ return Promise.all(
+ Array.from(urlsToCacheKeys.values()).map(function (cacheKey) {
+ // If we don't have a key matching url in the cache already, add it.
+ if (!cachedUrls.has(cacheKey)) {
+ var request = new Request(cacheKey, { credentials: 'same-origin' });
+ return fetch(request).then(function (response) {
+ // Bail out of installation unless we get back a 200 OK for
+ // every request.
+ if (!response.ok) {
+ throw new Error('Request for ' + cacheKey + ' returned a ' +
+ 'response with status ' + response.status);
+ }
+
+ return cleanResponse(response).then(function (responseToCache) {
+ return cache.put(cacheKey, responseToCache);
+ });
+ });
+ }
+ })
+ );
+ });
+ }).then(function () {
+
+ // Force the SW to transition from installing -> active state
+ return self.skipWaiting();
+
+ })
+ );
+});
+
+self.addEventListener('activate', function (event) {
+ var setOfExpectedUrls = new Set(urlsToCacheKeys.values());
+
+ event.waitUntil(
+ caches.open(cacheName).then(function (cache) {
+ return cache.keys().then(function (existingRequests) {
+ return Promise.all(
+ existingRequests.map(function (existingRequest) {
+ if (!setOfExpectedUrls.has(existingRequest.url)) {
+ return cache.delete(existingRequest);
+ }
+ })
+ );
+ });
+ }).then(function () {
+
+ return self.clients.claim();
+
+ })
+ );
+});
+
+
+self.addEventListener('fetch', function (event) {
+ if (event.request.method === 'GET') {
+ // Should we call event.respondWith() inside this fetch event handler?
+ // This needs to be determined synchronously, which will give other fetch
+ // handlers a chance to handle the request if need be.
+ var shouldRespond;
+
+ // First, remove all the ignored parameters and hash fragment, and see if we
+ // have that URL in our cache. If so, great! shouldRespond will be true.
+ var url = stripIgnoredUrlParameters(event.request.url, ignoreUrlParametersMatching);
+ shouldRespond = urlsToCacheKeys.has(url);
+
+ // If shouldRespond is false, check again, this time with 'index.html'
+ // (or whatever the directoryIndex option is set to) at the end.
+ var directoryIndex = '';
+ if (!shouldRespond && directoryIndex) {
+ url = addDirectoryIndex(url, directoryIndex);
+ shouldRespond = urlsToCacheKeys.has(url);
+ }
+
+ // If shouldRespond is still false, check to see if this is a navigation
+ // request, and if so, whether the URL matches navigateFallbackWhitelist.
+ var navigateFallback = 'index.html';
+ if (!shouldRespond &&
+ navigateFallback &&
+ (event.request.mode === 'navigate') &&
+ isPathWhitelisted(["\\/[^\\/\\.]*(\\?|$)"], event.request.url)) {
+ url = new URL(navigateFallback, self.location).toString();
+ shouldRespond = urlsToCacheKeys.has(url);
+ }
+
+ // If shouldRespond was set to true at any point, then call
+ // event.respondWith(), using the appropriate cache key.
+ if (shouldRespond) {
+ event.respondWith(
+ caches.open(cacheName).then(function (cache) {
+ return cache.match(urlsToCacheKeys.get(url)).then(function (response) {
+ if (response) {
+ return response;
+ }
+ throw Error('The cached response that was expected is missing.');
+ });
+ }).catch(function (e) {
+ // Fall back to just fetch()ing the request if some unexpected error
+ // prevented the cached response from being valid.
+ console.warn('Couldn\'t serve response for "%s" from cache: %O', event.request.url, e);
+ return fetch(event.request);
+ })
+ );
+ }
+ }
+});
+
+
+// *** Start of auto-included sw-toolbox code. ***
+/*
+ Copyright 2016 Google Inc. All Rights Reserved.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+*/
+!function (e) { if ("object" == typeof exports && "undefined" != typeof module) module.exports = e(); else if ("function" == typeof define && define.amd) define([], e); else { var t; t = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof self ? self : this, t.toolbox = e() } }(function () { return function e(t, n, r) { function o(c, s) { if (!n[c]) { if (!t[c]) { var a = "function" == typeof require && require; if (!s && a) return a(c, !0); if (i) return i(c, !0); var u = new Error("Cannot find module '" + c + "'"); throw u.code = "MODULE_NOT_FOUND", u } var f = n[c] = { exports: {} }; t[c][0].call(f.exports, function (e) { var n = t[c][1][e]; return o(n ? n : e) }, f, f.exports, e, t, n, r) } return n[c].exports } for (var i = "function" == typeof require && require, c = 0; c < r.length; c++)o(r[c]); return o }({ 1: [function (e, t, n) { "use strict"; function r(e, t) { t = t || {}; var n = t.debug || m.debug; n && console.log("[sw-toolbox] " + e) } function o(e) { var t; return e && e.cache && (t = e.cache.name), t = t || m.cache.name, caches.open(t) } function i(e, t) { t = t || {}; var n = t.successResponses || m.successResponses; return fetch(e.clone()).then(function (r) { return "GET" === e.method && n.test(r.status) && o(t).then(function (n) { n.put(e, r).then(function () { var r = t.cache || m.cache; (r.maxEntries || r.maxAgeSeconds) && r.name && c(e, n, r) }) }), r.clone() }) } function c(e, t, n) { var r = s.bind(null, e, t, n); d = d ? d.then(r) : r() } function s(e, t, n) { var o = e.url, i = n.maxAgeSeconds, c = n.maxEntries, s = n.name, a = Date.now(); return r("Updating LRU order for " + o + ". Max entries is " + c + ", max age is " + i), g.getDb(s).then(function (e) { return g.setTimestampForUrl(e, o, a) }).then(function (e) { return g.expireEntries(e, c, i, a) }).then(function (e) { r("Successfully updated IDB."); var n = e.map(function (e) { return t.delete(e) }); return Promise.all(n).then(function () { r("Done with cache cleanup.") }) }).catch(function (e) { r(e) }) } function a(e, t, n) { return r("Renaming cache: [" + e + "] to [" + t + "]", n), caches.delete(t).then(function () { return Promise.all([caches.open(e), caches.open(t)]).then(function (t) { var n = t[0], r = t[1]; return n.keys().then(function (e) { return Promise.all(e.map(function (e) { return n.match(e).then(function (t) { return r.put(e, t) }) })) }).then(function () { return caches.delete(e) }) }) }) } function u(e, t) { return o(t).then(function (t) { return t.add(e) }) } function f(e, t) { return o(t).then(function (t) { return t.delete(e) }) } function h(e) { e instanceof Promise || p(e), m.preCacheItems = m.preCacheItems.concat(e) } function p(e) { var t = Array.isArray(e); if (t && e.forEach(function (e) { "string" == typeof e || e instanceof Request || (t = !1) }), !t) throw new TypeError("The precache method expects either an array of strings and/or Requests or a Promise that resolves to an array of strings and/or Requests."); return e } function l(e, t, n) { if (!e) return !1; if (t) { var r = e.headers.get("date"); if (r) { var o = new Date(r); if (o.getTime() + 1e3 * t < n) return !1 } } return !0 } var d, m = e("./options"), g = e("./idb-cache-expiration"); t.exports = { debug: r, fetchAndCache: i, openCache: o, renameCache: a, cache: u, uncache: f, precache: h, validatePrecacheInput: p, isResponseFresh: l } }, { "./idb-cache-expiration": 2, "./options": 4 }], 2: [function (e, t, n) { "use strict"; function r(e) { return new Promise(function (t, n) { var r = indexedDB.open(u + e, f); r.onupgradeneeded = function () { var e = r.result.createObjectStore(h, { keyPath: p }); e.createIndex(l, l, { unique: !1 }) }, r.onsuccess = function () { t(r.result) }, r.onerror = function () { n(r.error) } }) } function o(e) { return e in d || (d[e] = r(e)), d[e] } function i(e, t, n) { return new Promise(function (r, o) { var i = e.transaction(h, "readwrite"), c = i.objectStore(h); c.put({ url: t, timestamp: n }), i.oncomplete = function () { r(e) }, i.onabort = function () { o(i.error) } }) } function c(e, t, n) { return t ? new Promise(function (r, o) { var i = 1e3 * t, c = [], s = e.transaction(h, "readwrite"), a = s.objectStore(h), u = a.index(l); u.openCursor().onsuccess = function (e) { var t = e.target.result; if (t && n - i > t.value[l]) { var r = t.value[p]; c.push(r), a.delete(r), t.continue() } }, s.oncomplete = function () { r(c) }, s.onabort = o }) : Promise.resolve([]) } function s(e, t) { return t ? new Promise(function (n, r) { var o = [], i = e.transaction(h, "readwrite"), c = i.objectStore(h), s = c.index(l), a = s.count(); s.count().onsuccess = function () { var e = a.result; e > t && (s.openCursor().onsuccess = function (n) { var r = n.target.result; if (r) { var i = r.value[p]; o.push(i), c.delete(i), e - o.length > t && r.continue() } }) }, i.oncomplete = function () { n(o) }, i.onabort = r }) : Promise.resolve([]) } function a(e, t, n, r) { return c(e, n, r).then(function (n) { return s(e, t).then(function (e) { return n.concat(e) }) }) } var u = "sw-toolbox-", f = 1, h = "store", p = "url", l = "timestamp", d = {}; t.exports = { getDb: o, setTimestampForUrl: i, expireEntries: a } }, {}], 3: [function (e, t, n) { "use strict"; function r(e) { var t = a.match(e.request); t ? e.respondWith(t(e.request)) : a.default && "GET" === e.request.method && 0 === e.request.url.indexOf("http") && e.respondWith(a.default(e.request)) } function o(e) { s.debug("activate event fired"); var t = u.cache.name + "$$$inactive$$$"; e.waitUntil(s.renameCache(t, u.cache.name)) } function i(e) { return e.reduce(function (e, t) { return e.concat(t) }, []) } function c(e) { var t = u.cache.name + "$$$inactive$$$"; s.debug("install event fired"), s.debug("creating cache [" + t + "]"), e.waitUntil(s.openCache({ cache: { name: t } }).then(function (e) { return Promise.all(u.preCacheItems).then(i).then(s.validatePrecacheInput).then(function (t) { return s.debug("preCache list: " + (t.join(", ") || "(none)")), e.addAll(t) }) })) } e("serviceworker-cache-polyfill"); var s = e("./helpers"), a = e("./router"), u = e("./options"); t.exports = { fetchListener: r, activateListener: o, installListener: c } }, { "./helpers": 1, "./options": 4, "./router": 6, "serviceworker-cache-polyfill": 16 }], 4: [function (e, t, n) { "use strict"; var r; r = self.registration ? self.registration.scope : self.scope || new URL("./", self.location).href, t.exports = { cache: { name: "$$$toolbox-cache$$$" + r + "$$$", maxAgeSeconds: null, maxEntries: null }, debug: !1, networkTimeoutSeconds: null, preCacheItems: [], successResponses: /^0|([123]\d\d)|(40[14567])|410$/ } }, {}], 5: [function (e, t, n) { "use strict"; var r = new URL("./", self.location), o = r.pathname, i = e("path-to-regexp"), c = function (e, t, n, r) { t instanceof RegExp ? this.fullUrlRegExp = t : (0 !== t.indexOf("/") && (t = o + t), this.keys = [], this.regexp = i(t, this.keys)), this.method = e, this.options = r, this.handler = n }; c.prototype.makeHandler = function (e) { var t; if (this.regexp) { var n = this.regexp.exec(e); t = {}, this.keys.forEach(function (e, r) { t[e.name] = n[r + 1] }) } return function (e) { return this.handler(e, t, this.options) }.bind(this) }, t.exports = c }, { "path-to-regexp": 15 }], 6: [function (e, t, n) { "use strict"; function r(e) { return e.replace(/[-\/\\^$*+?.()|[\]{}]/g, "\\$&") } var o = e("./route"), i = e("./helpers"), c = function (e, t) { for (var n = e.entries(), r = n.next(), o = []; !r.done;) { var i = new RegExp(r.value[0]); i.test(t) && o.push(r.value[1]), r = n.next() } return o }, s = function () { this.routes = new Map, this.routes.set(RegExp, new Map), this.default = null };["get", "post", "put", "delete", "head", "any"].forEach(function (e) { s.prototype[e] = function (t, n, r) { return this.add(e, t, n, r) } }), s.prototype.add = function (e, t, n, c) { c = c || {}; var s; t instanceof RegExp ? s = RegExp : (s = c.origin || self.location.origin, s = s instanceof RegExp ? s.source : r(s)), e = e.toLowerCase(); var a = new o(e, t, n, c); this.routes.has(s) || this.routes.set(s, new Map); var u = this.routes.get(s); u.has(e) || u.set(e, new Map); var f = u.get(e), h = a.regexp || a.fullUrlRegExp; f.has(h.source) && i.debug('"' + t + '" resolves to same regex as existing route.'), f.set(h.source, a) }, s.prototype.matchMethod = function (e, t) { var n = new URL(t), r = n.origin, o = n.pathname; return this._match(e, c(this.routes, r), o) || this._match(e, [this.routes.get(RegExp)], t) }, s.prototype._match = function (e, t, n) { if (0 === t.length) return null; for (var r = 0; r < t.length; r++) { var o = t[r], i = o && o.get(e.toLowerCase()); if (i) { var s = c(i, n); if (s.length > 0) return s[0].makeHandler(n) } } return null }, s.prototype.match = function (e) { return this.matchMethod(e.method, e.url) || this.matchMethod("any", e.url) }, t.exports = new s }, { "./helpers": 1, "./route": 5 }], 7: [function (e, t, n) { "use strict"; function r(e, t, n) { return n = n || {}, i.debug("Strategy: cache first [" + e.url + "]", n), i.openCache(n).then(function (t) { return t.match(e).then(function (t) { var r = n.cache || o.cache, c = Date.now(); return i.isResponseFresh(t, r.maxAgeSeconds, c) ? t : i.fetchAndCache(e, n) }) }) } var o = e("../options"), i = e("../helpers"); t.exports = r }, { "../helpers": 1, "../options": 4 }], 8: [function (e, t, n) { "use strict"; function r(e, t, n) { return n = n || {}, i.debug("Strategy: cache only [" + e.url + "]", n), i.openCache(n).then(function (t) { return t.match(e).then(function (e) { var t = n.cache || o.cache, r = Date.now(); if (i.isResponseFresh(e, t.maxAgeSeconds, r)) return e }) }) } var o = e("../options"), i = e("../helpers"); t.exports = r }, { "../helpers": 1, "../options": 4 }], 9: [function (e, t, n) { "use strict"; function r(e, t, n) { return o.debug("Strategy: fastest [" + e.url + "]", n), new Promise(function (r, c) { var s = !1, a = [], u = function (e) { a.push(e.toString()), s ? c(new Error('Both cache and network failed: "' + a.join('", "') + '"')) : s = !0 }, f = function (e) { e instanceof Response ? r(e) : u("No result returned") }; o.fetchAndCache(e.clone(), n).then(f, u), i(e, t, n).then(f, u) }) } var o = e("../helpers"), i = e("./cacheOnly"); t.exports = r }, { "../helpers": 1, "./cacheOnly": 8 }], 10: [function (e, t, n) { t.exports = { networkOnly: e("./networkOnly"), networkFirst: e("./networkFirst"), cacheOnly: e("./cacheOnly"), cacheFirst: e("./cacheFirst"), fastest: e("./fastest") } }, { "./cacheFirst": 7, "./cacheOnly": 8, "./fastest": 9, "./networkFirst": 11, "./networkOnly": 12 }], 11: [function (e, t, n) { "use strict"; function r(e, t, n) { n = n || {}; var r = n.successResponses || o.successResponses, c = n.networkTimeoutSeconds || o.networkTimeoutSeconds; return i.debug("Strategy: network first [" + e.url + "]", n), i.openCache(n).then(function (t) { var s, a, u = []; if (c) { var f = new Promise(function (r) { s = setTimeout(function () { t.match(e).then(function (e) { var t = n.cache || o.cache, c = Date.now(), s = t.maxAgeSeconds; i.isResponseFresh(e, s, c) && r(e) }) }, 1e3 * c) }); u.push(f) } var h = i.fetchAndCache(e, n).then(function (e) { if (s && clearTimeout(s), r.test(e.status)) return e; throw i.debug("Response was an HTTP error: " + e.statusText, n), a = e, new Error("Bad response") }).catch(function (r) { return i.debug("Network or response error, fallback to cache [" + e.url + "]", n), t.match(e).then(function (e) { if (e) return e; if (a) return a; throw r }) }); return u.push(h), Promise.race(u) }) } var o = e("../options"), i = e("../helpers"); t.exports = r }, { "../helpers": 1, "../options": 4 }], 12: [function (e, t, n) { "use strict"; function r(e, t, n) { return o.debug("Strategy: network only [" + e.url + "]", n), fetch(e) } var o = e("../helpers"); t.exports = r }, { "../helpers": 1 }], 13: [function (e, t, n) { "use strict"; var r = e("./options"), o = e("./router"), i = e("./helpers"), c = e("./strategies"), s = e("./listeners"); i.debug("Service Worker Toolbox is loading"), self.addEventListener("install", s.installListener), self.addEventListener("activate", s.activateListener), self.addEventListener("fetch", s.fetchListener), t.exports = { networkOnly: c.networkOnly, networkFirst: c.networkFirst, cacheOnly: c.cacheOnly, cacheFirst: c.cacheFirst, fastest: c.fastest, router: o, options: r, cache: i.cache, uncache: i.uncache, precache: i.precache } }, { "./helpers": 1, "./listeners": 3, "./options": 4, "./router": 6, "./strategies": 10 }], 14: [function (e, t, n) { t.exports = Array.isArray || function (e) { return "[object Array]" == Object.prototype.toString.call(e) } }, {}], 15: [function (e, t, n) { function r(e, t) { for (var n, r = [], o = 0, i = 0, c = "", s = t && t.delimiter || "/"; null != (n = x.exec(e));) { var f = n[0], h = n[1], p = n.index; if (c += e.slice(i, p), i = p + f.length, h) c += h[1]; else { var l = e[i], d = n[2], m = n[3], g = n[4], v = n[5], w = n[6], y = n[7]; c && (r.push(c), c = ""); var b = null != d && null != l && l !== d, E = "+" === w || "*" === w, R = "?" === w || "*" === w, k = n[2] || s, $ = g || v; r.push({ name: m || o++, prefix: d || "", delimiter: k, optional: R, repeat: E, partial: b, asterisk: !!y, pattern: $ ? u($) : y ? ".*" : "[^" + a(k) + "]+?" }) } } return i < e.length && (c += e.substr(i)), c && r.push(c), r } function o(e, t) { return s(r(e, t)) } function i(e) { return encodeURI(e).replace(/[\/?#]/g, function (e) { return "%" + e.charCodeAt(0).toString(16).toUpperCase() }) } function c(e) { return encodeURI(e).replace(/[?#]/g, function (e) { return "%" + e.charCodeAt(0).toString(16).toUpperCase() }) } function s(e) { for (var t = new Array(e.length), n = 0; n < e.length; n++)"object" == typeof e[n] && (t[n] = new RegExp("^(?:" + e[n].pattern + ")$")); return function (n, r) { for (var o = "", s = n || {}, a = r || {}, u = a.pretty ? i : encodeURIComponent, f = 0; f < e.length; f++) { var h = e[f]; if ("string" != typeof h) { var p, l = s[h.name]; if (null == l) { if (h.optional) { h.partial && (o += h.prefix); continue } throw new TypeError('Expected "' + h.name + '" to be defined') } if (v(l)) { if (!h.repeat) throw new TypeError('Expected "' + h.name + '" to not repeat, but received `' + JSON.stringify(l) + "`"); if (0 === l.length) { if (h.optional) continue; throw new TypeError('Expected "' + h.name + '" to not be empty') } for (var d = 0; d < l.length; d++) { if (p = u(l[d]), !t[f].test(p)) throw new TypeError('Expected all "' + h.name + '" to match "' + h.pattern + '", but received `' + JSON.stringify(p) + "`"); o += (0 === d ? h.prefix : h.delimiter) + p } } else { if (p = h.asterisk ? c(l) : u(l), !t[f].test(p)) throw new TypeError('Expected "' + h.name + '" to match "' + h.pattern + '", but received "' + p + '"'); o += h.prefix + p } } else o += h } return o } } function a(e) { return e.replace(/([.+*?=^!:${}()[\]|\/\\])/g, "\\$1") } function u(e) { return e.replace(/([=!:$\/()])/g, "\\$1") } function f(e, t) { return e.keys = t, e } function h(e) { return e.sensitive ? "" : "i" } function p(e, t) { var n = e.source.match(/\((?!\?)/g); if (n) for (var r = 0; r < n.length; r++)t.push({ name: r, prefix: null, delimiter: null, optional: !1, repeat: !1, partial: !1, asterisk: !1, pattern: null }); return f(e, t) } function l(e, t, n) { for (var r = [], o = 0; o < e.length; o++)r.push(g(e[o], t, n).source); var i = new RegExp("(?:" + r.join("|") + ")", h(n)); return f(i, t) } function d(e, t, n) { return m(r(e, n), t, n) } function m(e, t, n) { v(t) || (n = t || n, t = []), n = n || {}; for (var r = n.strict, o = n.end !== !1, i = "", c = 0; c < e.length; c++) { var s = e[c]; if ("string" == typeof s) i += a(s); else { var u = a(s.prefix), p = "(?:" + s.pattern + ")"; t.push(s), s.repeat && (p += "(?:" + u + p + ")*"), p = s.optional ? s.partial ? u + "(" + p + ")?" : "(?:" + u + "(" + p + "))?" : u + "(" + p + ")", i += p } } var l = a(n.delimiter || "/"), d = i.slice(-l.length) === l; return r || (i = (d ? i.slice(0, -l.length) : i) + "(?:" + l + "(?=$))?"), i += o ? "$" : r && d ? "" : "(?=" + l + "|$)", f(new RegExp("^" + i, h(n)), t) } function g(e, t, n) { return v(t) || (n = t || n, t = []), n = n || {}, e instanceof RegExp ? p(e, t) : v(e) ? l(e, t, n) : d(e, t, n) } var v = e("isarray"); t.exports = g, t.exports.parse = r, t.exports.compile = o, t.exports.tokensToFunction = s, t.exports.tokensToRegExp = m; var x = new RegExp(["(\\\\.)", "([\\/.])?(?:(?:\\:(\\w+)(?:\\(((?:\\\\.|[^\\\\()])+)\\))?|\\(((?:\\\\.|[^\\\\()])+)\\))([+*?])?|(\\*))"].join("|"), "g") }, { isarray: 14 }], 16: [function (e, t, n) { !function () { var e = Cache.prototype.addAll, t = navigator.userAgent.match(/(Firefox|Chrome)\/(\d+\.)/); if (t) var n = t[1], r = parseInt(t[2]); e && (!t || "Firefox" === n && r >= 46 || "Chrome" === n && r >= 50) || (Cache.prototype.addAll = function (e) { function t(e) { this.name = "NetworkError", this.code = 19, this.message = e } var n = this; return t.prototype = Object.create(Error.prototype), Promise.resolve().then(function () { if (arguments.length < 1) throw new TypeError; return e = e.map(function (e) { return e instanceof Request ? e : String(e) }), Promise.all(e.map(function (e) { "string" == typeof e && (e = new Request(e)); var n = new URL(e.url).protocol; if ("http:" !== n && "https:" !== n) throw new t("Invalid scheme"); return fetch(e.clone()) })) }).then(function (r) { if (r.some(function (e) { return !e.ok })) throw new t("Incorrect response status"); return Promise.all(r.map(function (t, r) { return n.put(e[r], t) })) }).then(function () { }) }, Cache.prototype.add = function (e) { return this.addAll([e]) }) }() }, {}] }, {}, [13])(13) });
+
+
+// *** End of auto-included sw-toolbox code. ***
+
+
+
+// Runtime cache configuration, using the sw-toolbox library.
+{% if cdnRegex %}
+toolbox.router.get(/{{ cdnRegex|raw }}/, toolbox.fastest, {});
+{% endif %}
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/site.json b/github-pages-deploy-action-temp-deployment-folder/site.json
new file mode 100644
index 0000000..6e7460c
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/site.json
@@ -0,0 +1,1594 @@
+{
+ "id": "95f2b045-cfdb-4e35-b29b-e7f71c859987",
+ "title": "hax-the-web",
+ "author": "elmsln",
+ "description": "Project home and documentation for all things HAX",
+ "license": "by-sa",
+ "metadata": {
+ "author": {
+ "name": "ELMS:LN",
+ "image": "",
+ "socialLink": "https://twitter.com/elmsln",
+ "email": "hax@psu.edu"
+ },
+ "site": {
+ "name": "haxtheweb",
+ "created": 1547138719,
+ "updated": 1726516452,
+ "domain": "https://haxtheweb.org/",
+ "git": {
+ "vendor": "github",
+ "branch": "master",
+ "staticBranch": "gh-pages",
+ "url": "git@github.com:elmsln/haxtheweb.org.git",
+ "autoPush": false,
+ "publicRepoUrl": "https://github.com/elmsln/haxtheweb.org/tree/master/"
+ },
+ "static": {
+ "cdn": "",
+ "lastPublished": 1617979997,
+ "publishedLocation": "https://haxtheweb.org/",
+ "offline": false
+ },
+ "settings": {
+ "pathauto": false,
+ "publishPagesOn": true,
+ "sw": false,
+ "forceUpgrade": false,
+ "gaID": null
+ },
+ "version": "9.0.5",
+ "logo": "files/3450183.png",
+ "tags": null
+ },
+ "theme": {
+ "element": "clean-two",
+ "path": "@haxtheweb/clean-two/clean-two.js",
+ "name": "Clean two theme",
+ "thumbnail": "build/es6/node_modules/@haxtheweb/app-hax/lib/assets/images/PartyStyle.svg",
+ "variables": {
+ "image": "assets/banner.jpg",
+ "imageAlt": null,
+ "imageLink": null,
+ "hexCode": "#009dc7",
+ "cssVariable": "--simple-colors-default-theme-purple-7",
+ "icon": "lrn:network"
+ },
+ "regions": {}
+ },
+ "node": {
+ "dynamicElementLoader": {
+ "h5p-element": "@lrnwebcomponents/h5p-element/h5p-element.js",
+ "hax-logo": "@lrnwebcomponents/hax-logo/hax-logo.js",
+ "a11y-gif-player": "@lrnwebcomponents/a11y-gif-player/a11y-gif-player.js",
+ "code-sample": "@lrnwebcomponents/code-sample/code-sample.js",
+ "citation-element": "@lrnwebcomponents/citation-element/citation-element.js",
+ "hero-banner": "@lrnwebcomponents/hero-banner/hero-banner.js",
+ "image-compare-slider": "@lrnwebcomponents/image-compare-slider/image-compare-slider.js",
+ "license-element": "@lrnwebcomponents/license-element/license-element.js",
+ "lrn-aside": "@lrnwebcomponents/lrn-aside/lrn-aside.js",
+ "lrn-math": "@lrnwebcomponents/lrn-math/lrn-math.js",
+ "lrn-table": "@lrnwebcomponents/lrn-table/lrn-table.js",
+ "lrn-vocab": "@lrnwebcomponents/lrn-vocab/lrn-vocab.js",
+ "lrndesign-blockquote": "@lrnwebcomponents/lrndesign-blockquote/lrndesign-blockquote.js",
+ "magazine-cover": "@lrnwebcomponents/magazine-cover/magazine-cover.js",
+ "media-behaviors": "@lrnwebcomponents/media-behaviors/media-behaviors.js",
+ "media-image": "@lrnwebcomponents/media-image/media-image.js",
+ "meme-maker": "@lrnwebcomponents/meme-maker/meme-maker.js",
+ "grid-plate": "@lrnwebcomponents/grid-plate/grid-plate.js",
+ "md-block": "@lrnwebcomponents/md-block/md-block.js",
+ "multiple-choice": "@lrnwebcomponents/multiple-choice/multiple-choice.js",
+ "paper-audio-player": "@lrnwebcomponents/paper-audio-player/paper-audio-player.js",
+ "person-testimonial": "@lrnwebcomponents/person-testimonial/person-testimonial.js",
+ "place-holder": "@lrnwebcomponents/place-holder/place-holder.js",
+ "q-r": "@lrnwebcomponents/q-r/q-r.js",
+ "full-width-image": "@lrnwebcomponents/full-width-image/full-width-image.js",
+ "self-check": "@lrnwebcomponents/self-check/self-check.js",
+ "simple-concept-network": "@lrnwebcomponents/simple-concept-network/simple-concept-network.js",
+ "stop-note": "@lrnwebcomponents/stop-note/stop-note.js",
+ "tab-list": "@lrnwebcomponents/tab-list/tab-list.js",
+ "task-list": "@lrnwebcomponents/task-list/task-list.js",
+ "video-player": "@lrnwebcomponents/video-player/video-player.js",
+ "wave-player": "@lrnwebcomponents/wave-player/wave-player.js",
+ "wikipedia-query": "@lrnwebcomponents/wikipedia-query/wikipedia-query.js",
+ "lrndesign-gallery": "@lrnwebcomponents/lrndesign-gallery/lrndesign-gallery.js",
+ "lrndesign-timeline": "@lrnwebcomponents/lrndesign-timeline/lrndesign-timeline.js",
+ "html-block": "@lrnwebcomponents/html-block/html-block.js",
+ "user-action": "@lrnwebcomponents/user-action/user-action.js",
+ "rss-items": "@lrnwebcomponents/rss-items/rss-items.js"
+ },
+ "fields": {}
+ }
+ },
+ "items": [
+ {
+ "id": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "indent": "1",
+ "location": "pages/documentation-1/hax-development/index.html",
+ "slug": "documentation-1/hax-development",
+ "order": "0",
+ "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "title": "HAX development",
+ "description": "Include HAX in your projectThe developers docs will lay out the many specifications that make HAX possible including core concepts, different schema's it leverages ad how to define app store spec in ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-587de126-437b-4864-a3ea-54078837127c",
+ "indent": "1",
+ "location": "pages/item-587de126-437b-4864-a3ea-54078837127c/index.html",
+ "slug": "integrations-1/hax11ty",
+ "order": "0",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "HAX11ty",
+ "description": "HAX + 11ty = HAX11ty! HAX11ty gives you the best of SEO from 11ty while using the HAX editor and the HAXcms theme engine for presenting material. This gives you the SPA capabilities of fast loading r",
+ "metadata": {
+ "created": 1597690877,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 4,
+ "schema": [
+ {
+ "resource": "#d8a4a0fc-7cf5-800c-41cd-cdae27ae49c4",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 4,
+ "video-player": 1
+ },
+ "elements": 5
+ }
+ }
+ },
+ {
+ "id": "item-36c4fc60-67c0-43c2-8f71-c6a117e8b7d6",
+ "indent": "4",
+ "location": "pages/documentation-1/haxcms/theming/core-elements/query-examples/index.html",
+ "slug": "documentation-1/haxcms/theming/core-elements/query-examples",
+ "order": "0",
+ "parent": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550",
+ "title": "Query examples",
+ "description": " Hold up there. You didn't cover any of the query tags in that last section!Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that n",
+ "metadata": {
+ "created": 1553349518,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/2019-03-23_10-51-10.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/2019-03-23_10-51-10.jpg",
+ "url": "files/2019-03-23_10-51-10.jpg",
+ "type": "image/jpeg",
+ "name": "2019-03-23_10-51-10.jpg",
+ "size": 54637
+ }
+ ]
+ }
+ },
+ {
+ "id": "item-asd7dab5-8208-65e3-c3e4-267f233f60553",
+ "indent": "1",
+ "location": "pages/welcome/what-is-hax/index.html",
+ "slug": "welcome/what-is-hax",
+ "order": "0",
+ "parent": "item-welcome",
+ "title": "What is HAX",
+ "description": "HAX - Headless Authoring eXperienceHAX is a WYSIWYG unlike any other. You extend your world by extending the web through the web component standard. HAX has a simple schema and integrations to allow",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files//sourceviewthispage.jpg",
+ "fullUrl": "/sites/haxtheweb/files/sourceviewthispage.jpg",
+ "url": "files/sourceviewthispage.jpg",
+ "type": "image/jpeg",
+ "name": "sourceviewthispage.jpg",
+ "size": 34616
+ }
+ ],
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 4,
+ "paragraphs": 8,
+ "schema": [],
+ "tags": {
+ "full-width-image": 1,
+ "h2": 4,
+ "p": 8,
+ "code-sample": 1,
+ "meme-maker": 1,
+ "ul": 1,
+ "img": 1
+ },
+ "elements": 17
+ }
+ }
+ },
+ {
+ "id": "item-692eb91c-4003-3429-5d9f-caac64691849",
+ "indent": "2",
+ "location": "pages/documentation-1/hax-development/wcfactory-tooling/index.html",
+ "slug": "documentation-1/hax-development/wcfactory-tooling",
+ "order": "0",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "WCFactory Tooling",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-welcome",
+ "indent": 0,
+ "location": "pages/welcome/index.html",
+ "slug": "welcome",
+ "order": 0,
+ "parent": null,
+ "title": "Our Mission",
+ "description": "We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless offfff ability, platform,tribe or income",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1661452015,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/demo.csv",
+ "fullUrl": "/_sites/haxtheweb/files/demo.csv",
+ "url": "files/demo.csv",
+ "type": "text/plain",
+ "name": "demo.csv",
+ "size": 830
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/demo.csv",
+ "fullUrl": "/_sites/haxtheweb/files/demo.csv",
+ "url": "files/demo.csv",
+ "type": "text/plain",
+ "name": "demo.csv",
+ "size": 830
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/ngdle.png",
+ "fullUrl": "/_sites/haxtheweb/files/ngdle.png",
+ "url": "files/ngdle.png",
+ "type": "image/png",
+ "name": "ngdle.png",
+ "size": 307196
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 2,
+ "paragraphs": 6,
+ "schema": [
+ {
+ "resource": "#13f8e41a-3150-15b2-162c-327f1132477f",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ },
+ {
+ "resource": "#18d556e9-a1d7-3069-81d9",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "page-break": 1,
+ "p": 6,
+ "grid-plate": 1,
+ "video-player": 1,
+ "code-sample": 1,
+ "h3": 2,
+ "ul": 1
+ },
+ "elements": 13
+ },
+ "published": true,
+ "locked": false
+ }
+ },
+ {
+ "id": "item-96d00871-d866-c65e-b7f0-4e242bde5b15",
+ "indent": "3",
+ "location": "pages/documentation-1/hax-development/hax-app-store/apps/index.html",
+ "slug": "documentation-1/hax-development/hax-app-store/apps",
+ "order": "0",
+ "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755",
+ "title": "apps",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-f0af8879-a79c-4d1c-afc4-e23c32f52dc4",
+ "indent": "3",
+ "location": "pages/documentation-1/haxcms/theming/css-vars/index.html",
+ "slug": "documentation-1/haxcms/theming/css-vars",
+ "order": "0",
+ "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "title": "CSS vars",
+ "description": "CSS can be modified via CSS variables. CSS variables create a happy middle ground between the constraints of Shadow DOM (namely that styles are fully encapsulated) and designers wanting flexibility a",
+ "metadata": {
+ "created": 1553349518,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-dfd62788-ba48-4051-a869-986e5956864f",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/concepts/index.html",
+ "slug": "documentation-1/haxcms/concepts",
+ "order": "0",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Concepts",
+ "description": "HAXcms seeks to be a microsite generator and manager that doesn't require any command line in order to operate. HAXcms leverages HAX to give a best in class authoring experience while HAXcms seeks to",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-e3dafe1a-1f50-1834-68f3-9f378e4ddda5",
+ "indent": "2",
+ "location": "pages/documentation-1/ux-concepts/add/index.html",
+ "slug": "documentation-1/ux-concepts/add",
+ "order": "0",
+ "parent": "item-06233713-d866-3351-81da-841d3931144c",
+ "title": "Add Content",
+ "description": "Add Content is how you create and add complex blocks to the HAX page editor. These blocks can be variable based on what you chose to include (see appstore) but ultimately are just adding web compon",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-34-32.png",
+ "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-34-32.png",
+ "url": "files/Screenshot from 2020-08-17 14-34-32.png",
+ "type": "image/png",
+ "name": "Screenshot from 2020-08-17 14-34-32.png",
+ "size": 78391
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "img": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-275a0928-60ab-b7ce-c2b6-d0e35826498b",
+ "indent": "1",
+ "location": "pages/documentation-1/core-concepts/index.html",
+ "slug": "documentation-1/core-concepts",
+ "order": "1",
+ "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "title": "Core concepts",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-39074718-758f-d51b-1dc5-15cfbb79e44c",
+ "indent": "2",
+ "location": "pages/documentation-1/hax-development/hello-world-element/index.html",
+ "slug": "documentation-1/hax-development/hello-world-element",
+ "order": "1",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "hello-world element",
+ "description": "Let's see what goes into the element called @lrnwebcomponents/example-hax-element in order to learn how we can wire anything up to HAXeditor.@lrnwebcomponents/example-hax-element/example-hax-elem",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617806663,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "h2": 1,
+ "code-sample": 1
+ },
+ "elements": 3
+ }
+ }
+ },
+ {
+ "id": "item-650eaa59-478c-4674-8ef3-93e4b43e2310",
+ "indent": "1",
+ "location": "pages/welcome/why-haxcms-1/index.html",
+ "slug": "welcome/why-haxcms-1",
+ "order": "1",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "HAXcms",
+ "description": "HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web ",
+ "metadata": {
+ "created": 1563972322,
+ "updated": 1617805490,
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 6,
+ "paragraphs": 5,
+ "schema": [
+ {
+ "typeof": "oer:Assessment",
+ "resource": "#dd2feacf-ed4a-dcb0-b85d",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "grid-plate": 1,
+ "h2": 2,
+ "ul": 3,
+ "p": 5,
+ "h4": 4,
+ "img": 1,
+ "multiple-choice": 1
+ },
+ "elements": 17
+ }
+ }
+ },
+ {
+ "id": "item-5a6e6643-3834-4ac5-ae70-0090263759cb",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/installation/index.html",
+ "slug": "documentation-1/haxcms/installation",
+ "order": "1",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Installation",
+ "description": "Generic PHP install directionsHave PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is ",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/mampstructure.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/mampstructure.jpg",
+ "url": "files/mampstructure.jpg",
+ "type": "image/jpeg",
+ "name": "mampstructure.jpg",
+ "size": 15099
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/mampstart.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/mampstart.jpg",
+ "url": "files/mampstart.jpg",
+ "type": "image/jpeg",
+ "name": "mampstart.jpg",
+ "size": 12670
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/mamppage.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/mamppage.jpg",
+ "url": "files/mamppage.jpg",
+ "type": "image/jpeg",
+ "name": "mamppage.jpg",
+ "size": 17086
+ }
+ ],
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 6,
+ "paragraphs": 13,
+ "schema": [
+ {
+ "resource": "#990ebe5c-04c8-58b2-385a",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ },
+ {
+ "resource": "#4e5cac2b-786f-596c-b394",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "h2": 4,
+ "p": 13,
+ "code-sample": 2,
+ "h3": 2,
+ "media-image": 2,
+ "img": 1,
+ "ul": 1
+ },
+ "elements": 25
+ }
+ }
+ },
+ {
+ "id": "item-a91393ea-31f8-30bd-888f-275a05e08e0a",
+ "indent": "3",
+ "location": "pages/documentation-1/hax-development/hax-app-store/blox/index.html",
+ "slug": "documentation-1/hax-development/hax-app-store/blox",
+ "order": "1",
+ "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755",
+ "title": "blox",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-504d6323-873d-49e3-9de0-ffa56c28fdf5",
+ "indent": "1",
+ "location": "pages/get-involved-1/index.html",
+ "slug": "get-involved-1",
+ "order": "1",
+ "parent": "item-welcome",
+ "title": "Get Involved!",
+ "description": "Join our communityJoin us on the HAXTheWeb Slack channelJoin us for HAXcamp Un-code every Friday 3 pm - 5 pm (EST)Follow / use the #HAXTheWeb hash tagJoin our projectsHAXcms - That which ",
+ "metadata": {
+ "created": 1553197584,
+ "updated": 1617805490,
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 3,
+ "paragraphs": 6,
+ "schema": [],
+ "tags": {
+ "h2": 3,
+ "ul": 3,
+ "p": 6,
+ "meme-maker": 1
+ },
+ "elements": 13
+ }
+ }
+ },
+ {
+ "id": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "indent": 0,
+ "location": "pages/integrations-1/index.html",
+ "slug": "integrations-1",
+ "order": "1",
+ "parent": null,
+ "title": "Integrations",
+ "description": "HAX provides plenty of ways to integrate into the platforms you already use! Here are some of the plugins and integrations below this heading.Some things a liittle bit crazyCode Pen?!Demonstration",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "h2": 1,
+ "ul": 1
+ },
+ "elements": 3
+ }
+ }
+ },
+ {
+ "id": "item-3859b3ac-1ef5-45b4-909c-3892f97a9f4c",
+ "indent": "3",
+ "location": "pages/documentation-1/haxcms/theming/skin-a-site/index.html",
+ "slug": "documentation-1/haxcms/theming/skin-a-site",
+ "order": "1",
+ "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "title": "Skin a site",
+ "description": "Theme skinning is the easiest way to build a decent looking theme in HAXcms. This method is geared toward people that know CSS and HTML but can't get into the weeds of web components or javascript.Wo",
+ "metadata": {
+ "created": 1553354507,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-eca7c8a4-393a-4e68-8cb4-440e94683738",
+ "indent": "2",
+ "location": "pages/item-eca7c8a4-393a-4e68-8cb4-440e94683738/index.html",
+ "slug": "documentation-1/ux-concepts/block-settings",
+ "order": "1",
+ "parent": "item-06233713-d866-3351-81da-841d3931144c",
+ "title": "Block settings",
+ "description": "Block settings will change contextually based on which block has been selected in the editable area of the page. In this screenshot, a paragraph has been selected and so the icon associated with it is",
+ "metadata": {
+ "created": 1597689709,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-42-07.png",
+ "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-42-07.png",
+ "url": "files/Screenshot from 2020-08-17 14-42-07.png",
+ "type": "image/png",
+ "name": "Screenshot from 2020-08-17 14-42-07.png",
+ "size": 46191
+ },
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-46-06.png",
+ "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-46-06.png",
+ "url": "files/Screenshot from 2020-08-17 14-46-06.png",
+ "type": "image/png",
+ "name": "Screenshot from 2020-08-17 14-46-06.png",
+ "size": 66054
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 2,
+ "paragraphs": 2,
+ "schema": [],
+ "tags": {
+ "p": 2,
+ "h2": 2,
+ "img": 2
+ },
+ "elements": 6
+ }
+ }
+ },
+ {
+ "id": "item-44a138ea-5122-4a2b-b2ce-8bf1fb11bb29",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/structure/index.html",
+ "slug": "documentation-1/haxcms/structure",
+ "order": "2",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Structure",
+ "description": "By design we've got a very simple structure. The goal of HAXcms isn't to lock you into anything and so we've simplified our file structure over other solutions.The key directories / files include:fi",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/2019-02-20_01-26-01.png",
+ "fullUrl": "/_sites/haxtheweb/files/2019-02-20_01-26-01.png",
+ "url": "files/2019-02-20_01-26-01.png",
+ "type": "image/png",
+ "name": "2019-02-20_01-26-01.png",
+ "size": 19448
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/2019-02-20_01-26-10.png",
+ "fullUrl": "/_sites/haxtheweb/files/2019-02-20_01-26-10.png",
+ "url": "files/2019-02-20_01-26-10.png",
+ "type": "image/png",
+ "name": "2019-02-20_01-26-10.png",
+ "size": 59026
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/2019-02-25_16-22-25.png",
+ "fullUrl": "/_sites/haxtheweb/files/2019-02-25_16-22-25.png",
+ "url": "files/2019-02-25_16-22-25.png",
+ "type": "image/png",
+ "name": "2019-02-25_16-22-25.png",
+ "size": 37234
+ }
+ ]
+ }
+ },
+ {
+ "id": "item-f1c8e3a4-eddb-806a-8a3a-206c1e33f7a9",
+ "indent": "2",
+ "location": "pages/documentation-1/hax-development/hax-schema/index.html",
+ "slug": "documentation-1/hax-development/hax-schema",
+ "order": "2",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "HAX schema",
+ "description": "Implementing HAXSchemaIn order for your element to talk to the HAX editor, you need to implement static get haxProperties() on your element. This callback either returns a String based location of ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617979979,
+ "readtime": 5,
+ "contentDetails": {
+ "headings": 6,
+ "paragraphs": 7,
+ "schema": [],
+ "tags": {
+ "h2": 5,
+ "p": 7,
+ "ul": 1,
+ "code-sample": 5,
+ "h3": 1,
+ "grid-plate": 1,
+ "img": 3
+ },
+ "elements": 23
+ }
+ }
+ },
+ {
+ "id": "item-29e7d7f5-db3e-3ef0-733a-ed41d88f2835",
+ "indent": "1",
+ "location": "pages/welcome/solutions/index.html",
+ "slug": "welcome/solutions",
+ "order": "2",
+ "parent": "item-welcome",
+ "title": "Solutions",
+ "description": "Modularity is key to HAX success. Here are some of the solutions that HAX provides which leverage the HAXeditor interface.HAX editorHAX or HAXeditor is the editor of the future you're using in this ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 4,
+ "paragraphs": 9,
+ "schema": [
+ {
+ "resource": "#832335f3-7442-7d40-0d56",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 9,
+ "h2": 3,
+ "h3": 1,
+ "media-image": 1
+ },
+ "elements": 14
+ },
+ "published": true
+ }
+ },
+ {
+ "id": "item-17449951-7504-468a-b315-4388b85c00e3",
+ "indent": "3",
+ "location": "pages/documentation-1/haxcms/theming/web-components/index.html",
+ "slug": "documentation-1/haxcms/theming/web-components",
+ "order": "2",
+ "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "title": "Web components",
+ "description": "Do you know full on web component development? Well, you can build a new theme from scratch. The best way to learn is by picking a part some of our examples. For this we'll analyze the haxcms-slide-th",
+ "metadata": {
+ "created": 1553349518,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-5a9ea17e-63ce-96f3-e94f-d5282b290661",
+ "indent": "1",
+ "location": "pages/integrations-1/wordpress/index.html",
+ "slug": "integrations-1/wordpress",
+ "order": "2",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "WordPress",
+ "description": "We support WordPress too! In order to use HAX though you'll want to replace the Gutenberg editor. The following steps will help you get it up and running.Get the Classic Editor. This plugin helps re",
+ "metadata": {
+ "created": 1549428503,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "ol": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "indent": 0,
+ "location": "pages/documentation-1/index.html",
+ "slug": "documentation-1",
+ "order": 2,
+ "parent": null,
+ "title": "Documentation",
+ "description": "HAX may seem complex, but it's built on a series of standards that will never break. As a result of the complexity of these standards, there are things you should know prior to digging into HAXedit",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1661452038,
+ "readtime": 1,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/3450183.png",
+ "fullUrl": "/sites/haxtheweb/files/3450183.png",
+ "url": "files/3450183.png",
+ "type": "image/png",
+ "name": "3450183.png",
+ "size": 9992
+ }
+ ],
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 3,
+ "schema": [
+ {
+ "resource": "#4e04ff57-98de-f227-681f-d3425ba60f04",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "page-break": 1,
+ "p": 3,
+ "h3": 1,
+ "grid-plate": 1
+ },
+ "elements": 6
+ },
+ "published": true,
+ "locked": false
+ }
+ },
+ {
+ "id": "item-faaa1198-10c7-ff30-ece6-01b30a9c0f85",
+ "indent": "3",
+ "location": "pages/documentation-1/hax-development/hax-app-store/stax/index.html",
+ "slug": "documentation-1/hax-development/hax-app-store/stax",
+ "order": "2",
+ "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755",
+ "title": "stax",
+ "description": "Stax are what most WYSIWYG systems would call Templates. Stax in HAX are a series of HAX element schema's in succession.Below is a definition for the \"example lesson\" seen above. This is a larger ex",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 4
+ }
+ },
+ {
+ "id": "item-251f207e-4046-a4b0-40ce-7c28fe38ae23",
+ "indent": "2",
+ "location": "pages/documentation-1/ux-concepts/find/index.html",
+ "slug": "documentation-1/ux-concepts/find",
+ "order": "2",
+ "parent": "item-06233713-d866-3351-81da-841d3931144c",
+ "title": "Search",
+ "description": "Search is a data interoperability layer to HAX where web components data binding shines. Search is able to stitch remote data together with local web components in order to streamline workflows. You ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "published": true,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-36-15.png",
+ "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-36-15.png",
+ "url": "files/Screenshot from 2020-08-17 14-36-15.png",
+ "type": "image/png",
+ "name": "Screenshot from 2020-08-17 14-36-15.png",
+ "size": 135869
+ },
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-43-47.png",
+ "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-43-47.png",
+ "url": "files/Screenshot from 2020-08-17 14-43-47.png",
+ "type": "image/png",
+ "name": "Screenshot from 2020-08-17 14-43-47.png",
+ "size": 105778
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "img": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-06233713-d866-3351-81da-841d3931144c",
+ "indent": "1",
+ "location": "pages/documentation-1/ux-concepts/index.html",
+ "slug": "documentation-1/ux-concepts",
+ "order": "2",
+ "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "title": "UX concepts",
+ "description": "The HAX UI can be broken down into three major production concepts. Content authors are either:Adding something they already haveEditing the Settings of the activated element on the pageSearch for ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "ol": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-0e4cc53c-944f-658a-5440-eacc5a1c0358",
+ "indent": "1",
+ "location": "pages/documentation-1/related-technologies/index.html",
+ "slug": "documentation-1/related-technologies",
+ "order": "3",
+ "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "title": "Related technologies",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-a839d5c1-3321-a395-c032-4ea8ea2cfa27",
+ "indent": "3",
+ "location": "pages/documentation-1/hax-development/hax-app-store/autoloader/index.html",
+ "slug": "documentation-1/hax-development/hax-app-store/autoloader",
+ "order": "3",
+ "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755",
+ "title": "autoloader",
+ "description": "Autoloader is waaayyy easier to implement then the other parts of the appstore spec and is probably the most important as it loads all the elements that will be available to your users. All it is is a",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617979603,
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 4,
+ "paragraphs": 5,
+ "schema": [],
+ "tags": {
+ "p": 5,
+ "ol": 1,
+ "h3": 1,
+ "code-sample": 1,
+ "h4": 3
+ },
+ "elements": 11
+ }
+ }
+ },
+ {
+ "id": "item-aa589faa-e860-4221-82fa-df6d57328ac2",
+ "indent": "2",
+ "location": "pages/item-aa589faa-e860-4221-82fa-df6d57328ac2/index.html",
+ "slug": "documentation-1/ux-concepts/templates-and-layouts",
+ "order": "3",
+ "parent": "item-06233713-d866-3351-81da-841d3931144c",
+ "title": "Templates and Layouts",
+ "description": "Templates and layouts allow you to drop in pre-built pieces of content structure. This might be a series of images or an example of content that could be written.",
+ "metadata": {
+ "created": 1597689709,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [],
+ "tags": {
+ "p": 1,
+ "img": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550",
+ "indent": "3",
+ "location": "pages/documentation-1/haxcms/theming/core-elements/index.html",
+ "slug": "documentation-1/haxcms/theming/core-elements",
+ "order": "3",
+ "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "title": "Core elements",
+ "description": "While you're not required to use them, HAXcms supplies a series of elements that can make theme development effortless. You can see the source of these in greater detail under the theme directory of h",
+ "metadata": {
+ "created": 1552437937,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/2019-03-12_16-45-51.png",
+ "fullUrl": "/_sites/haxtheweb/files/2019-03-12_16-45-51.png",
+ "url": "files/2019-03-12_16-45-51.png",
+ "type": "image/png",
+ "name": "2019-03-12_16-45-51.png",
+ "size": 212153
+ }
+ ]
+ }
+ },
+ {
+ "id": "item-49d727fb-b5c8-871a-3979-a5143116946d",
+ "indent": 0,
+ "location": "pages/f-a-q-1/index.html",
+ "slug": "f-a-q-1",
+ "order": 3,
+ "parent": null,
+ "title": "F.A.Q.",
+ "description": "Are web components ready for prime time?Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor leverages this approach and standardizes its usage in order to ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1661452776,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/pubwork1.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/pubwork1.jpg",
+ "url": "files/pubwork1.jpg",
+ "type": "image/jpeg",
+ "name": "pubwork1.jpg",
+ "size": 51662
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/IMG_20190127_153429.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/IMG_20190127_153429.jpg",
+ "url": "files/IMG_20190127_153429.jpg",
+ "type": "image/jpeg",
+ "name": "IMG_20190127_153429.jpg",
+ "size": 27242
+ }
+ ],
+ "readtime": 5,
+ "contentDetails": {
+ "headings": 6,
+ "paragraphs": 11,
+ "schema": [
+ {
+ "resource": "#4afe6e57-7d57-53d4-cca3-2512c120ffcc",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "page-break": 1,
+ "h2": 6,
+ "p": 11,
+ "ul": 3
+ },
+ "elements": 21
+ },
+ "published": true,
+ "locked": false
+ }
+ },
+ {
+ "id": "item-ca8c6ba8-c012-8ace-343a-3701f20609e9",
+ "indent": "1",
+ "location": "pages/integrations-1/drupal/index.html",
+ "slug": "integrations-1/drupal",
+ "order": "3",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "Drupal",
+ "description": "Try on SimplyTest.meTry HAX on Simplytest me in a few steps without needing to install anythingGo to Simplytest me and pick HAX modulePick 9.x,8.x or 7.xLog in, go to Administration -> Configurat",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/scale-50/d8cdnimage.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/scale-50/d8cdnimage.jpg",
+ "url": "files/scale-50/d8cdnimage.jpg",
+ "type": "image/jpeg",
+ "name": "d8cdnimage.jpg",
+ "size": 136928
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/scale-50/haxd8simply.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/scale-50/haxd8simply.jpg",
+ "url": "files/scale-50/haxd8simply.jpg",
+ "type": "image/jpeg",
+ "name": "haxd8simply.jpg",
+ "size": 91967
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 3,
+ "paragraphs": 3,
+ "schema": [
+ {
+ "resource": "#3b994c7f-952f-e85f-48b3",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "h2": 2,
+ "p": 3,
+ "ol": 2,
+ "grid-plate": 1,
+ "h3": 1,
+ "wikipedia-query": 1
+ },
+ "elements": 10
+ }
+ }
+ },
+ {
+ "id": "item-01e0f49a-190a-4c8d-ae0e-83d62675e070",
+ "indent": "1",
+ "location": "pages/welcome/roadmap-1/index.html",
+ "slug": "welcome/roadmap-1",
+ "order": "3",
+ "parent": "item-welcome",
+ "title": "Roadmap",
+ "description": "HAX encompasses many different projectsThis roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements a",
+ "metadata": {
+ "created": 1565290387,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/sites/haxtheweb/files//haxrelationships.jpg",
+ "fullUrl": "/sites/haxtheweb/files/haxrelationships.jpg",
+ "url": "files/haxrelationships.jpg",
+ "type": "image/jpeg",
+ "name": "haxrelationships.jpg",
+ "size": 88416
+ },
+ {
+ "path": "/var/www/html/sites/haxtheweb/files//Roadmap.jpg",
+ "fullUrl": "/sites/haxtheweb/files/Roadmap.jpg",
+ "url": "files/Roadmap.jpg",
+ "type": "image/jpeg",
+ "name": "Roadmap.jpg",
+ "size": 108725
+ },
+ {
+ "path": "/var/www/html/sites/haxtheweb/files/headshot272229.61999999825.jpg",
+ "fullUrl": "/sites/haxtheweb/files/headshot272229.61999999825.jpg",
+ "url": "files/headshot272229.61999999825.jpg",
+ "type": "image/jpeg",
+ "name": "headshot272229.61999999825.jpg",
+ "size": 121898
+ }
+ ],
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 2,
+ "paragraphs": 6,
+ "schema": [],
+ "tags": {
+ "h3": 2,
+ "p": 6,
+ "img": 2
+ },
+ "elements": 10
+ }
+ }
+ },
+ {
+ "id": "item-5df45272-f6b9-4f4f-b650-16c47aeac6fb",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/publishing/index.html",
+ "slug": "documentation-1/haxcms/publishing",
+ "order": "3",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Publishing",
+ "description": "HAXcms requires being published in order to be visible to other people. Working locally or on Desktop or on a server, is akin to you writing a document on your computer. It's not shared with anyone. W",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/gitpublishingdata.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/gitpublishingdata.jpg",
+ "url": "files/gitpublishingdata.jpg",
+ "type": "image/jpeg",
+ "name": "gitpublishingdata.jpg",
+ "size": 12847
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/pubwork1.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/pubwork1.jpg",
+ "url": "files/pubwork1.jpg",
+ "type": "image/jpeg",
+ "name": "pubwork1.jpg",
+ "size": 51662
+ },
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/pubwork2.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/pubwork2.jpg",
+ "url": "files/pubwork2.jpg",
+ "type": "image/jpeg",
+ "name": "pubwork2.jpg",
+ "size": 70772
+ }
+ ]
+ }
+ },
+ {
+ "id": "item-44cc230b-07db-442a-90cf-687e2d089a5d",
+ "indent": "2",
+ "location": "pages/item-44cc230b-07db-442a-90cf-687e2d089a5d/index.html",
+ "slug": "haxhooks",
+ "order": "3",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "haxHooks",
+ "description": "Elements can integrate deeply into HAX state management using what we call \"hax hooks\". By supplying a method on your web component like haxHooks() you are magically able to tap into different li",
+ "metadata": {
+ "created": 1617802345,
+ "updated": 1617805490,
+ "readtime": 5,
+ "contentDetails": {
+ "headings": 10,
+ "paragraphs": 11,
+ "schema": [],
+ "tags": {
+ "p": 11,
+ "h2": 2,
+ "ul": 2,
+ "code-sample": 1,
+ "h3": 8
+ },
+ "elements": 24
+ }
+ }
+ },
+ {
+ "id": "item-c86470aa-0295-4c9d-9f17-48ad79ab05be",
+ "indent": "1",
+ "location": "pages/welcome/presentations/index.html",
+ "slug": "welcome/presentations",
+ "order": "4",
+ "parent": "item-welcome",
+ "title": "Presentations",
+ "description": "This is the youtube playlist of all things HAXTheWebThis playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists relat",
+ "metadata": {
+ "created": 1552910817,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 2,
+ "schema": [],
+ "tags": {
+ "p": 2,
+ "iframe": 1
+ },
+ "elements": 3
+ }
+ }
+ },
+ {
+ "id": "item-4824986b-1897-568d-fdd9-4b882ea6ee1f",
+ "indent": "1",
+ "location": "pages/integrations-1/backdropcms/index.html",
+ "slug": "integrations-1/backdropcms",
+ "order": "4",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "BackdropCMS",
+ "description": "Getting HAX setup in BackdropCMSSearch for HAX on BackdropCMS.org or from within your Backdrop siteFollow the instructions in the Web components module README for buildingDon't worry, HAX requ",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 1,
+ "schema": [
+ {
+ "resource": "#5b790bef-7d78-f85e-104d",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 1,
+ "h2": 1,
+ "ol": 1,
+ "media-image": 1
+ },
+ "elements": 4
+ }
+ }
+ },
+ {
+ "id": "item-7ab2e2fd-622f-4a0f-9967-599410c6cd43",
+ "indent": 0,
+ "location": "pages/scavenger-hunt-1/index.html",
+ "slug": "scavenger-hunt-1",
+ "order": "4",
+ "parent": null,
+ "title": "Scavenger Hunt",
+ "description": "Become part of our dynasty franchise **by wearing a cool jerseyWe're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next ev",
+ "metadata": {
+ "created": 1563970537,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 2,
+ "schema": [
+ {
+ "typeof": "oer:SupportingMaterial",
+ "resource": "#238ee75a-de4d-02a9-3755",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "h3": 1,
+ "p": 2,
+ "ul": 1,
+ "task-list": 1,
+ "meme-maker": 1
+ },
+ "elements": 6
+ }
+ }
+ },
+ {
+ "id": "item-7f3dd690-4c3f-4616-baa5-159b9a15809c",
+ "indent": "3",
+ "location": "pages/documentation-1/haxcms/theming/dev-workflows/index.html",
+ "slug": "documentation-1/haxcms/theming/dev-workflows",
+ "order": "4",
+ "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "title": "Dev workflows",
+ "description": "Our development workflow is as follows (for themes)All custom theme work happens in your _config directoryMake my-theme.js, pull everything together, either in this directory or in a wcfactory cat",
+ "metadata": {
+ "created": 1553349518,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-e6daa06e-dfd2-43a4-ade8-0c0ded24e0b4",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/life-cycle/index.html",
+ "slug": "documentation-1/haxcms/life-cycle",
+ "order": "4",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Life cycle",
+ "description": "This is a general life cycle that happens when HAXcms \"boots up\". When web components are unpacking the contents of what to do it generally will work this way.page load, should it be no-js or a web c",
+ "metadata": {
+ "created": 1554496047,
+ "updated": 1617805490,
+ "readtime": 3,
+ "contentDetails": {
+ "headings": 3,
+ "paragraphs": 5,
+ "schema": [],
+ "tags": {
+ "p": 5,
+ "ul": 3,
+ "h2": 1,
+ "code-sample": 1,
+ "h3": 2
+ },
+ "elements": 12
+ }
+ }
+ },
+ {
+ "id": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "indent": "1",
+ "location": "pages/documentation-1/haxcms/index.html",
+ "slug": "documentation-1/haxcms",
+ "order": "4",
+ "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d",
+ "title": "HAXcms",
+ "description": "HAXcms, that which powers the site you are currently reading is a powerful \"static site generator\" paradigm. It leverages server technology in order to orchestrate a static site. That way the \"server\"",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/HAXCms workflow.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/HAXCms workflow.jpg",
+ "url": "files/HAXCms workflow.jpg",
+ "type": "image/jpeg",
+ "name": "HAXCms workflow.jpg",
+ "size": 72736
+ }
+ ]
+ }
+ },
+ {
+ "id": "item-cdd303d0-4490-4433-94fa-0e78cf849e80",
+ "indent": "2",
+ "location": "pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html",
+ "slug": "documentation-1/hax-development/internationalization-i18n",
+ "order": "4",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "Internationalization - i18n",
+ "description": "We've created a way to internationalize ANY web component you create. Because this is a complex topic, and we seek to empower anyone, anywhere to work with web components; i18n is a critical piece of ",
+ "metadata": {
+ "created": 1617805490,
+ "updated": 1617806250,
+ "readtime": 2,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 3,
+ "schema": [],
+ "tags": {
+ "p": 3,
+ "a": 1,
+ "h3": 1,
+ "ul": 1,
+ "code-sample": 2
+ },
+ "elements": 8
+ }
+ }
+ },
+ {
+ "id": "item-52727dcf-a7d5-90e9-c459-a4a53dd07ffd",
+ "indent": "2",
+ "location": "pages/documentation-1/hax-development/hax-element-schema/index.html",
+ "slug": "documentation-1/hax-development/hax-element-schema",
+ "order": "5",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "HAX Element Schema",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-5dede24a-2de7-4fae-a00b-31e8121e3c16",
+ "indent": "1",
+ "location": "pages/welcome/i-have-issues/index.html",
+ "slug": "welcome/i-have-issues",
+ "order": "5",
+ "parent": "item-welcome",
+ "title": "I have issues",
+ "description": "You have a problem or would like to contribute to anything in our universe? That's awesome! All issues, feature requests and general thumbs up should happen in our issue queue on github: https://gith",
+ "metadata": {
+ "created": 1553556295,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 1,
+ "schema": [
+ {
+ "resource": "#b54c9847-4d26-90ae-d748",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 1,
+ "a11y-gif-player": 1
+ },
+ "elements": 2
+ }
+ }
+ },
+ {
+ "id": "item-677468f6-7bff-4bb6-bd2a-18520d88b3c4",
+ "indent": "1",
+ "location": "pages/integrations-1/classicpress-1/index.html",
+ "slug": "integrations-1/classicpress-1",
+ "order": "5",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "ClassicPress",
+ "description": "ClassicPress is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original!Get the HAX plugin from the wordpress registryGo to edit / create a page/post ",
+ "metadata": {
+ "created": 1565279009,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 1,
+ "paragraphs": 2,
+ "schema": [
+ {
+ "resource": "#85219ed3-d806-24d7-5c02",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 2,
+ "ol": 1,
+ "h2": 1,
+ "video-player": 1
+ },
+ "elements": 5
+ }
+ }
+ },
+ {
+ "id": "item-c7500902-9aed-4117-8949-a6597a02dada",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/troubleshooting/index.html",
+ "slug": "documentation-1/haxcms/troubleshooting",
+ "order": "5",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Troubleshooting",
+ "description": "These are some common issues / resolutions in HAXcms related to installation, publishing, etc.I installed HAXcms and forgot my passwordYour username and password can be found in _config/config.php o",
+ "metadata": {
+ "created": 1553555764,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-4de60a5f-98ab-a602-edfc-0cf024e83755",
+ "indent": "2",
+ "location": "pages/documentation-1/hax-development/hax-app-store/index.html",
+ "slug": "documentation-1/hax-development/hax-app-store",
+ "order": "6",
+ "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc",
+ "title": "HAX app store",
+ "description": "",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-897a9839-4ca3-a336-4795-afca7b6de0ee",
+ "indent": "1",
+ "location": "pages/integrations-1/gravcms/index.html",
+ "slug": "integrations-1/gravcms",
+ "order": "6",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "GravCMS",
+ "description": "There's two plugins needed to run HAX on GravCMS - The web components and HAX plugins.Web components plugin - provides the build routine and installation instructionsHAX plugin - editor capab",
+ "metadata": {
+ "created": 1548826475,
+ "updated": 1617805490,
+ "readtime": 1,
+ "contentDetails": {
+ "headings": 0,
+ "paragraphs": 2,
+ "schema": [
+ {
+ "resource": "#f0356db6-f345-316d-1426",
+ "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org "
+ }
+ ],
+ "tags": {
+ "p": 2,
+ "ul": 1,
+ "media-image": 1
+ },
+ "elements": 4
+ }
+ }
+ },
+ {
+ "id": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed",
+ "indent": "2",
+ "location": "pages/documentation-1/haxcms/theming/index.html",
+ "slug": "documentation-1/haxcms/theming",
+ "order": "6",
+ "parent": "item-4bce3546-4d53-4456-8eae-494c79180229",
+ "title": "Theming",
+ "description": "There are multiple ways to \"theme\" in HAXcms that align with the skillsets of the person doing the theme development. Know web components? Cool. Know basic CSS and HTML? Cool. Want to build something ",
+ "metadata": {
+ "created": 1550643005,
+ "updated": 1617805490
+ }
+ },
+ {
+ "id": "item-c5e61b84-e88a-5a48-29c6-5908117ec505",
+ "indent": "1",
+ "location": "pages/integrations-1/creating-new-ones/index.html",
+ "slug": "integrations-1/creating-new-ones",
+ "order": "7",
+ "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f",
+ "title": "Creating new ones!",
+ "description": "The main piece to our integrations is wrapped up in something we call \"The magic script\". The magic script is a standard way of dynamically discovering and importing the definitions of web components ",
+ "metadata": {
+ "created": 1548828434,
+ "updated": 1617805490,
+ "files": [
+ {
+ "path": "/var/www/html/_sites/haxtheweb/files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg",
+ "fullUrl": "/_sites/haxtheweb/files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg",
+ "url": "files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg",
+ "type": "image/jpeg",
+ "name": "59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg",
+ "size": 51809
+ }
+ ],
+ "readtime": 3,
+ "contentDetails": {
+ "headings": 3,
+ "paragraphs": 8,
+ "schema": [],
+ "tags": {
+ "p": 8,
+ "code-sample": 2,
+ "full-width-image": 1,
+ "h2": 3,
+ "ol": 1
+ },
+ "elements": 15
+ }
+ }
+ }
+ ]
+}
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/sitemap.xml b/github-pages-deploy-action-temp-deployment-folder/sitemap.xml
new file mode 100644
index 0000000..7c8b17b
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/sitemap.xml
@@ -0,0 +1,318 @@
+
+
+
+
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//item-587de126-437b-4864-a3ea-54078837127c
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/core-elements/query-examples
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/what-is-hax
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/wcfactory-tooling
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome
+ 2022-08-25T18:26:55+00:00
+ daily
+ 1.0
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-app-store/apps
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/css-vars
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/concepts
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/ux-concepts/add
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/core-concepts
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hello-world-element
+ 2021-04-07T14:44:23+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/why-haxcms-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/installation
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-app-store/blox
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//get-involved-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 1.0
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/skin-a-site
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//item-eca7c8a4-393a-4e68-8cb4-440e94683738
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/structure
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-schema
+ 2021-04-09T14:52:59+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/solutions
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/web-components
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/wordpress
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1
+ 2022-08-25T18:27:18+00:00
+ daily
+ 1.0
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-app-store/stax
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/ux-concepts/find
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/ux-concepts
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/related-technologies
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-app-store/autoloader
+ 2021-04-09T14:46:43+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//item-aa589faa-e860-4221-82fa-df6d57328ac2
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/core-elements
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//f-a-q-1
+ 2022-08-25T18:39:36+00:00
+ daily
+ 1.0
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/drupal
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/roadmap-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/publishing
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//item-44cc230b-07db-442a-90cf-687e2d089a5d
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/presentations
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/backdropcms
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//scavenger-hunt-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 1.0
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming/dev-workflows
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/life-cycle
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//item-cdd303d0-4490-4433-94fa-0e78cf849e80
+ 2021-04-07T14:37:30+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-element-schema
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//welcome/i-have-issues
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/classicpress-1
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/troubleshooting
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development/hax-app-store
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/gravcms
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
+ https://haxtheweb.org/https://haxtheweb.org//documentation-1/haxcms/theming
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.7
+
+
+ https://haxtheweb.org/https://haxtheweb.org//integrations-1/creating-new-ones
+ 2021-04-07T14:24:50+00:00
+ daily
+ 0.5
+
+
diff --git a/github-pages-deploy-action-temp-deployment-folder/sitemap.xml.gz b/github-pages-deploy-action-temp-deployment-folder/sitemap.xml.gz
new file mode 100644
index 0000000..6b3e093
Binary files /dev/null and b/github-pages-deploy-action-temp-deployment-folder/sitemap.xml.gz differ
diff --git a/github-pages-deploy-action-temp-deployment-folder/theme/._.DS_Store b/github-pages-deploy-action-temp-deployment-folder/theme/._.DS_Store
new file mode 100644
index 0000000..9ad849c
Binary files /dev/null and b/github-pages-deploy-action-temp-deployment-folder/theme/._.DS_Store differ
diff --git a/github-pages-deploy-action-temp-deployment-folder/theme/theme.css b/github-pages-deploy-action-temp-deployment-folder/theme/theme.css
new file mode 100644
index 0000000..176ba5d
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/theme/theme.css
@@ -0,0 +1,13 @@
+/**
+ * This is a custom theme css file. You can write whatever you want here
+ * but realize you'll need to play by the rules of shadow dom. Meaning,
+ * that if something is in a shadow root you won't be able to style it.
+ *
+ * There is hope though. We leverage CSS variables heavily and most of the
+ * elements we have baked in do too.
+ *
+ * Also since our themes are built on Polymer, you can leverage what
+ * are called "apply blocks". The apply block loos like @apply --whatever-stuff;
+ * Think of it like a sass mixin, where you can apply any css you want
+ * inside of that block and it'll apply downstream. Two examples are given below
+ */
diff --git a/github-pages-deploy-action-temp-deployment-folder/theme/theme.html b/github-pages-deploy-action-temp-deployment-folder/theme/theme.html
new file mode 100644
index 0000000..2e510ab
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/theme/theme.html
@@ -0,0 +1,46 @@
+
+
+
+Modern browser required
+
+
+
+
+ In namespace-aware XML processors, the "xml" prefix is bound to the namespace name http://www.w3.org/XML/1998/namespace. Do not reference this file in XML instances Schawn Thropp: Changed the uriReference type to string type Refers to universal XML 1.0 lang attribute Refers to XML Base: http://www.w3.org/TR/xmlbase
diff --git a/imscp_rootv1p1p2.xsd b/imscp_rootv1p1p2.xsd
new file mode 100755
index 0000000..f8bc522
--- /dev/null
+++ b/imscp_rootv1p1p2.xsd
@@ -0,0 +1,345 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ DRAFT XSD for IMS Content Packaging version 1.1 DRAFT
+ Copyright (c) 2001 IMS GLC, Inc.
+ 2000-04-21, Adjustments by T.D. Wason from CP 1.0.
+ 2001-02-22, T.D.Wason: Modify for 2000-10-24 XML-Schema version. Modified to support extension.
+ 2001-03-12, T.D.Wason: Change filename, target and meta-data namespaces and meta-data fielname. Add meta-data to itemType, fileType and organizationType.
+ Do not define namespaces for xml in XML instances generated from this xsd.
+ Imports IMS meta-data xsd, lower case element names.
+ This XSD provides a reference to the IMS meta-data root element as imsmd:record
+ If the IMS meta-data is to be used in the XML instance then the instance must define an IMS meta-data prefix with a namespace. The meta-data targetNamespace should be used.
+ 2001-03-20, Thor Anderson: Remove manifestref, change resourceref back to identifierref, change manifest back to contained by manifest. --Tom Wason: manifest may contain _none_ or more manifests.
+ 2001-04-13 Tom Wason: corrected attirbute name structure. Was misnamed type.
+ 2001-05-14 Schawn Thropp: Made all complexType extensible with the group.any
+ Added the anyAttribute to all complexTypes. Changed the href attribute on the fileType and resourceType to xsd:string
+ Changed the maxLength of the href, identifierref, parameters, structure attributes to match the Information model.
+ 2001-07-25 Schawn Thropp: Changed the namespace for the Schema of Schemas to the 5/2/2001 W3C XML Schema
+ Recommendation. attributeGroup attr.imsmd deleted, was not used anywhere. Any attribute declarations that have
+ use = "default" changed to use="optional" - attr.structure.req.
+ Any attribute declarations that have value="somevalue" changed to default="somevalue",
+ attr.structure.req (hierarchical). Removed references to IMS MD Version 1.1.
+ Modified attribute group "attr.resourcetype.req" to change use from optional
+ to required to match the information model. As a result the default value also needed to be removed
+ Name change for XSD. Changed to match version of CP Spec
+
+
+
+ Inclusions and Imports
+
+
+
+ Attribute Declarations
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ element groups
+
+
+
+
+ Any namespaced element from any namespace may be included within an "any" element. The namespace for the imported element must be defined in the instance, and the schema must be imported.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/imsmanifest.xml b/imsmanifest.xml
new file mode 100755
index 0000000..29db1fa
--- /dev/null
+++ b/imsmanifest.xml
@@ -0,0 +1,57 @@
+
+
+
+
+
+
+
+
+ ADL SCORM
+ 1.2
+
+
+
+
+ hax-the-web
+ -
+
haxtheweb
+
+
+
+
+
+
+
+
+
diff --git a/imsmd_rootv1p2p1.xsd b/imsmd_rootv1p2p1.xsd
new file mode 100755
index 0000000..d8a7869
--- /dev/null
+++ b/imsmd_rootv1p2p1.xsd
@@ -0,0 +1,573 @@
+
+
+
+
+
+ 2001-04-26 T.D.Wason. IMS meta-data 1.2 XML-Schema.
+ 2001-06-07 S.E.Thropp. Changed the multiplicity on all elements to match the
+ Final 1.2 Binding Specification.
+ Changed all elements that use the langstringType to a multiplicy of 1 or more
+ Changed centity in the contribute element to have a multiplicity of 0 or more.
+ Changed the requirement element to have a multiplicity of 0 or more.
+ 2001-07-25 Schawn Thropp. Updates to bring the XSD up to speed with the W3C
+ XML Schema Recommendation. The following changes were made: Change the
+ namespace to reference the 5/2/2001 W3C XML Schema Recommendation,the base
+ type for the durtimeType, simpleType, was changed from timeDuration to duration.
+ Any attribute declarations that have use="default" had to change to use="optional"
+ - attr.type. Any attribute declarations that have value ="somevalue" had to change
+ to default = "somevalue" - attr.type (URI)
+ 2001-09-04 Schawn Thropp
+ Changed the targetNamespace and namespace of schema to reflect version change
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Any namespaced element from any namespace may be used for an "any" element. The namespace for the imported element must be defined in the instance, and the schema must be imported.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/index.html b/index.html
old mode 100644
new mode 100755
index bce3bd7..83f4ca4
--- a/index.html
+++ b/index.html
@@ -1,154 +1,74 @@
-
+
- HAXcms
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
- hax-the-web
-
-
+
+
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
-
-
+
-
-
-
+
+
-
-
-
-
+
+
-
-
-
-
-
+
-
-
+
-
Danger zone
This will publish your site, overwriting the previous copy living in your \"published\" storage location.
This wil revert the git history powering the site by 1 commit. This is a destructive command, only use this if you just saved something you didn't mean to.
+
+
+
+
+ Loading..
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/legacy-outline.html b/github-pages-deploy-action-temp-deployment-folder/legacy-outline.html
new file mode 100644
index 0000000..69b986e
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/legacy-outline.html
@@ -0,0 +1,9 @@
+
+
+
+
+
+
+
+
+
+
+
+ Please use a modern browser to
+ view our website correctly. Update my browser now
+ - HAX development
- CSS vars
- Concepts
- Add Content
- Core concepts
- hello-world element
- HAXcms
- Installation
- blox
- Get Involved!
- Integrations
- Skin a site
- Block settings
- Structure
- HAX schema
- Solutions
- Web components
- WordPress
- Documentation
- stax
- Search
- UX concepts
- Related technologies
- autoloader
- Templates and Layouts
- Core elements
- F.A.Q.
- Drupal
- Roadmap
- Publishing
- haxHooks
- Presentations
- BackdropCMS
- Scavenger Hunt
- Dev workflows
- Life cycle
- HAXcms
- Internationalization - i18n
- HAX Element Schema
- I have issues
- ClassicPress
- Troubleshooting
- HAX app store
- GravCMS
- Theming
- Creating new ones!
My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/blox/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/blox/index.html new file mode 100644 index 0000000..0a31f5d --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/blox/index.html @@ -0,0 +1 @@ +My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/concepts-app/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/concepts-app/index.html new file mode 100644 index 0000000..16b877e --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/concepts-app/index.html @@ -0,0 +1,2 @@ +An App adds remote data capabilities to HAX. Want to search Youtube without leaving your editing experience? Hax Apps are the way to do that. Apps show up for users under the Find + menu and while we provide definitions for talking to commonly used APIs, it can be modified to connect to almost anything.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/core-concepts/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/core-concepts/index.html new file mode 100644 index 0000000..c01e6e7 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/core-concepts/index.html @@ -0,0 +1,6 @@ +A Gizmo is an advanced piece of media or interactivity placed on the page. At a technical level, it is a web component, but to your users and content readers it's an advanced piece of functionality helping them complete a task. Maybe they want to embed an article from Wikipedia, or create a gorgeous, responsive video. How would they do that without advanced code knowledge?
+Gizmo's ensure that your users have a consistent visual presentation and authoring experience across a myriad of complex functionality. Any web component can be wired to support HAX.
+An App adds remote data capabilities to HAX. Want to search Youtube without leaving your editing experience? Hax Apps are the way to do that. Apps show up for users under the Find + + + menu and while we provide definitions for talking to commonly used APIs, it can be modified to connect to almost anything.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/apps/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/apps/index.html new file mode 100644 index 0000000..e18e33b --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/apps/index.html @@ -0,0 +1,144 @@ +A single App definition
+This is an example of how the Flickr + + + + integration is set up in haxtheweb.org. Below this integration's pieces have been annotated i order to illustrate what each provides to HAX. For more advanced integrations see the complete example + + + + +.
+Autoloader is waaayyy easier to implement then the other parts of the appstore spec and is probably the most important as it loads all the elements that will be available to your users. All it is is an array or object of references to elements that HAX should forcibly load the definitions of once it's done bootstrapping. Here's a basic example with the steps as to what HAX does with this information
+-
+
+
- HAX loads the appstore definition + +
- HAX finishes its bootstrap and is ready to use + +
- It then loops through each autoloader element and does the following: + +
- attempts to dynamically import the definition of the element + +
- It then creates an instance of the element (virtually) and looks for + + static get haxProperties + + + +
- If this exists and is valid haxSchema then you can leverage it in hax! +
-
+
+
Spec details
+There are a few different ways you can declare references to the autoloader schema. Here is a simple example of all three common forms an then we'll explain each.
+Definition from file
+The most common method of import is simply + "tag-name": "location-of-tag.js" +. You'll see this for importing anything that's been published + WITH + + static get haxProperties +. You can also use this to add your own published / built elements that have their own haxProperties. +
+Definition import
+This is basically just to enable future support for defining capabilities at run time. It could also be used to issue an element but not actually import anything (so + "whatever": { "import": ""} + ). This is because possibly other logistics of your CMS / application are in charge of + WHEN + this definition gets imported. +
+Definition import + schema
+This is the most powerful but also most verbose. This allows you to potentially import someone else's element that + DOES NOT + have + haxSchema + defined, and then define it yourself on the fly! This means you can leverage community elements and supply their wiring to talk to HAX based on your own mental model. This allows wiring up anything to HAX, but also the performance benefit of potentially building a design library but not including references to the + static get haxProperties + in your class for the element. +
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/blox/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/blox/index.html new file mode 100644 index 0000000..ff75cbb --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/hax-development/hax-app-store/blox/index.html @@ -0,0 +1,49 @@ +Blox are the internal name of what a normal wysiwyg would call Layouts. The Layouts menu lists the blox / grid-plate tags that you can populate. There's no other way to generate a layout plate in HAX to ensure that decent defaults are produced.
+The schema below will generate the Blox / Layout definition seen above.
+The app store specification is what provides HAX with it's raw data integration capabilities. It's a block of JSON that tells HAXeditor the rules by which it is to play by. A complete example is available in the h-a-x tag's demo + + + + + but we'll outline what the different parts of this JSON supports as well as one app in detail.
+Keys and what they mean
+-
+
- Apps + + + + - A source of data either to upload or search. Apps supply the definition of how to connect to the remote data, search it, upload things to it. + + +
- Blox + + + + - A block of elements. Blox are a series of elements wrapped inside of a plate element. Blox can be modified in pieces but fundamentally the entire thing is one piece. A block can be moved up and down as an entire group. + + +
- Stax
+
+
+
+ - A stack of elements is a series of HTML elements that are added into the DOM all at once. Think of these like a
- Autoloader + + + + - A series of elements that are automatically to be loaded when HAX is setup. + + +
Stax are what most WYSIWYG systems would call Templates. Stax in HAX are a series of HAX element schema's in succession.
+Below is a definition for the "example lesson" seen above. This is a larger example, most templates will probably only be a few items. A stack template is like a blox / layout element except the pieces do NOT have to move as a group and they can be deleted. It's more of a shortcut for generating items. The details area describes the element visually in the UI while the subsequent stax + + + property is an array of HAX element schemas.
+Example of HAX element schema JSON object. It's a pretty simple abstraction of HTML elements that helps with packaging and sanitization.
+h2 tag (core HTML)
+p tag (core HTML)
+video-player (web component)
+Implementing HAXSchema
+In order for your element to talk to the HAX editor, you need to implement static get haxProperties() + on your element. This callback either returns a String + based location of where the HAXSchema lives OR the JSON blob directly. The appstore documentation page also describes how you can integrate without defining this directly on your element.
+- Example definition via file reference + +
- Example definition directly on the element + +
- Example definition via appstore specification + +
Understanding HAXschema
+HAXSchema is the name of our standard for expressing the way HAX can communicate with and implement your web component. This is broken into two major groupings of settings and some basic Boolean +.
+After these Booleans we get into the "Gizmo" section. A Gizmo is what internal to the code base we're calling a custom element as it is represented in HAX interfaces like the Make + area. The reason for this is so that the word element isn't everywhere or else it would get too confusing. A Gizmo describes the way HAX should reference this item in interfaces.
+A detailed example below in the comments
+Settings for wiring up to HAX
+Settings forms for HAX capable elements are grouped into three different areas. The quick +settings segment of the schema provides quick edit, singular properties on the UI as icons. This is present when you select an item in HAX (see screenshot).
+
+
+Configure block
+The configure section shows up when moving on to the settings manager
+After hitting settings, you'll see the manager open up defaulted to the configure settings display.
+Advanced block
+The advanced section shows up when in the configuration manager is open and the user selects Advanced
+Let's see what goes into the element called @lrnwebcomponents/example-hax-element + + +in order to learn how we can wire anything up to HAXeditor.
+@lrnwebcomponents/example-hax-element/example-hax-element.js
+Include HAX in your project
+The developers docs will lay out the many specifications that make HAX possible including core concepts, different schema's it leverages ad how to define app store spec in order to take integrations further.
+Now this paragraph is editable
+Uhh, is that it?
+Yeah, that's it. Behold the power of a thousand open source suns raining down all their hate on the editors of the past and their complex integrations or ecosystem lock in.
+We made tooling to publish web components with ease and in any library. It's called WCFactory and while not required, it's the tooling we use for managing HAX and the many related elements in our library.
+A factory that churns out web components, library agnostic with a unified development, testing, and build to production pipeline. We want to eliminate the barriers to web component adoption because as of Oct 23rd, 89.18% of all traffic can handle web components with no polyfills. Get it on npm + or yarn + and get publishing!
+HAXcms seeks to be a microsite generator and manager that doesn't require any command line in order to operate +. HAXcms leverages HAX to give a best in class authoring experience while HAXcms seeks to eliminate all the barriers to then publishing that content online.
+Some words and phrases worth understanding in HAXcms
+- HAXeditor - the HAX editor +
- microsite - An individual site that's been created by a user +
- Outline - All sites are an outline, we use JSON Outline Schema to manage this +
- Theme - A single web component based theme that's agnostic of content +
- Elements / web components - design assets that work anywhere +
HAXcms, that which powers the site you are currently reading is a powerful "static site generator" paradigm. It leverages server technology in order to orchestrate a static site. That way the "server" is only used when needed for a user to securely develop their content.
+Difference from past static generators
+Unlike solutions like Jekyll + +, HAXcms is for anyone to publish a website, not just those that understand command line. HAXcms is intended to be installed and then allow users to entirely use a UI to create, publish and manage micro-sites.
+Visualization
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html
new file mode 100644
index 0000000..b1913fc
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/installation/index.html
@@ -0,0 +1,228 @@
+Generic PHP install directions
+Have PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is to create two basic folders). If all goes well you'll see some ASCii art telling you what your password is. HAXcms seeks to be a 0 config installation so if anything didn't work or make sense, just drop us a line in the issue queues.
+Or from Command Line...
+Just run this one command and you'll be HAXing the web in no time! This will step you through prompts (which can be scripted via arguments) to feed the backend what it needs to create the few configuration files it uses to load.
+A note on bash + + +
+ +If you're having issues installing via the bash script, ensure you are on bash version 4.x. Some OS flavors start at 3.x which won't work. + + +
+ +MAMP
+MAMP + + + + + + + allows Mac and PC users to rapidly install a working webdev stack on their machine. Here's the steps you need to take if using this (or on similar site hosting).
+Download the latest copy of HAXcms from github + + + + and place this in MAMP/htdocs + +either at the root level (as in copying the files you download into htdocs as shown in the image below) or by placing the folder in the directory (in the case where you have MAMP already installed / want to keep things tidy).
+Open MAMP and hit the Start Servers Button + + + +
+Click MY WEBSITE in MAMP start page to get started + + + +
+Now you can build website organically off of MAMP!
+DDEV / Docksal / Lando / Vagrant
+We recommend using HAXcms in a docker container manager like ddev + + + + + + +, though based on above you can see basically we're just downloading and running one command to get going. We support all of the above methods so pick the one you work with most often.
+-
+
- Clone this repo:
git clone https://github.com/elmsln/haxcms.git+ + + + + + + +
+
+
+
+
+
+
+
+
+ - install docker + + + + + + + + + + + + + + + + +
- install ddev + + + + + + + + or install docksal + + + + + + + + or install lando + + + + + + + + or install vagrant + + + + + + + + (We support 'em all!) + + + + + + + + +
- open a terminal window, go to the directory and type
ddev start+ + + + + + + + (for ddev) orfin init+ + + + + + + + (for docksal) orlando start && lando magic+ + + + + + + + (for lando) orvagrant up+ + + + + + + + (for vagrant)
+
+
+
+
+
+
+
+
+ - go to the link any of them give you in a browser + + + + + + + + +
- username/password is
admin+ + + + + + + +/admin+ + + + + + + + to get building out static sites locally that you can push up anywhere!
+
+
+
+
+
+
+
+
+ - Click the icon in the top right and you're off and running! + + + + + + + + +
Apache gotchas
+If installing on an existing server it might already have apache configurations that would cause HAXcms to have issues out of the gate + (or any CMS for that matter). Make sure local overrides are allowed with something like the following:
+This is a general life cycle that happens when HAXcms "boots up". When web components are unpacking the contents of what to do it generally will work this way.
+- page load, should it be no-js or a web component delivered, preflight +
- haxcms-site-builder loads site.json, reads JSON Outline Schema and starts to bootstrap that into a theme, items, title, etc +
- Appends a haxcms-editor-builder tag which checks for "context" +
- Context is established based on global values for php, nodejs, beaker, etc
- Uses a login end point to check if there's a JWT in the user's local data +
- When it finds a backend, it injects a tag to bridge that backend + +
- HAXeditor gets injected into the correct place in the theme which then all of that unpacks and does its thing +
Event driven architecture
+HAXcms allows for jumping in at different core operational steps and reacting to these changes based on an event driven design pattern. This means that an event "fires" in PHP, much like it does in JavaScript and code written to react to it can make changes at that point in the operation.
+Here is an example from HAXiam which implements custom configuration event listeners
+Core listeners
+Core listeners to influence how the data is constructed. You can add these to your _config/config.php file
+- haxcms-init + - just after HAXcms bootstraps its initial configuration +
- haxcms-site-metadata + - when constructing metadata block at the top of the document +
- haxcms-connection-settings + - for authorized users, this is the block of end points for connecting to and modifying HAXcms logic as far as where data flows. +
Enterprise integrations and SSO
+The following hooks allow for supplanting the HAXcms (intentionally) simplistic login system. This allows you to do custom integrations for your organization. HAXiam implements many of these + if you need specific examples.
+- haxcms-login-test + - when a login didn't pass our simplistic built in checks. Useful for enterprise integrations and other SSO methods of access +
- haxcms-validate-user + - same as login-test except this fires to validate every transaction to ensure the user name matches when decoding the JWT +
- haxcms-jwt-get + - when we ask for the JWT. This allows SSO to supply the token manually via a different methodology than our core one +
- haxcms-refresh-token-get + - when our connection is deemed needing to refresh, this supplies the refresh token for when and what that looks like +
HAXcms requires being published in order to be visible to other people. Working locally or on Desktop or on a server, is akin to you writing a document on your computer. It's not shared with anyone. We recommend you setup publishing ahead of time to save hassle later.
+Setting up publishing
+From the HAXcms site listing + page, click the settings gear in the top right corner.
+Next you'll see a modal that has options for plugging in your github credentials. We don't save your password and this aspect is optional. If you do enter your password, a one time API call is made on your behalf from your container which will setup an ssh key pair. This allows for all future requests to publish to happen automatically on your behalf. Your password is not stored. If you don't want to set this part up, you can plug in the rest of the git settings, save, and then manually publish files after using the UI (see last heading on this page).
Publishing from your sites / new sites
+When you want to share your site with people or update your website, hitting the Publish button inside of your site is how to do this. Click the settings gear in the bottom right to get started.
Currently GitHub is the only provider supported in the local installation method (or from DDEV / one of the supported container providers). In the future hitting publish will have additional development flexibility.
+Understanding what's actually happening
+When you hit publish, a few things happen to make your site "web ready". This is the general order of those operations:
+- HAXcms takes the underlying files and commits them all to version control (though they already should be) + + +
- It then pushes these to the origin of the git repository (likely github) + +
- Then it switches to the branch you do your publishing from. In github, this is the gh-pages + + branch, but can deviate as needed. + +
- Next it deletes symlinks and replaces them with the correct references as needed and leverages the "cdn provider" you specified when setting up HAXcms in order to super charge your files for end users. + +
- It uses twig + + to step through and correctly rewrite references in the index.html of your site to match the paths of where it's going to be sent + +
- Then it adds all this to version control and sends it up to your gh-pages branch. + +
- It does some local file clean up and sets things back to master branch for the next time you go to work on everything + +
When this is all done, in the UI you'll see a link to your site after it's indicated a successful publish (meaning it pushed the files up there). Depending on where you host your content it may take a few minutes to see the change, though GitHub is usually up within about 2 minutes.
+Once about 2 minutes or so has passed, refresh your live site address or type in the URL of the site. If you've been there previously, you'll probably see the same content / theme as the last time you were there. After about 5 seconds, a message will pop up indicating "new content available" and clicking it (or refreshing the browser) will give you your updated content.
+This last step happens because of what's called a "service worker". This enables your site to be 100% offline capable and ensures that your site only uses traffic and data when it's absolutely necessary.
+A note on non UI publishing workflows
+You might not have (or want to) setup the credentials between HAXcms and github / your git repo. That's ok. After you hit publish go to terminal / a Git GUI and run the following to publish your site:
+HAXcms will have made sure that the gh-pages and master branches are valid for distribution, even if it wasn't able to actually send these files to their publishing destination.
+By design we've got a very simple structure. The goal of HAXcms isn't to lock you into anything and so we've simplified our file structure over other solutions.
+The key directories / files include:
+- files - any files you've uploaded through the HAX interface + +
- pages - folders named by their content uri that have index.html in it, no structure other then what you created when hitting save +
- site.json - JSON Outline Schema object that defines the pages in your site and their relationship to each other
- index.html - front page of the PWA that stitch it all together +
- service-worker.js - makes it a PWA, no need to edi this +
Screen grab of a microsite
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/core-elements/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/core-elements/index.html
new file mode 100644
index 0000000..43a3032
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/core-elements/index.html
@@ -0,0 +1,89 @@
+While you're not required to use them, HAXcms supplies a series of elements that can make theme development effortless. You can see the source of these in greater detail under the theme directory of haxcms-elements + + +. This is a brief overview of what they are and what they provide to your interface.
+HAXcms seeks to apply the SDS pattern, a technique we made up just for this sentence, for dramatic effect +. As everyone knows who is about to read the next heading, SDS stands for:
+So. Damn. Semantic.
+Whew, I need an ice cold drink to wash away the semantic sweats.
+Yes, that's right, HAXcms allows you to theme a complex state managed system without needing to understand state management... like... at all.
+"But I understand state management and it's important to me"
+That's awesome, four people on twitter, but most designers just want to design! They don't need or want to understand the intricacies of making a collapsed field area expand relative to what item has been dictated as active in the store*.
+*an intentionally confusing worded sentence + + +
+We use MobX to do our state management if that's something you care about and some of our themes directly implement and interface with the state management layer. See Simple Blog's footer element + + + for a great example of why state management is a PITA. + +
+Back to the elements jerk
+Ok fine, here they are. Here's the list of ES module imports to get them
+Now here's what each of them provide you (pretty self explanatory because #SDS)
+- site-active-title -
+the title of the active item wrapped in a h1 tag
+
- site-children-block + - all child menu items based on a criteria match +
- site-outline-block + - part of the outline based on criteria match +
- site-footer + - a basic footer with license element based on site details +
- site-modal + - a basic modal with button that can house other elements +
- site-breadcrumb + + - a breadcrumb trail for the active menu item +
- site-dot-indicator + - site links but as a simple line of dots +
- site-menu-button
+ - buttons for navigating through the active items in the menu. This is next, previous, parent and first child kinds of options.
- site-menu + + - A visualization of the hierarchy of your site, complete with checkmarks given per page the user goes to (optional) as well as a lot of styling options and a highlighted bar that scrolls the menu into view for small screens. It's fantastic and one line. +
- site-top-menu + - Top level menu links with indicator that scrolls to focus +
- site-print-button
+ - print button with support for 4 levels of printing the site
- site-rss-button
+ - a button that displays a link (opened in a new window) to get the RSS feed in RSS 2.0 or Atom 1.0 format (also applies correct semantic values for bots to discover)
- site-title
+ - a link to the homepage of the site wrapped in an h1 tag
See the elements themselves for more details API examples and check out our themes as we leverage them heavily across the core themes.
+A word about style
+We use CSS variables to style all the bits inside of our custom elements. So if you don't like the styling, look at the CSS variables we make available and style away. The "Learn 2 theme" + + + is a great example implementing multiple levels of styling against multiple HAXcms site elements. You can always you know, go back and reread the CSS variables section +.
+Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that now. The site- + + + + query elements are incredibly powerful aspects of HAXcms theming that deserve their own section anyway.
+site-query + +
+Code Example
+Spoken Example
+"Give me all of the
+When it's useful
+Always. This is by far the most powerful element in our library. It can query the site structure and effectively return anything, anywhere that matches the criteria. It is for exact criteria matching though so you won't be getting children of page X unless you specifically requested them.
+This is great for getting things like getting all the pages that don't have parents (top level items) which is exactly how the site-top-menu + + tag does it in conjunction with a dom-repeat tag (in that example).
+Caveats
+- This doesn't render anything by itself + + +
- You have to then know how to do a two way template bind (Polymer convention looking like {{result}} + +or know how to use javascript in order to bind the results to visual output + +
- Its incredibly powerful + +
A menu slice query is one which takes part of a hierarchy and chops it out to return the items.
+Spoken example
++that are 2 to 4 levels deep. +
Delivered results
+Dynamic leveling
+The dynamic leveling flag would allow you to create a query that analyzes the current active item (as example). And then say "Always give me 2-3 levels below this". In that instance you've got a dynamic sub-set of children being returned.
+When it's useful
+This can be useful for a block that always shows the children of the current page in a documentation site.
+site-render-query + +
+A site render query attempts to standardize the practice of wiring site-query up to something visual. It requires you supply something visual to get going and has the unfortunate limitation though that what you render must not be dynamic in nature.
+Example
+
+
+
+
+
+
+
+ description: [[item.description]]
+ location: [[item.location]]
+ changed: [[item.metadata.updated]]
+
+ Set as active
+
+ When it's useful
+When you have a static set of items you want to query once and have it be dynamic based on site infrastructure yet not be changing dynamically during site view.
+Possible usage
+As we haven't rolled this into any themes at the time, this could be useful for placing a "latest posts" block or "upcoming events" block. Anything that's dynamic based on the data being passed in but yet unchanging once it's loaded. Think of this as a simple "views" construct if you are from the Drupal worldview.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/css-vars/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/css-vars/index.html new file mode 100644 index 0000000..62daeb9 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/css-vars/index.html @@ -0,0 +1,48 @@ +CSS can be modified via CSS variables +. CSS variables create a happy middle ground between the constraints of Shadow DOM (namely that styles are fully encapsulated) and designers wanting flexibility and control over design. We leverage CSS variables heavily in our template layer to allow you to "skin" just about any theme we have already.
+A note about @apply
+Unlike normal css variables, Polymer (the library we build our theme layer on) supports a convention for CSS variables that operate a bit more like Saas mixins. You can write blocks of code like @apply --my-variable-blob; + which will then allow someone to mix in and apply whatever valid CSS attributes they want at that level. You can see several implemented below (both CSS variables and @apply blocks).
+Example
+This is an example from the haxcms-basic-theme +which forms a clean baseline for most sites.
+Our development workflow is as follows (for themes)
+- All custom theme work happens in your _config directory + +
- Make my-theme.js, pull everything together, either in this directory or in a wcfactory + catalog of elements you've made +
- Reference this in you _config/my-custom-elements.js element +
- Update the _config/config.json block that says themes + to include something like... +
This tells HAXcms UI that you can now select the theme (but don't yet, it won't be valid)
+Local development workflow during theme development
+We use polymer cli to serve up and work on web components locally and while you don't have to, it's recommended as part of the WCFactory workflow.
+- Make a new site in the HAXcms UI + +
- Go to _sites/mynewsite and run polymer serve --npm --open --entrypoint dist/dev.html + + +
- Adjust the URL that opens to only be the IP address with no path after it +
- You'll see your site open up for local development work, which will be leveraging any assets referenced in your node_modules directory at the HAXcms project root. +
- To add / install new assets run yarn (or npm) add @what/ever-you-want --save +, just like you would any other project you work on in FE dev +
- edit your site's site.json manually to update the theme to point to the theme location your actively working on +
- Develop away until it is to your liking +
Shipping the theme
+To ship the theme, you'll need to do a polymer build routine
+important note
+This currently forks you from the original source of HAXcms core (because it will recompile the assets). If you're ok with this cool, just know we're trying to find ways around this involving rollup +.
+- Go to the HAXcms project root + +
- run polymer build + + +
- Copy the build directory and go to your site +
- Delete the symlink and replace it with your build directory +
- Now you can publish via the UI so long as you do not leverage a CDN +
The future
+Admittedly, the full on custom theme / web component development workflow is rough. It's hard to maintain a built copy in a modular system without tooling. In the future we plan on having tooling workflows built directly into WCFactory that allow you to streamline the development and creation of HAXcms themes.
+Current limitations
+You can't leverage existing CDNs (like webcomponents.psu.edu and whatever else is out there) that are pegged to the HAXcms project's source. You'll be creating a custom theme which then creates a custom build in effect so you'll want to ensure that you have some place that you can host the assets in order to power your site.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/index.html new file mode 100644 index 0000000..2494039 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/theming/index.html @@ -0,0 +1,337 @@ +There are multiple ways to "theme" in HAXcms that align with the skillsets of the person doing the theme development. Know web components? Cool. Know basic CSS and HTML? Cool. Want to build something complete from the ground up? Go for it. We've got a robust templating engine to unleash your creativity.
+We've also written the wcfactory + + + + + tooling in order to improve the development and management of web component libraries at scale (see LRNWebComponents + + + + + for our element portfolio). This isn't required but if you fancy yourself a "modern front end developer" this might be for you.
+Watch a video
+These are some deep dives into the HAXcms theme layer. They are great for seeing what's possible, how we go about making new themes. Now the store and state management works internally and how we try to always keep state away from designers.
+Here's the source code for the learn-two-theme + + + + (which you are viewing currently) as an initial example of what a theme looks like.
+
+
+
+
+
+
+
+
+
+
+ Theme skinning is the easiest way to build a decent looking theme in HAXcms. This method is geared toward people that know CSS and HTML but can't get into the weeds of web components or javascript.
+Workflow
+- Make a new site in the HAXcms UI + +
- Select "Custom theme" as your theme +
- In the file system go to _sites/mynewsite +/theme +
- Edit theme.html to modify the structure +
- Edit theme.css to modify the design +
This is the easiest way to skin HAXcms to your liking. It's able to ship and work in CDNs and is the minimal barrier to entry for those used to seeing HTML and CSS files that they can touch and see the change. It requires no tooling to utilize either!
+Do you know full on web component development? Well, you can build a new theme from scratch. The best way to learn is by picking a part some of our examples. For this we'll analyze the haxcms-slide-theme + +.
+Import classes / web components
+As you can see this theme imports a few basic components helpful in the development of most themes. First we import PolymerElement and the HAXCMSTheme mix-in from our theme wiring library. Theme wiring provides a basis for wiring any custom element into the state management of HAXcms, typically without having to deal with any concepts of state!
+Mix-ins
+Next we get the mix-in statement. Note how HAXCMSTheme wraps the PolymerElement class, thereby giving us a mix of the two together.
+HAXCMSTheme mix-in class
+You can learn more about what the mix-in class provides by digging into the HAXCMSThemeWiring.js + + class. This class bridges the HAXcms store (written in mobx) with the design layer. This way you can leverage anything in the store by writing the polymer convention for referencing a data bound variable in the template.
+Here's the variables you'll commonly see + + in our themes, direct from the store with an example of what a dom bind of that would look like in a template
+[[siteTitle]]
+[[ancestorTitle
+[[parentTitle]]
+[[activeTitle]]
+
+ [[activeItemFields.images.0.url]]
+
+That last line with activeItemFields is part of the raw power under the hood of this approach. You can use HAXcms to create field definitions (in HAXschema + +) that then extend the capabilities of your pages.
+Required CSS
+There is one small required block of CSS when doing web component / theme development for HAXcms. It is the following:
+This helps ensure that when your user clicks the edit button that they see the HAXeditor as opposed to the body of content they are currently working with. Then when they hit save, the HAXeditor sends the content to the backend which then updates the front end and they see the changes. This CSS ensures that it isn't visible during editing.
+Required HTML
+
+
+Related to the CSS, the following block of HTML must appear in your template somewhere (or in the case of simple-blog +, an element leveraged by your theme). You can make this look like whatever you want beyond this but this ensures the HAXeditor can correctly target and be integrated using the HAXCMSTheme mix-in. There are ways to position and reposition the HAXeditor dynamically that will not be covered here but can be seen in simple-blog +.
+From there, design away. Write whatever CSS and HTML and JS you want! The example themes referenced in our docs all provide blue prints for different ways of leveraging our template system.
+Next we'll discuss our Core template elements which you'll want to leverage in order to make theme development even cleaner!
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/troubleshooting/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/troubleshooting/index.html new file mode 100644 index 0000000..d9fda21 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/haxcms/troubleshooting/index.html @@ -0,0 +1,13 @@ +These are some common issues / resolutions in HAXcms related to installation, publishing, etc.
+I installed HAXcms and forgot my password
+Your username and password can be found in _config/config.php on the server (assuming local development)
+I clicked login and nothing happened and now I'm locked out.
+- Clear your browser cache. A cookie is set that might be invalid. + +
- Open a new browser and try to login again +
I clicked publish and nothing happened
+- Publishing can take up to a minute or so at times since it's creating a commit, rewriting files and then the front end is waiting on the push to github before it triggers a successful response. +
- If it did fail to publish, you might not have git setup. Click the gear icon on the dashboard (site listing) and ensure you've setup github / git integration correctly. +
Realize that everything is just a file and that our json outline schema is very easy to read. So if there's an issue with something related to publishing, check _sites/mysite/site.json for publishing, then _config/config.json. All settings and variables cascade in this way. Settings are stored globally, then replicated locally to allow them to be pealed off and more easily imported / exported into other setups.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/index.html new file mode 100644 index 0000000..a2cb6c4 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/index.html @@ -0,0 +1,10 @@ +HAX may seem complex, but it's built on a series of standards that will never + + break. As a result of the complexity of these standards, there are things you should know prior to digging into HAXeditor core or any of its related Solutions +
+Watch us build!
+Many members of the core development team participate in a show called HAX camp Uncode +.
+ +There are several technologies you should learn about if your going to understand how HAX is built (and how to extend it)
+JSON Schema
+Learn more about JSON Schema + + + + on the official website for that standard. JSON Schema provides a way of describing the data contained in a JSON blob so that a form can be built to modify those values. HAX uses this extensively via a tag called eco-json-schema-object + + + + and related tags, to turn any json schema definition into a fully two-way data binded form.
+Example
+HAX schema + + + + + is an abstraction that sits on top of JSON Schema in order to provide forms for updating values in your HAX wired elements. If you wanted to extend the types of input fields that HAX has access to then learning JSON Schema would be the best place to start!
+JSON Outline Schema
++ +JSON Outline Schema + is a standard way of expressing and storing the relation between objects. It gives you a simple way of linking data together to form an outline of related concepts / entities. Here is an example of a JSON Outline schema entity:
+This gives you enough data to visually represent this information in an outline form. Let's look at a larger example of 3 items related together which would express nested hierarchy in a consistent way:
+Let's break down these properties and why we have them in the schema:
+Higher order schema
+- `title +` - name of the work as a whole +
- `author +` - who created this work +
- `description +` - short description of the work to explain it +
- `license +` - a valid license short hard for the work as a whole +
- `metadata +` - area to storing any additional details about the work. This has no standard structure but could be used for relating work if needed. +
- `id +` - a unique identifier for this work in the universe of all works +
- `items +` - an array of schema elements which contain the pages / leaves of the structure of this outline +
Leaf / page element within the structure
+- `id +` - the UUID / unique ID of the element +
- `indent +` - How far to visually position the item inward. You could have something be the parent as a page but visually only be indented 2 levels +
- `location +` - a file or resource that references the related data to display here +
- `order +` - a weighting as to the order relative to other items that match this parent level +
- `parent +` - a UUID / unique ID of the element this is a child of +
- `title +` - title of this item to display +
- `description +` - short description of the item to explain it +
- `metadata +` - a container for any additional details of information you need to ship. This has no standard structure +
Add Content + is how you create and add complex blocks to the HAX page editor. These blocks can be variable based on what you chose to include (see appstore +) but ultimately are just adding web components to the editable area of the page. These web components then tell HAX how to surface an editing interface which then just writes to the properties, attributes, and slots of the element in the editable area of the page.
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html
new file mode 100644
index 0000000..544941f
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/find/index.html
@@ -0,0 +1,3 @@
+Search + is a data interoperability layer to HAX where web components data binding shines. Search is able to stitch remote data together with local web components in order to streamline workflows. You can search any source directly in context and then drag and drop or click the item in question to add it to the page your building instantly.
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html
new file mode 100644
index 0000000..ef95f78
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/documentation-1/ux-concepts/index.html
@@ -0,0 +1,6 @@
+The HAX UI can be broken down into three major production concepts. Content authors are either:
+- Adding something they already have
- Editing the Settings of the activated element on the page +
- Search for media from remote sources
- Add in a Template or predefined layout into the page +
Make allows you to create things using the Gizmos that the editor knows about. Make typically will involve media pieces but could also just be a treatment to text you'd like to apply. Some examples of things you can make with the default editor settings:
+- Wikipedia article - reference a wikipedia article and cite it just by entering the name of the article + + + + + + + +
-
+
+ + + +
+
+
+
+
+- Math
+ - So that you can write things like
e=mc^2 + + + which is WAY more difficult then you'd ever expect. +
+
+
+ + + +
+
+
+- can be used to wire metadata into text elements in order to provide additional details for search engines + + +
- Or hey, make a QR code, whatever you want. These are just some of the things that come out of the box + + + + + + + +
Using the make menu
+Are web components legit? Is this really possible?
+Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor + + + leverages this approach and standardizes its usage in order to supply an incredible amount of functionality in the browser. We do what the vast majority of CMS provide prior to interfacing with a server. Just HTML files and a h-a-x + + + + + + tag to understand how to modify content.
+What's Browser support like?
+- Web components + + + + + + + + + + + can be compiled to support IE11 and work in all major browsers natively + + + + + + + + + + + + +
- HAXeditor + + + + + + + + + + + is supported by IE 11 + + + + + + + + + + + and all major browsers, though we mostly test "evergreen" browsers. + + + + + + + + + + + +
- HAXcms + + support is broad but a bit fragmented to optimize the experience per each device. From lowest to highest quality (numbers based on global traffic data in aggregate + +, last updated July 2019 + +) + +
- IE (11) / Safari (9.1) / older - no JS / frame based site
+
+ (~ 3%)
- Edge (18 and below) - watered down UI + + (~ 2.2%) + + + +
- Firefox 48-67 / Safari 10.x (~1%) - ES5 or ES6 w/ AMD compile + +
- Evergreen / Modern browsers (~ 93.8%) - Native ES6! + + + + +
Do I have to use the elements HAXeditor supplies?
+No. HAX is written such that the Appstore Specification + + + + + + + + + + + + + + + is defining the elements that are available in this site and other demos. Leveraging the autoloader + + + + + + + + + + + + + + + piece of the spec, you can tell HAX which tags to load. The web component definitions and schema can be kept separate as desired (useful in CMS with editorial workflows / permissions scenarios).
+Do these elements require HAX to operate?
+No! HAX modifies HTML inside of itself and then exports back to HTML. This means that as long as the web components on your site have definitions, HAX no longer is required to render them!
+HAX is effectively writing the same HTML you could have by hand. Web components help make it semantic but also ensure that functionality lives with "the platform"; in this case, the platform being the browser. So long as the definitions of the component are in scope of the page, the element will unpack correctly HAX or otherwise.
+How does this compare to the WordPress Gutenberg plugin?
+In terms of mission and what they attempt to provide, a click and build website tonight, no-or-minimal-code solution for the masses... they are the same. They both seek to reduce barriers to entry in web expression. HAX takes some critical differences in philosophy of design to Gutenberg both in technical implementation and goals for the open web.
+HAX seeks to improve web publishing for all systems, HAXcms or otherwise. HAXcms (which this site is constructed in) is but a tiny fraction of the web and we want to empower anyone to improve self expression. We want to improve privacy, self sovereignty, and the individuality of all peoples on the web. HAX seeks to eliminate technical barriers to production, integration and delivery of material on the internet; all of it, not just the expensive CMS part of it. We want to hax-the-web, hence this domain name.
+Some larger points of different are highlighted below
+- HAX is platform independent - We seek to improve the web and all that it touches, platform agnostic. Gutenberg is highly focused on the needs of WordPress and improving the content authoring experience for WordPress users. + + + + + + + + + + + + + +
- Gutenberg embeds its blocks layer with the authoring nuance such that all operations can be wildly different per block. For example, a tabbed list of items may have a "add another" button inline with the block. HAX believes that the editing experience across complex elements must be delivered by the HAXeditor, not the element or block level. This illustrates itself in the UX as users selecting an element to work on and then interfacing with it the same way they would any other element. We feel that this will reduce long term barriers to adoption by end-users and training through a lack of cognitive load increase per element. + + + + + + + + + + + + + +
- Gutenberg sees you "add" things as its primary construction method. If you need to upload media that's a separately integrated process, highly dependent on WordPress to deliver. HAX boils content creation operations down into the mental model of the author. Authors either say "I need to Add + + + + + + + + + + + + + + something" (Add menu), "I need to to Find + + + + + + + + + + + + + + something" (Find menu), "I need to Make + + + + + + + + + + + + + + something" (Make / create menu), "I need to Layout + + + + + + + + + + + + + + something" (Blox / Layout menu) or that they want to remix something from a Template + + + + + + + + + + + + + + (Stax / Template menu). + + + + + + + + + + + + + +
- The Gutenberg blocks system produces react components which are specific to the logistics of WordPress. The elements produced for HAX work in and out of HAX capable systems + + +. We believe in extending the broader capabilities of the web first and HAX second in order to reduce duplication of efforts globally and improves resource sharing. + + + + + + + + + + + + + +
- Gutenberg is written in React, effectively requiring all plugins and block components be written in React. HAX is written in Web components leveraging a mix of "VanillaJS", LitElement and PolymerElement constructed elements. You can use any web component compatible library + + + + + + in order to produce elements for HAX. While not limited to, here are some popular examples that could natively talk to HAX: + + + + + + + + + + + + + +
- VanillaJS following the web component specification + + + + + + + + + + + + + +
- PolymerElement + + + + + + + + + + + + + + + + +
- LitElement + + + + + + + + + + + + + + + + +
- SkateJS + + + + + + + + + + + + + + + + +
- Slim.js + + + + + + + + + + + + + + + + +
- Svelte + + + + + + + + + + + + + + + + +
- VueJS + + + (web component wrapper) + + + + + + + + + + + + + +
- Angular Components + + + (compiled to custom elements) + + + + + + + + + + + + + +
- Any library that passes testing on custom-elements-everywhere + + + + + + + + + + + + + + should work + + + + + + + + + + + + + +
Where did this come from?
+HAX is the brain child of the ELMS:LN team at Pennsylvania State University + + + + + + + + + + + + +. HAX is the authoring solution originally created to power ELMS:LN + + + + + + + + + + + + + and other instructional innovations and was quickly realized for its potential to transform web publishing.
+The original core development / evangelist team on HAX in its infancy (an idea conceived in 2016, experimented in 2017, manifested in 2018, actualized in 2019):
+- Bryan Ollendyke (@btopro + + +) - Project lead Developer + + + + + + + + + + + + +
- Michael Potter (@hey__mp + + +) - Core Developer + + + + + + + + + + + + +
- Nikki Massaro-Kauffman (@nikkimk + + +) - Core Developer + + + + + + + + + + + + +
- Charles Lavera (@cgldevel + + +) - Core Developer + + + + + + + + + + + + +
- Michael Collins (@_mike_collins + + +) - End user testing, needs assessment + + + + + + + + + + + + +
- Katrina Wehr (@katrinamwehr + + +) - End user testing, needs assessment + + + + + + + + + + + + +
- Melissa Hicks (@juststormy + + +) - Needs assessment, champion + + + + + + + + + + + + +
There is nothing we can't do together.
+Ex uno Plures
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/f-a-q-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/f-a-q-1/index.html new file mode 100644 index 0000000..f62d578 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/f-a-q-1/index.html @@ -0,0 +1,92 @@ +Are web components ready for prime time?
+Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor + leverages this approach and standardizes its usage in order to supply an incredible amount of functionality in the browser. We do what the vast majority of CMS provide prior to interfacing with a server. Just HTML files and a h-a-x + + tag to understand how to modify content.
+What's Browser support like?
+- Web components + can be compiled to support IE11 and work in all major browsers natively +
- HAXeditor + is supported by IE 11 + and all major browsers, though we mostly test "evergreen" browsers. +
- HAXcms + support is broad but a bit fragmented to optimize the experience per each device. From lowest to highest quality (numbers based on global traffic data in aggregate +, last updated Aug 2020 +) +
- IE (11) / Safari (9.1) / older - no JS / frame based site
+ (~ 1.8%) ES5 / fallback text
- Edge (18 and below) - watered down UI + (~ .7%) ES5 + +
- Firefox 48-67 / Safari 10.x (~1%) - ES5 +
- Evergreen / Modern browsers (~ 96.5%) - Native ES6! + +
Do I have to use the elements HAXeditor supplies?
+No. HAX is written such that the Appstore Specification + is defining the elements that are available in this site and other demos. Leveraging the autoloader + piece of the spec, you can tell HAX which tags to load. The web component definitions and schema can be kept separate as desired (useful in CMS with editorial workflows / permissions scenarios).
+Do these elements require HAX to operate?
+No! HAX modifies HTML inside of itself and then exports back to HTML. This means that as long as the web components on your site have definitions, HAX no longer is required to render them!
+HAX is effectively writing the same HTML you could have by hand. Web components help make it semantic but also ensure that functionality lives with "the platform"; in this case, the platform being the browser. So long as the definitions of the component are in scope of the page, the element will unpack correctly HAX or otherwise.
+How does this compare to the WordPress Gutenberg plugin?
+In terms of mission and what they attempt to provide, a click and build website tonight, no-or-minimal-code solution for the masses... they are the same. They both seek to reduce barriers to entry in web expression. HAX takes some critical differences in philosophy of design to Gutenberg both in technical implementation and goals for the open web.
+HAX seeks to improve web publishing for all systems, HAXcms or otherwise. HAXcms (which this site is constructed in) is but a tiny fraction of the web and we want to empower anyone to improve self expression. We want to improve privacy, self sovereignty, and the individuality of all peoples on the web. HAX seeks to eliminate technical barriers to production, integration and delivery of material on the internet; all of it, not just the expensive CMS part of it. We want to hax-the-web, hence this domain name.
+Some larger points of different are highlighted below
+- HAX is platform independent - We seek to improve the web and all that it touches, platform agnostic. Gutenberg is highly focused on the needs of WordPress and improving the content authoring experience for WordPress users. +
- Gutenberg embeds its blocks layer with the authoring nuance such that all operations can be wildly different per block. For example, a tabbed list of items may have a "add another" button inline with the block. HAX believes that the editing experience across complex elements must be delivered by the HAXeditor, not the element or block level. This illustrates itself in the UX as users selecting an element to work on and then interfacing with it the same way they would any other element. We feel that this will reduce long term barriers to adoption by end-users and training through a lack of cognitive load increase per element. +
- Gutenberg sees you "add" things as its primary construction method. If you need to upload media that's a separately integrated process, highly dependent on WordPress to deliver. HAX boils content creation operations down into the mental model of the author. Authors either say "I need to Add + something" (Add menu), "I need to to Find + something" (Find menu), "I need to Make + something" (Make / create menu), "I need to Layout + something" (Blox / Layout menu) or that they want to remix something from a Template + (Stax / Template menu). +
- The Gutenberg blocks system produces react components which are specific to the logistics of WordPress. The elements produced for HAX work in and out of HAX capable systems +. We believe in extending the broader capabilities of the web first and HAX second in order to reduce duplication of efforts globally and improves resource sharing. +
- Gutenberg is written in React, effectively requiring all plugins and block components be written in React. HAX is written in Web components leveraging a mix of "VanillaJS", LitElement and PolymerElement constructed elements. You can use any web component compatible library + + in order to produce elements for HAX. While not limited to, here are some popular examples that could natively talk to HAX: +
- VanillaJS following the web component specification +
- PolymerElement + +
- LitElement + +
- SkateJS + +
- Slim.js + +
- Svelte + +
- VueJS + (web component wrapper) +
- Angular Components + (compiled to custom elements) +
- Any library that passes testing on custom-elements-everywhere + should work +
Where did this come from?
+HAX is the brain child of the ELMS:LN team at Pennsylvania State University +. HAX is the authoring solution originally created to power ELMS:LN + and other instructional innovations and was quickly realized for its potential to transform web publishing.
+The original core development / evangelist team on HAX in its infancy (an idea conceived in 2016, experimented in 2017, manifested in 2018, actualized in 2019):
+- Bryan Ollendyke (@btopro +) - Project lead Developer +
- Michael Potter (@hey__mp +) - Core Developer +
- Nikki Massaro-Kauffman (@nikkimk +) - Core Developer +
- Charles Lavera (@cgldevel +) - Core Developer +
- Michael Collins (@_mike_collins +) - End user testing, needs assessment +
- Katrina Wehr (@katrinamwehr +) - End user testing, needs assessment +
- Melissa Hicks (@juststormy +) - Needs assessment, champion +
There is nothing we can't do together. Help us build a better web together!
+Ex uno Plures
diff --git "a/github-pages-deploy-action-temp-deployment-folder/pages/f.a.q\357\200\251/index.html" "b/github-pages-deploy-action-temp-deployment-folder/pages/f.a.q\357\200\251/index.html" new file mode 100644 index 0000000..0a31f5d --- /dev/null +++ "b/github-pages-deploy-action-temp-deployment-folder/pages/f.a.q\357\200\251/index.html" @@ -0,0 +1 @@ +My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/get-involved--1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/get-involved--1/index.html new file mode 100644 index 0000000..18fd63d --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/get-involved--1/index.html @@ -0,0 +1,131 @@ +Join our community
+- Join us on the HAXTheWeb Slack + + + channel + + + +
- Follow / use the #HAXTheWeb hash tag + + + + + + + +
Jump in issue queues
+- HAXcms + + + + + + + + - That which powers this website + + + + + + + + +
- HAXeditor + + + + + + + + - That which powers our editing experience (and all our other tags for that matter) + + + + + + + +
- WCFactory
+
+
+
+
+
+
+
+ - Build and maintain your own web component library, why should we be special.
- Check out our integrations page + + + for platform specific repos + + + + + + + +
Organization that wants to get involved?
+Great! Here's some of the best ways for organizations to try "HAX" and get involved in the project.
+- Reach out to any of the members of the core project team or who's listed at the bottom of the FAQ + + +. We're happy to do conference calls to forge partnerships especially around HAX as a Learning management or OER production solution though it has implications for any public site! + + + + +
- Try out the HAXcms live demo + + + (reset hourly) + + + + +
- Reach out in in the HAXcms issue queue + + + + + with questions + + + + +
- Bring this website to developers in your organization or other code junkies and tell them to explore +
- Host a HAX camp / meet up (ask for more details) + + + + +
HAX makes up multiple projects across hundreds of web components and various other repos. It can be a bit overwhelming but we want you to imagine something... Imagine being a developer on HAX.
+Because all it takes to get involved in HAX is, that's right, showing up in our repos and getting involved! Yes you too can be just as special and meme-able as we are!
+All things HAX are powered by people just like you, wanting to make the web a better, more accessible, easier to use, less painful to develop for... place.Help us make that a reality and you too could have Snoop Dawg escorting you over to a brand new car*
+Anything is possible with HAXTheWeb. The only limit...is yourself + + + + + + + +.
+*Claims vs reality may vary. Just help us out and we'll see where it goes.. + + + + + + + +
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/get-involved-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/get-involved-1/index.html new file mode 100644 index 0000000..df99a41 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/get-involved-1/index.html @@ -0,0 +1,43 @@ +Join our community
+- Join us on the HAXTheWeb Slack + channel +
- Join us for HAXcamp Un-code + every Friday 3 pm - 5 pm (EST) +
- Follow / use the #HAXTheWeb hash tag + +
Join our projects
+- HAXcms + - That which powers this website +
- Unbundled-Webcomponents + - A methodology for building and deploying web components to CDNs that we use in all our projects +
- Web components monorepo + - That which powers our editing experience (and all our other tags for that matter) +
- WCFactory
+ - Build and maintain your own web component library, why should we be special.
- Check out our integrations page + for platform specific repos +
Organization that wants to get involved?
+Great! Here's some of the best ways for organizations to try "HAX" and get involved in the project.
+- Reach out to any of the members of the core project team on our slack +. We're happy to do conference calls to forge partnerships especially around HAX or OER production solution though it has implications for any public site! +
- Try out the HAXcms live demo + (reset hourly) +
- Reach out in the issue queue + with questions +
- Bring this website to developers in your organization or other code junkies and tell them to explore +
- Host a HAX camp + (ask for more details) +
HAX makes up multiple projects across hundreds of web components and various other repos. It can be a bit overwhelming but we want you to imagine something... Imagine being a developer on HAX.
+Step 'ight up
+
+ urz te next contrib
Because all it takes to get involved in HAX is, that's right, showing up in our repos and getting involved! Yes you too can be just as meme-able as we are!
+All things HAX are powered by people just like you, wanting to make the web a better, more accessible, easier to use, less painful to develop for... place.Help us make that a reality and you too could have Snoop Dawg escorting you over to a brand new car*
+Anything is possible with HAXTheWeb. The only limit...is yourself +.
+*Claims vs reality may vary. Just help us out and we'll see where it goes.. +
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/gizmo/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/gizmo/index.html new file mode 100644 index 0000000..5562706 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/gizmo/index.html @@ -0,0 +1,2 @@ +A Gizmo is an advanced piece of media or interactivity placed on the page. At a technical level, it is a web component, but to your users and content readers it's an advanced piece of functionality helping them complete a task. Maybe they want to embed an article from Wikipedia, or create a gorgeous, responsive video. How would they do that without advanced code knowledge?
+Gizmo's ensure that your users have a consistent visual presentation and authoring experience across a myriad of complex functionality. Any web component can be wired to support HAX.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/haxcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/haxcms/index.html new file mode 100644 index 0000000..0a31f5d --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/haxcms/index.html @@ -0,0 +1 @@ +My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/haxdesktop/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/haxdesktop/index.html new file mode 100644 index 0000000..ef263ef --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/haxdesktop/index.html @@ -0,0 +1 @@ +HAXdesktop is the same great experience of HAXcms but provided as a stand alone desktop app. It builds out content that is in a forever format just like HAX, and puts it in version control, but with the simplicity of using a desktop app.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/elms-ln/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/elms-ln/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/elms-ln/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxcms/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxcms/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxeditor/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxeditor/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxeditor/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxiam/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxiam/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/home/roadmap/haxiam/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/backdropcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/backdropcms/index.html new file mode 100644 index 0000000..b4d1e19 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/backdropcms/index.html @@ -0,0 +1,13 @@ + +Getting HAX setup in BackdropCMS
+- Search for HAX on BackdropCMS.org + or from within your Backdrop site +
- Follow the instructions in the Web components module README + for building +
- Don't worry, HAX requires Web components module but the module comes with files that supply details to install HAX +
- Enable the HAX and Web components modules +
- Go to a node in your site, you should see a tab that says "HAX mode" +
- Enjoy HAXing your BackDropCMS site +
ClassicPress + is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original!
+-
+
- Get the HAX plugin + from the wordpress registry +
- Go to edit / create a page/post and you are HAXing +
Installation video
+This shows installing it manually if you can't get it from the wordpress store!
+ClassicPress + + + + + + is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original!
+-
+
+
+
+
- Get the Web component plugin + + + +, unzip and rename to webcomponents + + + + + + + +
- Get the HAX plugin + + + +, unzip and rename to hax + + + + + + + +
- Put both of these plugins in your wp-content/plugins/ + + + + directory + + + +
- Go into your site's plugins area and enable both wp-admin/plugins.php + + + + + + +
- Go to edit / create a page/post and you are HAXing + + + + + + + +
Installation video
+HAXeditor keeps so much functionality on the front-end that there's really very little tying it to..well.. anything. As a result, HAX is easy to integrate into systems that currently have WYSIWYG capabilities.
+All integrations effectively boil down to four things
+- End point to load content + + +
- End point to save content + + +
- End point to load the appstore specification + + +
- End point to upload files (optional) + + +
Content filtering
+Because web components are valid HTML tags your system may accept them when saved into your database but you may also be doing tag filtering or other XSS sanitization prior to storage. If you do process prior to storage (and you should) but it strips the web components out of the mark up, you'll need to add some filtering / white-listing capabilities to your system in order to ensure that the web component html tags pass through that should.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/creating-new-ones/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/creating-new-ones/index.html new file mode 100644 index 0000000..b19cfdc --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/creating-new-ones/index.html @@ -0,0 +1,49 @@ +The main piece to our integrations is wrapped up in something we call "The magic script". The magic script is a standard way of dynamically discovering and importing the definitions of web components on the fly. We leverage this approach in all of our HAX platform integrations because it simplifies the initial question of how to teach the CMS / app about web components.
+There's an entire Dev.to Series about our integration + methodology if you'd like more detail about why we do this or how it works. The integration methodology is a stand alone repo you can use for custom builds, found in our Unbundled Web components repo +. Below is what is recommended if you want to leverage our CDN and wide array of elements we already include in our builds.
+This script will load off of the Penn State CDN and automatically hydrate the web components discovered on the page, including h-a-x and the HAX family of tags.
+HAX All the Things + repo has every integration we support as well as some examples of including HAX in Angular and other frameworks (see platform folder in that repo). For a common CMS integration example see this part of the WordPress plugin (code below)
+WordPress integration example
+In this example we can see that WordPress is able to integrate with the wysiwyg-hax tag by using jQuery to correctly time when the WordPress loaded DOM is ready, then replacing the "content" area (a textarea with id="content") at run time with our light-dom capable wysiwyg-hax tag.
+General integration advisement
+HAXeditor keeps so much functionality on the front-end that there's really very little tying it to..well.. anything. As a result, HAX is easy to integrate into systems that currently have WYSIWYG capabilities.
+All integrations effectively boil down to four things
+- End point to load content +
- End point to save content +
- End point to load the appstore specification +
- End point to upload files (optional) +
Content filtering
+Because web components are valid HTML tags your system may accept them when saved into your database but you may also be doing tag filtering or other XSS sanitation prior to storage. If you do process prior to storage (and you should) but it strips the web components out of the mark up, you'll need to add some filtering / white-listing capabilities to your system in order to ensure that the web component html tags pass through that should.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/drupal/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/drupal/index.html new file mode 100644 index 0000000..66f4488 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/integrations-1/drupal/index.html @@ -0,0 +1,53 @@ +Try on SimplyTest.me
+Try HAX on Simplytest me in a few steps without needing to install anything
+- Go to Simplytest me and pick HAX module + +
- Pick 9.x,8.x or 7.x +
- Log in, go to Administration -> Configuration -> Content Authoring -> Input formats / filters +
- Make sure that Filter HTML tags is disabled +
+ CDN all the things
+ Garland...
Getting HAX setup in Drupal CMS
+HAX works with Drupal 8, 7 and all the way back to 6 (mostly to prove a point). While the install routines are largely the same make sure you follow the directions for your flavor of Drupal if it has any branching steps. Drupal 8 is the easiest to get setup while 7 and 6 require some additional modules to get going.
+- Go to the HAX project page on drupal.org + + +
- Be aware that the Drupal 8 and 9 version of HAX does not + + require the web components module while Drupal 7 does +
- Download the module for your platform and follow the directions found in the README.md + +
- Drupal 7 have these files in the CopyThisStuff + folder found in the web components module + so make sure you get that! +
- Enable the HAX module
- Web components module too if in Drupal 7
+
- Go to a node in your site, you should see a tab that says "Block editor mode" + +
- Enjoy HAX'ing your Drupal site! + +
Special note on Drupal 7
+In order to get the upload capabilities in Drupal 7 you'll need to download the File Entity + + and RESTws + + modules as well. We've created a "HAX Common" feature using the Features module which will help with the dependencies that are common in sites using HAX.
+There's two plugins needed to run HAX on GravCMS - The web components and HAX plugins.
+- Web components plugin
+
+ - provides the build routine and installation instructions
- HAX plugin + + - editor capabilities + +
Enable these and then HAX will show up when you go to edit / add a page. Beware there can be conflicts between HAX and the markdown parsing capabilities of Grav so you may need to disable the markdown parser on pages that use HAX.
+HAX provides plenty of ways to integrate into the platforms you already use! Here are some of the plugins and integrations below this heading.
+Some things a liittle bit crazy
+- Code Pen
+?!
- Demonstration of Autoloading any web component + in codepen from a CDN +
- HAX bookmarklet + (allows injecting HAX into any website, see below for details) +
- Web-component-izer + - Inject and clip parts of web sites (good for exploring the web component ecosystem we ride on) +
- Electron Apps - once ours reaches maturity you'll know! +
We support WordPress too! In order to use HAX though you'll want to replace the Gutenberg editor. The following steps will help you get it up and running.
+- Get the Classic Editor +. This plugin helps restore WordPress back to what you wanted +
- Get the HAX plugin +, unzip and rename to hax +
- Break free of platform specific assets and content +
Elements can integrate deeply into HAX state management using what we call "hax hooks". By supplying a method on your web component like + haxHooks() + you are magically able to tap into different life-cycle steps within the HAX editor. +
+Because of the simplicity and power of + haxHooks + this may not be an exhaustive list and + + the internal code documentation on this should be consulted + (or open an issue to ensure we document a missing hook!). You can search the lrnwebcomponents monorepo for usage of haxHooks + in order to discover additional implementations beyond what is pointed to below.
++ Blog posts about this topic +
+-
+
-
+ haxHooks(): How elements can supply their own editing experience in HAX now!
+
+
+ -
+ haxHooks: webcomponents that ship their own editing UX
+
+
+
+Code example
++ This is a basic example in which each of the strings you'd then implement as their own async + callbacks. async + / await + allows HAX to safely defer to your element to do whatever it wants to the DOM / internal structure of that callback, without disrupting element activation or conversion of DOM structure to HAX Element Schema, what it uses to virtualize the body for sanitation + purposes at the time of save / adding new things to the page. +
++ gizmoRegistration(store) +
+The most powerful hook in haxHooks. This fires whenever an element is read in via the appStore and it's definition loaded for use. This hook supplies an instance of the HAXStore which is the internal state management of HAX (written in MobX). You can use this object to do whatever you want to HAX. While seemingly too powerful, here are some examples of past things to leverage this super power for good
+-
+
- + code-sample + - the code-sample tag uses this hook in order to inject additional shortcut logic. If the tag is supplied, things like + ```js + will convert to a JS based code-sample. It also hijacks the baked in support for + ``` + in order to inject a code-sample tag instead of the default + code + tag + +
- supplying "apps" based on tag - + wikipedia-query + and + github-preview + supply custom public API search endpoints based on their tag being loaded. This way you can use the "Media" menu in order to search Github or Wikipedia in HAX just by including these tags in your autoloader block of the appstore. + +
- supplying translatable haxProperties - + meme-maker + and + twitter-embed + supply custom translations for their haxProperties. This means that if you were to edit these elements using the editor in Spanish (es), you would see the fields and example inputs in Spanish (es) as opposed to their English (en) default text supplied by the + static get haxProperties() + method. + +
+ activeElementChanged(element, value) +
+This runs whenever a user activates / selects an element to modify in HAX. This supplies an instance of the element / DOM node that is active as well as if we are active (true) or inactive (false). This hook can be used to modify state / functional aspects of your elements just prior to it receiving activation by hax. An example use-case for this could be preventing default behavior for an element that is a clickable link (see: + ebook-button +). Another possible usage is making pieces of the internal + shadowRoot + + contenteditable +, only while activated (see: + meme-maker +). +
++ editModeChanged(value) +
+This runs on all active nodes in the + hax-body + tag when the editing state of the HAX editor itself changes. If we are now editing, value is + true +, when we go to save / are no longer editing, it is + false +.
++ inlineContextMenu(ceMenu)
+This hook runs after element activation in order to allow elements to supply custom editing buttons and operations to the in-context menu that hovers above active elements. You have access to the instance of the custom elements hax menu element (hax-ce-context) and can add whatever buttons you want at this time with custom callbacks. See multiple-choice + for an example of how you can leverage this. multiple-choice + uses this to add quick buttons for adding and removing potential answers quickly.
++ preProcessNodeToContent(node)
+This runs right before nodes are converted to content in the entire hax-body. This happens when the user has triggered a save event and we are converting the DOM from real nodes into the HTML text that is to be saved / returned to a backend. This hook allows you to do any known data clean up to the element prior to it being converted to HTML. See multiple-choice + for an example of taking a complex data property and converting it to innerHTML children at the time of save for progressive enhancement purposes.
+progressiveEnhancement(element)
+This hook runs WHILE the node is being converted to text and should return a string that will be appended into the innerHTML area of the element. This is an alternative to what you could accomplish during preProcessNodeToContent but want to work with a string based response. See meme-maker + for an example of using this to inject innerHTML which only is for SEO purposes.
++ postProcessNodeToContent(content)
+This hook runs after preProcessNodeToContent and progressiveEnhancement and before the element is returned in the hax-save event. This runs AFTER the node has been converted to content. This is useful for forcible content clean up like regex'ing output for specific words to not leak into output. See video-player + for ensuring there are no internal empty arrays for data is not a required field.
++ preProcessInsertContent(detail)
+This is a hax schema element, our virtual dom node, that is about to be inserted into the hax-body. This allows for custom modification to the data that's about to be converted to a DOM node. See multiple-choice + for an example of ensuring that answer data doesn't bleed through to the page. This hook runs on duplication as well as inserting a node by the user selecting the block.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/item-587de126-437b-4864-a3ea-54078837127c/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/item-587de126-437b-4864-a3ea-54078837127c/index.html new file mode 100644 index 0000000..4b7272e --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/item-587de126-437b-4864-a3ea-54078837127c/index.html @@ -0,0 +1,10 @@ +HAX + 11ty = HAX11ty +! HAX11ty gives you the best of SEO from 11ty while using the HAX editor and the HAXcms theme engine for presenting material. This gives you the SPA capabilities of fast loading routes in HAXcms but reload the page and it loads a physical file for high SEO ala 11ty!
+Create a new repository from hax11ty +
+It even has github actions support built in! Meaning you can check out the mini-doc site for HAX11ty + which is self-updated when we update the docs / repo for HAX11ty.
+This video shows + early work on HAX11ty by Michael Potter
+Templates and layouts allow you to drop in pre-built pieces of content structure. This might be a series of images or an example of content that could be written.
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html
new file mode 100644
index 0000000..32477e4
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html
@@ -0,0 +1,46 @@
+We've created a way to internationalize ANY web component you create. Because this is a complex topic, and we seek to empower anyone, anywhere to work with web components; i18n is a critical piece of accessibility and improving knowledge access on the web. Doing so without requiring a framework driven approach, or even knowing how our element will be used in production, is a complicated series of decisions.
+This blog series details these decisions +I18NMixin
+-
+
- + Install the mixin via yarn or npm: yarn add @lrnwebcomponents/i18n-manager + +
- + create a folder in your element called /locales + +
- create a file called my-element.es.json for the spanish translation of your element. Japanese would be my-element.ja.json for example. +
This invokes a dependency on our manager which you might not want to have in your element. If you want to do a similar approach but without dependencies, you just have to feed a custom event to our manager. You'll still have to use the convention for translatable text, but here's how you can invoke the event needed
+Using the vanilla approach, you'll still need to have a /locales directory and the same naming convention. Our mixin just simplifies the integration a bit as well as the timing of what it's initiated but this event registration method will still work within any element that's going to arrive in HAX/HAXcms or any property you make that isn't using HAX at all.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/item-eca7c8a4-393a-4e68-8cb4-440e94683738/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/item-eca7c8a4-393a-4e68-8cb4-440e94683738/index.html new file mode 100644 index 0000000..0bf2f1a --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/item-eca7c8a4-393a-4e68-8cb4-440e94683738/index.html @@ -0,0 +1,4 @@ +Block settings will change contextually based on which block has been selected in the editable area of the page. In this screenshot, a paragraph has been selected and so the icon associated with it is shown as well as the name of the element. If we selected a meme or other tag we'd see contextual settings based on what that HTML element tells HAX should be the editing interface.
+Normal HTML Paragraph Tag
+Meme Tag
+Notice with the meme element that it now has additional fields which when changed are reflected in the page instantly!
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/json-outline-schema/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/json-outline-schema/index.html new file mode 100644 index 0000000..0a31f5d --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/json-outline-schema/index.html @@ -0,0 +1 @@ +My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/json-schema/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/json-schema/index.html new file mode 100644 index 0000000..83fce74 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/json-schema/index.html @@ -0,0 +1,11 @@ +Learn more about JSON Schema + + + on the official website for that standard. JSON Schema provides a way of describing the data contained in a JSON blob so that a form can be built to modify those values. HAX uses this extensively via a tag called eco-json-schema-object + + + and related tags, to turn any json schema definition into a fully two-way data binded form.
+HAX schema + + + is an abstraction that sits on top of JSON Schema in order to provide forms for updating values in your HAX wired elements. If you wanted to extend the types of input fields that HAX has access to then learning JSON Schema would be the best place to start!
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/scavenger-hunt-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/scavenger-hunt-1/index.html new file mode 100644 index 0000000..3116c79 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/scavenger-hunt-1/index.html @@ -0,0 +1,32 @@ +Become part of our dynasty franchise *
*by wearing a cool jersey
+
+
+
+
+We're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next event to join the movement!
+Past winners rocking their merch from completing the hunt!
+- @onelittlebecca + + + + - at DrupalGovCon '19 + + + +
- @JProffitt + + + + - at DrupalGovCon '19 + + +
- @natefollmer
+
+
+ - IRL Aug '19
My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/things-and-stuff/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/things-and-stuff/index.html new file mode 100644 index 0000000..0a31f5d --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/things-and-stuff/index.html @@ -0,0 +1 @@ +My great new content!
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/i-have-issues/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/i-have-issues/index.html new file mode 100644 index 0000000..f8814ae --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/i-have-issues/index.html @@ -0,0 +1,3 @@ +You have a problem or would like to contribute to anything in our universe? That's awesome! All issues, feature requests and general thumbs up should happen in our issue queue on github: https://github.com/elmsln/issues/issues +
+We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless of ability, + platform, +tribe + or income +.
+Will you help us #HAXTheWeb + and in doing so, HAX society?
+Then keep reading; we Got This!
+Live demo
+Seeing is believing! Thanks to Penn State College of Arts & Architecture for sponsoring this demo!
+HAXcms live demo + (admin / admin as login info)
+Developer quick start
+Integrations +
+- NPM + +
- HAX + 11ty +
- WordPress
+
+ / ClassicPress
+
- Drupal 7,8 or 9 + +
- BackdropCMS + +
- GravCMS + +
- HAXcms + +
H +eadless A +uthoring eX +perience (HAX) is a next generation block editor + that works anywhere via web components +!
+What is this?
+HAX works with web component based design assets so you are never tied to HAX. This keeps your design pure +and without adding platform lock-in as content produced by HAX is semantic HTML. Want the video player above this? Then just run this:
+Get involved!
+Join us on our slack channel + and get involved in all things HAX and web components. HAX is an open community of people who love the open web across all platforms.
+Who's involved
+HAX is the brainchild of Bryan Ollendyke, Michael Potter, Nikki Massaro Kaufman and a chorus of contributors. We've had contributions from:
+- Arizona State University (Drupal 8 plugin), The National Archives (UX Audit, Drupal 8 plugin) +
- Penn State Libraries (HAX11ty) +
- Penn State Eberly College of Science (core contributor / maintainers) +
- Penn State Arts and Architecture (core contributors / maintainers) +
Check out the Get involved + page for additional details.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/presentations/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/presentations/index.html new file mode 100644 index 0000000..25cf992 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/presentations/index.html @@ -0,0 +1,4 @@ +This is the youtube playlist + of all things HAXTheWeb
+ +This playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists related to all things ELMS:LN, WCFactory, HAXcms and web components in general.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/elms-ln/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/elms-ln/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/elms-ln/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxcms/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxcms/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxeditor/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxeditor/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxeditor/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxiam/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxiam/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/haxiam/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/index.html new file mode 100644 index 0000000..63a5173 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap-1/index.html @@ -0,0 +1,8 @@ +HAX encompasses many different projects
+This roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements and next steps for the different projects in our wheel house.
+As you can see, there's a lot of planned enhancements to HAXeditor and HAXcms with a lot of additional future capabilities in ELMS:LN as a result of these projects. It's important to understand these relationships through and how innovations flow between them.
+Relationships of major pieces
+HAX has many different parts detailed here, so let's look at the relationship between these pieces before getting into the roadmap. HAX projects are part of the ELMS:LN organization and so ELMS:LN is also included in these roadmap details.
+HAXiam, HAXcms, HAXeditor are three projects that make up the "HAX" name space, all of which benefit from being built on web components. HAXiam is a server technology while HAXcms is a mix of server and front end assets. HAXeditor is fully front-end code which then requires a backend to save and load pages from.
+Below is an image consolidating information found on this site with arrows illustrating flow of innovation. Web components are always our building blocks, usually bubbling up as a need in either ELMS:LN, HAXcms or HAXeditor. From there, HAXeditor influences and improves ELMS:LN and HAXcms. ELMS:LN has a copy of HAXcms inside of it so sees improvements from both platforms. HAXiam just makes sure that copies of HAXcms are generated.
+Now with this foundation you can dig into the different pieces of the project roadmaps.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/elms-ln/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/elms-ln/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/elms-ln/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxcms/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxcms/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxeditor/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxeditor/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxeditor/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxiam/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxiam/index.html new file mode 100644 index 0000000..13d35f6 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/haxiam/index.html @@ -0,0 +1 @@ +Ex uno Plures
\ No newline at end of file diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/index.html new file mode 100644 index 0000000..63a5173 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/roadmap/index.html @@ -0,0 +1,8 @@ +HAX encompasses many different projects
+This roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements and next steps for the different projects in our wheel house.
+As you can see, there's a lot of planned enhancements to HAXeditor and HAXcms with a lot of additional future capabilities in ELMS:LN as a result of these projects. It's important to understand these relationships through and how innovations flow between them.
+Relationships of major pieces
+HAX has many different parts detailed here, so let's look at the relationship between these pieces before getting into the roadmap. HAX projects are part of the ELMS:LN organization and so ELMS:LN is also included in these roadmap details.
+HAXiam, HAXcms, HAXeditor are three projects that make up the "HAX" name space, all of which benefit from being built on web components. HAXiam is a server technology while HAXcms is a mix of server and front end assets. HAXeditor is fully front-end code which then requires a backend to save and load pages from.
+Below is an image consolidating information found on this site with arrows illustrating flow of innovation. Web components are always our building blocks, usually bubbling up as a need in either ELMS:LN, HAXcms or HAXeditor. From there, HAXeditor influences and improves ELMS:LN and HAXcms. ELMS:LN has a copy of HAXcms inside of it so sees improvements from both platforms. HAXiam just makes sure that copies of HAXcms are generated.
+Now with this foundation you can dig into the different pieces of the project roadmaps.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxcms/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxcms/index.html new file mode 100644 index 0000000..c074718 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/haxcms/index.html @@ -0,0 +1,8 @@ +Pure publishing joy
+HAXcms is the slimmest possible Content Management System possible thanks to the awesome power of HAX. HAXcms boils content creation down to a handful of files behind the scenes, all of which are highly readable and small.
+HAXcms works by loading a single "site.json" file which contains all the relationships between the pages in your site. The content of those pages is stored in single html files, which HAX is used as the editor to manipulate. The CMS then acts as a simple server technology to basically update those two files, making for easy publishing.
+HAXcms has publishing baked in for Github pages. Read the documentation + section to get in deeper. This website you're viewing is powered by HAXcms and the edit controls in the bottom right would update the site if this were a live HAXcms implementation (this site is demo'ing the capabilities).
+How HAX fits into your organization
+HAX (and HAXCMS) are trying to lead you to education's "Roku Remote" moment. By that I mean, a world where you have a very simple little box (HAXCMS) that can be controlled in a completely uniform, simple manner (HAX) that actually pulls together a universe of content and media from across your organization. HAX helps bridge the knowledge gap between content creators and content publishers. It eliminates most of the work involved in publishing (that none of us want to do anyway)!
+HAX or HAXeditor is the editor of the future you're using in this site! It's all the editing capabilities you've come for with HAX and the core solution that all other projects are based on here. The most common way of using HAXeditor is via one of it's many integrations. Check out the integrations + page to find one that works best for you
+SO many integrations
+
+ hax has
HAXiam (HAX-I-Am +) is a SaaS platform code base that's used to deploy HAXcms to multiple people. It is an abstraction on the HAXcms code base that enables it to be used by multiple users from a single point of deployment.
+HAXiam leverages the hooks built into HAXcms to allow for integration with Enterprise login providers, making it a perfect fit for organizations looking to provide their users with micro-site publishing.
+It's still early on but you can check out HAXiam on github +.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/index.html new file mode 100644 index 0000000..b1ec2ca --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/solutions/index.html @@ -0,0 +1,18 @@ +Modularity is key to HAX success. Here are some of the solutions that HAX provides which leverage the HAXeditor interface.
HAX editor
+HAX or HAXeditor is the editor of the future you're using in this site! It's all the editing capabilities you've come for with HAX and the core solution that all other projects are based on here. The most common way of using HAXeditor is via one of it's many integrations. Check out the integrations + page to find one that works best for you
+HAXcms
+HAXcms is the slimmest possible Content Management System possible thanks to the awesome power of HAX. HAXcms boils content creation down to a handful of files behind the scenes, all of which are highly readable and small.
+HAXcms works by loading a single "site.json" file which contains all the relationships between the pages in your site. The content of those pages is stored in single html files, which HAX is used as the editor to manipulate. The CMS then acts as a simple server technology to basically update those two files, making for easy publishing.
+HAXcms has publishing baked in for Github pages. Read the documentation + section to get in deeper. This website you're viewing is powered by HAXcms and the edit controls in the bottom right would update the site if this were a live HAXcms implementation (this site is demo'ing the capabilities).
+How HAX fits into your organization
+HAX (and HAXCMS) are trying to lead you to education's "Roku Remote" moment. By that I mean, a world where you have a very simple little box (HAXCMS) that can be controlled in a completely uniform, simple manner (HAX) that actually pulls together a universe of content and media from across your organization. HAX helps bridge the knowledge gap between content creators and content publishers. It eliminates most of the work involved in publishing (that none of us want to do anyway)!
+HAXiam
+HAXiam (HAX-I-Am + ) is a SaaS platform code base that's used to deploy HAXcms to multiple people. It is an abstraction on the HAXcms code base that enables it to be used by multiple users from a single point of deployment.
+HAXiam leverages the hooks built into HAXcms to allow for integration with Enterprise login providers, making it a perfect fit for organizations looking to provide their users with micro-site publishing.
+It's still early on but you can check out HAXiam on github + .
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/try-hax/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/try-hax/index.html new file mode 100644 index 0000000..0413b71 --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/try-hax/index.html @@ -0,0 +1,10 @@ +Live Demo / ways to try hax
+The Penn State's Office of Digital Learning + sponsors the hosting of a HAXcms demo which runs the latest code at all times.
+Address: http://haxcms.do1.demos.elmsln.org/
+
Username / Password: admin / admin
+This resets hourly on the hour so be aware that this is purely for testing capabilities.
+Special note for Penn State users
+If you work at the university and would like to run courses or websites with HAX, you can do this by accessing hax.psu.edu +. This is used to deploy courses and student blogs at the university and is actively supported.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/what-is-hax/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/what-is-hax/index.html new file mode 100644 index 0000000..cf5cdce --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/what-is-hax/index.html @@ -0,0 +1,34 @@ +HAX - Headless Authoring eXperience
+HAX is a WYSIWYG unlike any other. You extend your world by extending the web through the web component standard. HAX has a simple schema and integrations to allow anyone to author that "widget" on any web site.
+This means that developers can fundamentally change the way HTML operates while expressing it in a highly semantic tag structure.
+Let's understand through a silly example
+Web components
+
+ It's "the" platform
How HAX leverages this
+HAX leverages this capability to express advanced functionality through a single tag in order to build itself. Ultimately, HAX is made up of dozens of complex new web component tags. In the end though. It shows up on the interface like +. A single tag that cascades and unpacks a unique interface experience.
+HAX also doesn't understand what it's editing though! It hasn't been built to say, understand the meme-maker tag above. It's been built to edit things
+ in a very general sense. If it's a custom element / DOM object, it could theoretically edit it... if it knew the directions. These directions are emitted from HAX capable elements when the editor sets itself up. The critical implication of this:
- HAX can be extended to understand how to modify just about any custom element! +
- these definitions are limited by the develop more or less creating the rules of the experience +
- the content produced can operate anywhere with or without hax after the fact + +
Wait, how can you say that
+HAX is effectively organizing the HTML of the page just like you could. Let's look at an example of this page's source. Either hit edit and then the "Source View" button or see the screenshot below
+So when this page was built and the files/lego.jpg + file uploaded (drag and drop in a place holder area) we selected the "Full width" image type for rendering. Then, adding a caption in the HAX element panel, we hit insert and HAX writes the properties into the web component and adds it to the DOM it is editing. When you hit save, HAX takes this piece of DOM and converts it into HTML to send to a backend.
+The output has no trace of HAX, meaning that if you can load the web component definition for the full-width-image tag, then you no longer require HAX. It also means that if this content migrates between platforms that have access to HAX, it'll know how to pick up and modify the content after the fact (as long as the web component definition is there).
+In this way, HAX then gets integrated into other platforms by effectively managing the "body" / blob area that makes up the page. The visual assets produced that work with HAX can then be used anywhere in any website.
diff --git a/github-pages-deploy-action-temp-deployment-folder/pages/welcome/why-haxcms-1/index.html b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/why-haxcms-1/index.html new file mode 100644 index 0000000..7bb7dee --- /dev/null +++ b/github-pages-deploy-action-temp-deployment-folder/pages/welcome/why-haxcms-1/index.html @@ -0,0 +1,48 @@ +HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web components.
+
+Features
+- Micro-site manager, so manage multiple sites from a single HAXcms install +
- Each site is powered by static files which live in version control +
- Every change is executed by the front end via HAX / Outline tools +
- Every change is automatically tracked in version control (zip the folder and send it to a friend and it'll work) +
- The "database" is powered by a site.json file that lives with the site +
- All operations write to static files so every change is as if you editing HTML by hand (but you didn't... HAX did) +
- Ability to serve up as a static site on CDNs (this site is on GH pages + a CDN) via Publishing which makes a purely static copy with a service worker and the whole jazz for offline / installable capability (0 config) +
- Build your own themes via custom front end dev if you like or use one of our baked in ones +
It is a flat file generator with a UI and the UI contextually loads based on if you should see it. It's weird, we know, and that's also why we have trouble describing what it is. It's a flat file CMS without tooling required. It's a sustainable way of building and maintaining a "CMS" as it has multiple pages, can handle custom fields, custom themes, but yet it doesn't require infrastructure to keep running beyond PHP / node / Beaker browser to act as a back end to edit the static files.
+It's an organic CMS. A living yet permanent website. It's hacking the limitations of content authoring capabilities. It's why we say, we're HAX The Web.
+Core Principles
+- Support all platforms and devices (CMS, App, etc) +
- Empower authors to write code without ever looking at code +
- All content produced must work with or without HAXeditor available +
- Support older markup, regardless of structure, as best we can +
- HAX will learn the rules of producing elements, it won't dictate them +
- Decentralize all the things, empower all the peoples +
Cross platform
+Because we've adopted the web component + + standard in the development of both HAX (authoring system) and HAXCMS (content management), everything we create and compile via our open tooling + can support about 98.4% of all browser traffic globally without server side rendering. HAXcms also employs a progressive enhancement methodology meaning that it can hit 100% of all browsing traffic with content.
+This means that you can use the latest and greatest of the web and not have to constantly worry about a library changing! The dawn of the age of web components is now, join the revolution!
+Platform support
+- Evergreen
+ browsers
+ (93+% of traffic) - no polyfills!
- IE 11 / Edge <18 / legacy browsers - polyfills with simplified design +
- See F.A.Q. + for a more detailed break out of stats +
No content lock-in
+The elements that make up HAX can be delivered via a CDN or installed locally. This means that the functionality is tied to the browser + + and NOT + + to the platform itself (huh?). Well, think of all the complex functionality of any site you've ever built or used. Then add content to that site. Now move that site (in your mind) to another server. What has to be migrated to maintain the content functioning that isn't actually content?
+For example, take this quiz:
+HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web components.
+
+Features
+- Micro-site manager, so manage multiple sites from a single HAXcms install +
- Each site is powered by static files which live in version control +
- Every change is executed by the front end via HAX / Outline tools +
- Every change is automatically tracked in version control (zip the folder and send it to a friend and it'll work) +
- The "database" is powered by a site.json file that lives with the site +
- All operations write to static files so every change is as if you editing HTML by hand (but you didn't... HAX did) +
- Ability to serve up as a static site on CDNs (this site is on GH pages + a CDN) via Publishing which makes a purely static copy with a service worker and the whole jazz for offline / installable capability (0 config) +
- Build your own themes via custom front end dev if you like or use one of our baked in ones +
It is a flat file generator with a UI and the UI contextually loads based on if you should see it. It's weird, we know, and that's also why we have trouble describing what it is. It's a flat file CMS without tooling required. It's a sustainable way of building and maintaining a "CMS" as it has multiple pages, can handle custom fields, custom themes, but yet it doesn't require infrastructure to keep running beyond PHP / node / Beaker browser to act as a back end to edit the static files.
+It's an organic CMS. A living yet permanent website. It's hacking the limitations of content authoring capabilities. It's why we say, we're HAX The Web.
+Core Principles
+- Support all platforms and devices (CMS, App, etc) +
- Empower authors to write code without ever looking at code +
- All content produced must work with or without HAXeditor available +
- Support older markup, regardless of structure, as best we can +
- HAX will learn the rules of producing elements, it won't dictate them +
- Decentralize all the things, empower all the peoples +
Cross platform
+Because we've adopted the web component + + standard in the development of both HAX (authoring system) and HAXCMS (content management), everything we create and compile via our open tooling + can support about 98.4% of all browser traffic globally without server side rendering. HAXcms also employs a progressive enhancement methodology meaning that it can hit 100% of all browsing traffic with content.
+This means that you can use the latest and greatest of the web and not have to constantly worry about a library changing! The dawn of the age of web components is now, join the revolution!
+Platform support
+- Evergreen
+ browsers
+ (93+% of traffic) - no polyfills!
- IE 11 / Edge <18 / legacy browsers - polyfills with simplified design +
- See F.A.Q. + for a more detailed break out of stats +
No content lock-in
+The elements that make up HAX can be delivered via a CDN or installed locally. This means that the functionality is tied to the browser + + and NOT + + to the platform itself (huh?). Well, think of all the complex functionality of any site you've ever built or used. Then add content to that site. Now move that site (in your mind) to another server. What has to be migrated to maintain the content functioning that isn't actually content?
+For example, take this quiz:
+Core Principles
+- Support all platforms and devices (CMS, App, etc) + +
- Empower authors to write code without ever looking at code + +
- All content produced must work with or without HAXeditor available + +
- Support older markup, regardless of structure, as best we can + +
- HAX will learn the rules of producing elements, it won't dictate them + + +
- Decentralize all the things, empower all the peoples + + +
Cross platform
+Because we've adopted the web component + + + + + + + + + + + + standard in the development of both HAX (authoring system) and HAXCMS (content management), everything we create and compile via our open tooling + can support about 98.4% of all browser traffic globally without server side rendering. HAXcms also employs a progressive enhancement methodology meaning that it can hit 100% of all browsing traffic with content.
+This means that you can use the latest and greatest of the web and not have to constantly worry about a library changing! The dawn of the age of web components is now, join the revolution!
+Platform support
+- Chrome, Safari, Opera, iOS, Android, Firefox - no polyfill, last 3 versions!
- IE 11 / Edge / legacy everything - aggressive polyfills + +
No content lock-in
+The elements that make up HAX can be delivered via a CDN or installed locally. This means that the functionality is tied to the browser + + + + + + + + + + + + and NOT + + + + + + + + + + + + to the platform itself (huh?). Well, think of all the complex functionality of any site you've ever built or used. Then add content to that site. Now move that site (in your mind) to another server. What has to be migrated to maintain the content functioning that isn't actually content?
+For example, take this quiz:
+
+
+
+
+Edit this file by going to theme/theme.html
+Edit the css by going to theme/theme.css
+You can and should delete these messages and you can do anything + you want with this. This stuff is here to be destroyed and replaced. + Welcome to theming without javascript. Woot Woot. +
+ALso, you'll notice that if you write things like `[[`siteTitle`]]` and you'll get the site title. + You can see it in action here as [[siteTitle]]. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/github-pages-deploy-action-temp-deployment-folder/wc-registry.json b/github-pages-deploy-action-temp-deployment-folder/wc-registry.json
new file mode 120000
index 0000000..108ba75
--- /dev/null
+++ b/github-pages-deploy-action-temp-deployment-folder/wc-registry.json
@@ -0,0 +1 @@
+../../wc-registry.json
\ No newline at end of file
diff --git a/ims_xml.xsd b/ims_xml.xsd
new file mode 100755
index 0000000..ba4226c
--- /dev/null
+++ b/ims_xml.xsd
@@ -0,0 +1 @@
+Outdated browser detected
+ + ++ Upgrade your browser to the latest version or download one of these browsers: +
+ + +
- 
-
- Loading hax-the-web
+Loading..
-
+ getPageContent($page); ?>
+
+ Offline ;-(
+
+
+ You appear to be offline
+
+
+
\ No newline at end of file
diff --git a/package.json b/package.json
index ef59e0d..68e0f6d 100644
--- a/package.json
+++ b/package.json
@@ -1,133 +1,20 @@
{
"name": "haxtheweb",
- "version": "2.0.9",
+ "version": "9.0.5",
"description": "Project home and documentation for all things HAX",
"main": "index.html",
- "repository": {
- "type": "git",
- "url": "git@github.com/elmsln/haxtheweb.git"
- },
"author": {
"name": "btopro"
},
"license": "Apache-2.0",
- "dependencies": {
- "@lrnwebcomponents/a11y-gif-player": "^2.0.1",
- "@lrnwebcomponents/aframe-player": "^2.0.1",
- "@lrnwebcomponents/app-datepicker": "^2.0.1",
- "@lrnwebcomponents/citation-element": "^2.0.1",
- "@lrnwebcomponents/code-editor": "^2.0.1",
- "@lrnwebcomponents/deduping-fix": "^2.0.1",
- "@lrnwebcomponents/dl-behavior": "^2.0.1",
- "@lrnwebcomponents/dropdown-select": "^2.0.1",
- "@lrnwebcomponents/eco-json-schema-form": "^2.0.1",
- "@lrnwebcomponents/elmsln-loading": "^2.0.1",
- "@lrnwebcomponents/grafitto-filter": "^2.0.1",
- "@lrnwebcomponents/grid-plate": "^2.0.1",
- "@lrnwebcomponents/hax-body": "^2.0.1",
- "@lrnwebcomponents/hax-body-behaviors": "^2.0.1",
- "@lrnwebcomponents/haxcms-elements": "^2.0.1",
- "@lrnwebcomponents/hero-banner": "^2.0.1",
- "@lrnwebcomponents/image-compare-slider": "^2.0.1",
- "@lrnwebcomponents/license-element": "^2.0.1",
- "@lrnwebcomponents/lrn-aside": "^2.0.1",
-
- "@lrnwebcomponents/lrn-icons": "^2.0.1",
- "@lrnwebcomponents/lrn-math": "^2.0.1",
- "@lrnwebcomponents/lrn-table": "^2.0.1",
- "@lrnwebcomponents/lrn-vocab": "^2.0.1",
- "@lrnwebcomponents/lrndesign-blockquote": "^2.0.1",
- "@lrnwebcomponents/magazine-cover": "^2.0.1",
- "@lrnwebcomponents/materializecss-styles": "^2.0.1",
- "@lrnwebcomponents/md-extra-icons": "^2.0.1",
- "@lrnwebcomponents/media-behaviors": "^2.0.1",
- "@lrnwebcomponents/media-image": "^2.0.1",
- "@lrnwebcomponents/meme-maker": "^2.0.1",
- "@lrnwebcomponents/multiple-choice": "^2.0.1",
- "@lrnwebcomponents/oer-schema": "^2.0.1",
- "@lrnwebcomponents/outline-player": "^2.0.1",
- "@lrnwebcomponents/paper-icon-picker": "^2.0.1",
- "@lrnwebcomponents/paper-input-flagged": "^2.0.1",
- "@lrnwebcomponents/pdf-element": "^2.0.1",
- "@lrnwebcomponents/person-testimonial": "^2.0.1",
- "@lrnwebcomponents/place-holder": "^2.0.1",
- "@lrnwebcomponents/q-r": "^2.0.1",
- "@lrnwebcomponents/responsive-grid": "^2.0.1",
- "@lrnwebcomponents/schema-behaviors": "^2.0.1",
- "@lrnwebcomponents/self-check": "^2.0.1",
- "@lrnwebcomponents/silly-hax-game": "^2.0.1",
- "@lrnwebcomponents/simple-blog": "^2.0.1",
- "@lrnwebcomponents/simple-colors": "^2.0.1",
- "@lrnwebcomponents/simple-concept-network": "^2.0.1",
- "@lrnwebcomponents/stop-note": "^2.0.1",
- "@lrnwebcomponents/task-list": "^2.0.1",
- "@lrnwebcomponents/video-player": "^2.0.1",
- "@lrnwebcomponents/wikipedia-query": "^2.0.1",
- "@polymer/app-localize-behavior": "^3.0.1",
- "@polymer/iron-a11y-keys": "^3.0.0",
- "@polymer/iron-dropdown": "^3.0.0",
- "@polymer/iron-flex-layout": "^3.0.0",
- "@polymer/iron-image": "^3.0.0",
- "@polymer/iron-list": "^3.0.0",
- "@polymer/iron-menu-behavior": "^3.0.0",
- "@polymer/iron-pages": "^3.0.1",
- "@polymer/neon-animation": "^3.0.1",
- "@polymer/paper-button": "^3.0.1",
- "@polymer/paper-card": "^3.0.0",
- "@polymer/paper-checkbox": "^3.0.0",
- "@polymer/paper-dialog": "^3.0.1",
- "@polymer/paper-dialog-scrollable": "^3.0.0",
- "@polymer/paper-dropdown-menu": "^3.0.0",
- "@polymer/paper-icon-button": "^3.0.0",
- "@polymer/paper-input": "^3.0.0",
- "@polymer/paper-item": "^3.0.0",
- "@polymer/paper-listbox": "^3.0.0",
- "@polymer/paper-material": "^3.0.1",
- "@polymer/paper-menu-button": "^3.0.0",
- "@polymer/paper-slider": "^3.0.0",
- "@polymer/paper-styles": "^3.0.0",
- "@polymer/paper-tabs": "^3.0.0",
- "@polymer/paper-toast": "^3.0.0",
- "@polymer/paper-toggle-button": "^3.0.0",
- "@polymer/paper-tooltip": "^3.0.0",
- "@polymer/polymer": "^3.1.0",
- "@vaadin/vaadin-split-layout": "^4.1.0",
- "@vaadin/vaadin-upload": "^4.2.1",
- "@webcomponents/webcomponentsjs": "2.2.10",
- "web-animations-js": "^2.3.1"
- },
"private": false,
"publishConfig": {
"access": "public"
},
- "resolutions": {
- "object-assign": "4.1.1",
- "commander": "2.19.0",
- "readable-stream": "1.1.14",
- "isarray": "1.0.0",
- "source-map": "0.5.7",
- "kind-of": "6.0.2",
- "is-number": "4.0.0",
- "once": "1.4.0",
- "minimist": "1.2.0",
- "ajv": "6.5.5",
- "fast-deep-equal": "2.0.1",
- "json-schema-traverse": "0.4.1",
- "@polymer/app-layout": "3.0.2"
- },
- "devDependencies": {
- "@prettier/plugin-php": "^0.11.0",
- "prettier": "^1.16.4",
- "gulp": "^4.0.2",
- "gulp-terser": "^1.2.0",
- "rollup-plugin-terser": "5.2.0"
- },
"scripts": {
- "lint": "prettier --check 'system/**/*.php' '*.{html,js,php,yml}'",
- "format": "prettier --write 'system/**/*.php' '*.{html,js,php,yml}'",
- "terser": "gulp",
- "start": "yarn run dev",
- "dev": "polymer serve --open --entrypoint dist/dev.html --allow-origin --open-path=/",
- "dev-theme": "cd custom && yarn start"
+ "start": "npm run dev",
+ "ghpages:build": "rm dist && rm assets/babel* && rm build && rm node_modules && rm wc-registry.json",
+ "dev": "npx @haxtheweb/haxcms-nodejs",
+ "dev-theme": "cd custom && npm start"
}
-}
+}
\ No newline at end of file
diff --git a/pages/documentation-1/hax-development/index.html b/pages/documentation-1/hax-development/index.html
index 81a9f7f..19bb4b9 100644
--- a/pages/documentation-1/hax-development/index.html
+++ b/pages/documentation-1/hax-development/index.html
@@ -1,3 +1,23 @@
+
+
+ cd HAXcms/
+ # link node_modules directory to your clone of lrnwebcomponents
+ ln -s ../lrnwebcomponents/node_modules/
+
+
+If you want to see your element changes in a haxcms site we need to setup some sym links to the haxcms directory.
+
+
+ cd sites/my-site/
+ # link dist, build, and node_modules
+ ln -s ../../dist/
+ ln -s ../../build/
+ ln -s ../../node_modules/
+
+
+
# get the code
diff --git a/pages/documentation-1/hax-development/wcfactory-tooling/index.html b/pages/documentation-1/hax-development/wcfactory-tooling/index.html
index bce69b1..056a5d8 100644
--- a/pages/documentation-1/hax-development/wcfactory-tooling/index.html
+++ b/pages/documentation-1/hax-development/wcfactory-tooling/index.html
@@ -1,4 +1,10 @@
+
+ curl -fsSL https://raw.githubusercontent.com/elmsln/WCFactory/master/wcfactoryme.sh -o wcfactoryme.sh && sh wcfactoryme.sh
+
+
+
+ curl -fsSL https://raw.githubusercontent.com/elmsln/HAXcms/master/scripts/haxcmsme.sh -o haxcmsme.sh && sh haxcmsme.sh
+
+
+
# HAX the web and answer the prompts
diff --git a/pages/documentation-1/index.html b/pages/documentation-1/index.html
index a2cb6c4..04c59f5 100644
--- a/pages/documentation-1/index.html
+++ b/pages/documentation-1/index.html
@@ -1,10 +1,26 @@
+
+
+
+
+
-
-
+ globalThis.MicroFrontendRegistryConfig = globalThis.MicroFrontendRegistryConfig || {};
+ globalThis.HAXCMSContext="php";document.body.removeAttribute('no-js');globalThis.__appCDN="./";globalThis.__appForceUpgrade=false;
+
+
\ No newline at end of file
diff --git a/index.php b/index.php
new file mode 100755
index 0000000..c572f6a
--- /dev/null
+++ b/index.php
@@ -0,0 +1,166 @@
+configDirectory . '/config.php';
+ $site = $HAXCMS->loadSite(basename(__DIR__));
+ $page = $site->loadNodeByLocation();
+ $color = 'var(' . $site->manifest->metadata->theme->variables->cssVariable . ', #FF2222)';
+?>
+
+
+
+ getBaseTag(); ?>
+ getSiteMetadata($page); ?>
+ getServiceWorkerScript(null, FALSE, $site->getServiceWorkerStatus()); ?>
+
+
+
+
+getSitePageAttributes();?>>
+
@@ -293,12 +213,9 @@
Loading hax-the-web
+
+
+
+
+ Loading name; ?>..
+
+
+
+
+
+getGaID()) { ?>
+
+
+
+
+
\ No newline at end of file
diff --git a/legacy-outline.html b/legacy-outline.html
index 7bcce05..69b986e 100644
--- a/legacy-outline.html
+++ b/legacy-outline.html
@@ -3,7 +3,7 @@
-
+
-
+
+
+
+ Please use a modern browser to
+ view our website correctly. Update my browser now
+ - HAX development
- HAX11ty
- Query examples
- What is HAX
- Our Mission
- CSS vars
- Concepts
- Add Content
- Core concepts
- HAXcms
- Installation
- Integrations
- Skin a site
- Block settings
- Structure
- Web components
- Documentation
- F.A.Q.
- Scavenger Hunt
- HAX development
- CSS vars
- Concepts
- Add Content
- Core concepts
- hello-world element
- HAXcms
- Installation
- blox
- Get Involved!
- Integrations
- Skin a site
- Block settings
- Structure
- HAX schema
- Solutions
- Web components
- WordPress
- Documentation
- stax
- Search
- UX concepts
- Related technologies
- autoloader
- Templates and Layouts
- Core elements
- F.A.Q.
- Drupal
- Roadmap
- Publishing
- haxHooks
- Presentations
- BackdropCMS
- Scavenger Hunt
- Dev workflows
- Life cycle
- HAXcms
- Internationalization - i18n
- HAX Element Schema
- I have issues
- ClassicPress
- Troubleshooting
- HAX app store
- GravCMS
- Theming
- Creating new ones!
Hax Development Quick Start
+If you want to work on individual components inside hax you need to link the node_modules folders. +Include HAX in your project
The developers docs will lay out the many specifications that make HAX possible including core concepts, different schema's it leverages ad how to define app store spec in order to take integrations further.
We made tooling to publish web components with ease and in any library. It's called WCFactory and while not required, it's the tooling we use for managing HAX and the many related elements in our library.
+Convenience Installation Script
+A factory that churns out web components, library agnostic with a unified development, testing, and build to production pipeline. We want to eliminate the barriers to web component adoption because as of Oct 23rd, 89.18% of all traffic can handle web components with no polyfills. Get it on npm or yarn and get publishing!
diff --git a/pages/documentation-1/haxcms/installation/index.html b/pages/documentation-1/haxcms/installation/index.html index b1913fc..1df9a22 100644 --- a/pages/documentation-1/haxcms/installation/index.html +++ b/pages/documentation-1/haxcms/installation/index.html @@ -1,5 +1,19 @@Generic PHP install directions
Have PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is to create two basic folders). If all goes well you'll see some ASCii art telling you what your password is. HAXcms seeks to be a 0 config installation so if anything didn't work or make sense, just drop us a line in the issue queues.
+ +Quick Start Installation
+Note: This installs ddev and docker on Linux / Mac users if possible and needed. For Windows users + you will need to install Docker Desktop + ( + https://docs.docker.com/docker-for-windows/install/ + ) and one of the following ddev, lando, or docksal as well. +
+Or from Command Line...
Just run this one command and you'll be HAXing the web in no time! This will step you through prompts (which can be scripted via arguments) to feed the backend what it needs to create the few configuration files it uses to load.
HAX may seem complex, but it's built on a series of standards that will never break. As a result of the complexity of these standards, there are things you should know prior to digging into HAXeditor core or any of its related Solutions
-Watch us build!
-Many members of the core development team participate in a show called HAX camp Uncode -.
+Storybook / styles / element listing
+Want to get started with using our various elements? Then check out our robust design storybook + full of elements, examples, and API details.
-Many members of the core development team participate in a show called HAX camp Uncode +.
+Blogging / social
+Here's some social media and blogs to follow for additional writing, tutorials and videos about HAX.
+- btopro +, NikkiMK +, HAXTheWeb +, HAXcamp + twitter accounts +
- YouTube Channel + +
- Dev.to Blog + +
Are web components ready for prime time?
-Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor
+
+ Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor
leverages this approach and standardizes its usage in order to supply an incredible amount of functionality in the browser. We do what the vast majority of CMS provide prior to interfacing with a server. Just HTML files and a h-a-x
tag to understand how to modify content. No. HAX is written such that the Appstore Specification
+ No. HAX is written such that the Appstore Specification
is defining the elements that are available in this site and other demos. Leveraging the autoloader
piece of the spec, you can tell HAX which tags to load. The web component definitions and schema can be kept separate as desired (useful in CMS with editorial workflows / permissions scenarios). No! HAX modifies HTML inside of itself and then exports back to HTML. This means that as long as the web components on your site have definitions, HAX no longer is required to render them! HAX is effectively writing the same HTML you could have by hand. Web components help make it semantic but also ensure that functionality lives with "the platform"; in this case, the platform being the browser. So long as the definitions of the component are in scope of the page, the element will unpack correctly HAX or otherwise. In terms of mission and what they attempt to provide, a click and build website tonight, no-or-minimal-code solution for the masses... they are the same. They both seek to reduce barriers to entry in web expression. HAX takes some critical differences in philosophy of design to Gutenberg both in technical implementation and goals for the open web. HAX seeks to improve web publishing for all systems, HAXcms or otherwise. HAXcms (which this site is constructed in) is but a tiny fraction of the web and we want to empower anyone to improve self expression. We want to improve privacy, self sovereignty, and the individuality of all peoples on the web. HAX seeks to eliminate technical barriers to production, integration and delivery of material on the internet; all of it, not just the expensive CMS part of it. We want to hax-the-web, hence this domain name. Some larger points of different are highlighted below HAX is the brain child of the ELMS:LN team at Pennsylvania State University
. HAX is the authoring solution originally created to power ELMS:LN
and other instructional innovations and was quickly realized for its potential to transform web publishing. We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless of ability,
- platform,
+
+ We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless offfff ability,
+ platform,
tribe
- or income
+ or income
. Will you help us #HAXTheWeb
and in doing so, HAX society? Then keep reading; we Got This! Seeing is believing! Thanks to Penn State College of Arts & Architecture for sponsoring this demo! HAXcms live demo
- (admin / admin as login info)Are web components ready for prime time?
+What's Browser support like?
+What's Browser support like?
-What's Browser support like
Do I have to use the elements HAXeditor supplies?
-Do I have to use the elements HAXeditor supplies?
+Do these elements require HAX to operate?
+Do these elements require HAX to operate?
How does this compare to the WordPress Gutenberg plugin?
+How does this compare to the WordPress Gutenberg plugin?
How does this compare to th
-How does this compare to th
should work
Where did this come from?
+Where did this come from?
Where did this come from?Michael Potter (@hey__mp
) - Core Developer
Live demo
-Developer quick start
-Integrations
+npm install --save @lrnwebcomponents/wysiwyg-hax
+yarn add @lrnwebcomponents/wysiwyg-hax
+pnpm add @lrnwebcomponents/wysiwyg-hax
Integrations
-- NPM
+
-
H -eadless A -uthoring eX -perience (HAX) is a next generation block editor - that works anywhere via web components -!
-What is this?
-+ + HAX works with web component based design assets so you are never tied to HAX. This keeps your design pure and without adding platform lock-in as content produced by HAX is semantic HTML. Want the video player above this? Then just run this:
-# the video-player tag works with HAX but works ANYWHERE regardless of it + # the video-player tag works with HAX but works ANYWHERE regardless of it yarn add @lrnwebcomponents/video-player -Get involved!
+Get involved!
Join us on our slack channel and get involved in all things HAX and web components. HAX is an open community of people who love the open web across all platforms.
-Who's involved
-HAX is the brainchild of Bryan Ollendyke, Michael Potter, Nikki Massaro Kaufman and a chorus of contributors. We've had contributions from:
-- Arizona State University (Drupal 8 plugin), The National Archives (UX Audit, Drupal 8 plugin) -
- Penn State Libraries (HAX11ty) +
- Arizona State University (Drupal 8 plugin) +
- The National Archives (UX Audit, Drupal 8 plugin) +
- Penn State Libraries (HAX11ty)
- Penn State Eberly College of Science (core contributor / maintainers)
- Penn State Arts and Architecture (core contributors / maintainers)
-
-
Internationalization - i18n - https://haxtheweb.org//item-cdd303d0-4490-4433-94fa-0e78cf849e80 -- We've created a way to internationalize ANY web component you create. Because this is a complex topic, and we seek to empower anyone, anywhere to work with web components; i18n is a critical piece of accessibility and improving knowledge access on the web. Doing so without requiring a framework driven approach, or even knowing how our element will be used in production, is a complicated series of decisions. -This blog series details these decisions - -I18NMixin
--
-
- - Install the mixin via yarn or npm: yarn add @lrnwebcomponents/i18n-manager - -
- - create a folder in your element called /locales - -
- create a file called my-element.es.json for the spanish translation of your element. Japanese would be my-element.ja.json for example. -
- import { I18NMixin } from "@lrnwebcomponents/i18n-manager/lib/I18NMixin.js"; -class MyElement extends I18NMixin(HTMLElement) { - constructor() { - this.t = { - stuff: "Stuff" - }; - this.registerLocalization({ - context: this, - basePath: import.meta.url, - locales: ["es", "ja"], - }); - connectedCallback() { - this.render(); - } - render() { - this.innerHTML = `${this.t.stuff}`; - } - } -} - -This invokes a dependency on our manager which you might not want to have in your element. If you want to do a similar approach but without dependencies, you just have to feed a custom event to our manager. You'll still have to use the convention for translatable text, but here's how you can invoke the event needed
-- window.dispatchEvent( - new CustomEvent("i18n-manager-register-element", { - detail: { - namespace: "my-element.haxProperties", - localesPath: decodeURIComponent(import.meta.url) + "/../locales", - locales: ["es"], - }, - }) - ); - -Using the vanilla approach, you'll still need to have a /locales directory and the same naming convention. Our mixin just simplifies the integration a bit as well as the timing of what it's initiated but this event registration method will still work within any element that's going to arrive in HAX/HAXcms or any property you make that isn't using HAX at all.
- ]]> -- https://haxtheweb.org//item-cdd303d0-4490-4433-94fa-0e78cf849e80 -Wed, 07 Apr 2021 14:24:50 +0000 -
- -
-
haxHooks - https://haxtheweb.org//item-44cc230b-07db-442a-90cf-687e2d089a5d -- Elements can integrate deeply into HAX state management using what we call "hax hooks". By supplying a method on your web component like - haxHooks() - you are magically able to tap into different life-cycle steps within the HAX editor. - - -Because of the simplicity and power of - haxHooks - this may not be an exhaustive list and +
-+ hax-the-web + https://haxtheweb.org//rss.xml +Project home and documentation for all things HAX +Copyright (C) 2024 https://haxtheweb.org/ +en-us +1970-01-20T23:35:16.452Z +- Blog posts about this topic -
--
-
-
- haxHooks(): How elements can supply their own editing experience in HAX now!
-
-
- -
- haxHooks: webcomponents that ship their own editing UX
-
-
-
-Code example
-- This is a basic example in which each of the strings you'd then implement as their own async - callbacks. async - / await - allows HAX to safely defer to your element to do whatever it wants to the DOM / internal structure of that callback, without disrupting element activation or conversion of DOM structure to HAX Element Schema, what it uses to virtualize the body for sanitation - purposes at the time of save / adding new things to the page. -
-- -haxHooks() { - return { - activeElementChanged: "haxactiveElementChanged", - editModeChanged : "haxeditModeChanged", - inlineContextMenu: "haxinlineContextMenu", - gizmoRegistration: "haxgizmoRegistration", - preProcessNodeToContent : "haxpreProcessNodeToContent", - postProcessNodeToContent : "haxpostProcessNodeToContent", - progressiveEnhancement: "haxprogressiveEnhancement", - preProcessInsertContent : "haxpreProcessInsertContent" - }; -} -- gizmoRegistration(store) -
-The most powerful hook in haxHooks. This fires whenever an element is read in via the appStore and it's definition loaded for use. This hook supplies an instance of the HAXStore which is the internal state management of HAX (written in MobX). You can use this object to do whatever you want to HAX. While seemingly too powerful, here are some examples of past things to leverage this super power for good
--
-
- - code-sample - - the code-sample tag uses this hook in order to inject additional shortcut logic. If the tag is supplied, things like - ```js - will convert to a JS based code-sample. It also hijacks the baked in support for - ``` - in order to inject a code-sample tag instead of the default - code - tag - -
- supplying "apps" based on tag - - wikipedia-query - and - github-preview - supply custom public API search endpoints based on their tag being loaded. This way you can use the "Media" menu in order to search Github or Wikipedia in HAX just by including these tags in your autoloader block of the appstore. - -
- supplying translatable haxProperties - - meme-maker - and - twitter-embed - supply custom translations for their haxProperties. This means that if you were to edit these elements using the editor in Spanish (es), you would see the fields and example inputs in Spanish (es) as opposed to their English (en) default text supplied by the - static get haxProperties() - method. - -
- activeElementChanged(element, value) -
-This runs whenever a user activates / selects an element to modify in HAX. This supplies an instance of the element / DOM node that is active as well as if we are active (true) or inactive (false). This hook can be used to modify state / functional aspects of your elements just prior to it receiving activation by hax. An example use-case for this could be preventing default behavior for an element that is a clickable link (see: - ebook-button -). Another possible usage is making pieces of the internal - shadowRoot - - contenteditable -, only while activated (see: - meme-maker -). -
-- editModeChanged(value) -
-This runs on all active nodes in the - hax-body - tag when the editing state of the HAX editor itself changes. If we are now editing, value is - true -, when we go to save / are no longer editing, it is - false -.
-- inlineContextMenu(ceMenu)
-This hook runs after element activation in order to allow elements to supply custom editing buttons and operations to the in-context menu that hovers above active elements. You have access to the instance of the custom elements hax menu element (hax-ce-context) and can add whatever buttons you want at this time with custom callbacks. See multiple-choice - for an example of how you can leverage this. multiple-choice - uses this to add quick buttons for adding and removing potential answers quickly.
-- preProcessNodeToContent(node)
-This runs right before nodes are converted to content in the entire hax-body. This happens when the user has triggered a save event and we are converting the DOM from real nodes into the HTML text that is to be saved / returned to a backend. This hook allows you to do any known data clean up to the element prior to it being converted to HTML. See multiple-choice - for an example of taking a complex data property and converting it to innerHTML children at the time of save for progressive enhancement purposes.
-progressiveEnhancement(element)
-This hook runs WHILE the node is being converted to text and should return a string that will be appended into the innerHTML area of the element. This is an alternative to what you could accomplish during preProcessNodeToContent but want to work with a string based response. See meme-maker - for an example of using this to inject innerHTML which only is for SEO purposes.
-- postProcessNodeToContent(content)
-This hook runs after preProcessNodeToContent and progressiveEnhancement and before the element is returned in the hax-save event. This runs AFTER the node has been converted to content. This is useful for forcible content clean up like regex'ing output for specific words to not leak into output. See video-player - for ensuring there are no internal empty arrays for data is not a required field.
-- preProcessInsertContent(detail)
-This is a hax schema element, our virtual dom node, that is about to be inserted into the hax-body. This allows for custom modification to the data that's about to be converted to a DOM node. See multiple-choice - for an example of ensuring that answer data doesn't bleed through to the page. This hook runs on duplication as well as inserting a node by the user selecting the block.
- ]]> -- https://haxtheweb.org//item-44cc230b-07db-442a-90cf-687e2d089a5d -Wed, 07 Apr 2021 13:32:25 +0000 -
- -
- haxHooks(): How elements can supply their own editing experience in HAX now!
-
-
-
HAX11ty - https://haxtheweb.org//item-587de126-437b-4864-a3ea-54078837127c -- HAX + 11ty = HAX11ty -! HAX11ty gives you the best of SEO from 11ty while using the HAX editor and the HAXcms theme engine for presenting material. This gives you the SPA capabilities of fast loading routes in HAXcms but reload the page and it loads a physical file for high SEO ala 11ty! - -Create a new repository from hax11ty -
-It even has github actions support built in! Meaning you can check out the mini-doc site for HAX11ty - which is self-updated when we update the docs / repo for HAX11ty.
-This video shows - early work on HAX11ty by Michael Potter
-- - ]]> -- https://haxtheweb.org//item-587de126-437b-4864-a3ea-54078837127c -Mon, 17 Aug 2020 19:01:17 +0000 -
- -
-
Block settings - https://haxtheweb.org//item-eca7c8a4-393a-4e68-8cb4-440e94683738 -- Block settings will change contextually based on which block has been selected in the editable area of the page. In this screenshot, a paragraph has been selected and so the icon associated with it is shown as well as the name of the element. If we selected a meme or other tag we'd see contextual settings based on what that HTML element tells HAX should be the editing interface. - -Normal HTML Paragraph Tag
-Meme Tag
-Notice with the meme element that it now has additional fields which when changed are reflected in the page instantly!
- ]]> -- https://haxtheweb.org//item-eca7c8a4-393a-4e68-8cb4-440e94683738 -Mon, 17 Aug 2020 18:41:49 +0000 -
- -
-
Templates and Layouts - https://haxtheweb.org//item-aa589faa-e860-4221-82fa-df6d57328ac2 -- Templates and layouts allow you to drop in pre-built pieces of content structure. This might be a series of images or an example of content that could be written. - - ]]>
- - https://haxtheweb.org//item-aa589faa-e860-4221-82fa-df6d57328ac2 -Mon, 17 Aug 2020 18:41:49 +0000 -
- -
-
Roadmap - https://haxtheweb.org//welcome/roadmap-1 -- HAX encompasses many different projects - -This roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements and next steps for the different projects in our wheel house.
-As you can see, there's a lot of planned enhancements to HAXeditor and HAXcms with a lot of additional future capabilities in ELMS:LN as a result of these projects. It's important to understand these relationships through and how innovations flow between them.
-Relationships of major pieces
-HAX has many different parts detailed here, so let's look at the relationship between these pieces before getting into the roadmap. HAX projects are part of the ELMS:LN organization and so ELMS:LN is also included in these roadmap details.
-HAXiam, HAXcms, HAXeditor are three projects that make up the "HAX" name space, all of which benefit from being built on web components. HAXiam is a server technology while HAXcms is a mix of server and front end assets. HAXeditor is fully front-end code which then requires a backend to save and load pages from.
-Below is an image consolidating information found on this site with arrows illustrating flow of innovation. Web components are always our building blocks, usually bubbling up as a need in either ELMS:LN, HAXcms or HAXeditor. From there, HAXeditor influences and improves ELMS:LN and HAXcms. ELMS:LN has a copy of HAXcms inside of it so sees improvements from both platforms. HAXiam just makes sure that copies of HAXcms are generated.
-Now with this foundation you can dig into the different pieces of the project roadmaps.
- ]]> -- https://haxtheweb.org//welcome/roadmap-1 -Thu, 08 Aug 2019 18:53:07 +0000 -
- -
-
ClassicPress - https://haxtheweb.org//integrations-1/classicpress-1 -- ClassicPress - is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original! - --
-
- Get the HAX plugin - from the wordpress registry -
- Go to edit / create a page/post and you are HAXing -
Installation video
-This shows installing it manually if you can't get it from the wordpress store!
-- ]]> - - https://haxtheweb.org//integrations-1/classicpress-1 -Thu, 08 Aug 2019 15:43:29 +0000 -
- -
-
HAXcms - https://haxtheweb.org//welcome/why-haxcms-1 -- - -HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web components.
-
-
- -Features
-- Micro-site manager, so manage multiple sites from a single HAXcms install -
- Each site is powered by static files which live in version control -
- Every change is executed by the front end via HAX / Outline tools -
- Every change is automatically tracked in version control (zip the folder and send it to a friend and it'll work) -
- The "database" is powered by a site.json file that lives with the site -
- All operations write to static files so every change is as if you editing HTML by hand (but you didn't... HAX did) -
- Ability to serve up as a static site on CDNs (this site is on GH pages + a CDN) via Publishing which makes a purely static copy with a service worker and the whole jazz for offline / installable capability (0 config) -
- Build your own themes via custom front end dev if you like or use one of our baked in ones -
It is a flat file generator with a UI and the UI contextually loads based on if you should see it. It's weird, we know, and that's also why we have trouble describing what it is. It's a flat file CMS without tooling required. It's a sustainable way of building and maintaining a "CMS" as it has multiple pages, can handle custom fields, custom themes, but yet it doesn't require infrastructure to keep running beyond PHP / node / Beaker browser to act as a back end to edit the static files.
-It's an organic CMS. A living yet permanent website. It's hacking the limitations of content authoring capabilities. It's why we say, we're HAX The Web.
-Core Principles
-- Support all platforms and devices (CMS, App, etc) -
- Empower authors to write code without ever looking at code -
- All content produced must work with or without HAXeditor available -
- Support older markup, regardless of structure, as best we can -
- HAX will learn the rules of producing elements, it won't dictate them -
- Decentralize all the things, empower all the peoples -
Cross platform
-Because we've adopted the web component - - standard in the development of both HAX (authoring system) and HAXCMS (content management), everything we create and compile via our open tooling - can support about 98.4% of all browser traffic globally without server side rendering. HAXcms also employs a progressive enhancement methodology meaning that it can hit 100% of all browsing traffic with content.
-This means that you can use the latest and greatest of the web and not have to constantly worry about a library changing! The dawn of the age of web components is now, join the revolution!
-Platform support
-- Evergreen
- browsers
- (93+% of traffic) - no polyfills!
- IE 11 / Edge <18 / legacy browsers - polyfills with simplified design -
- See F.A.Q. - for a more detailed break out of stats -
No content lock-in
-The elements that make up HAX can be delivered via a CDN or installed locally. This means that the functionality is tied to the browser - - and NOT - - to the platform itself (huh?). Well, think of all the complex functionality of any site you've ever built or used. Then add content to that site. Now move that site (in your mind) to another server. What has to be migrated to maintain the content functioning that isn't actually content?
-For example, take this quiz:
-- ]]> - - https://haxtheweb.org//welcome/why-haxcms-1 -Wed, 24 Jul 2019 12:45:22 +0000 -
- -
-
Scavenger Hunt - https://haxtheweb.org//scavenger-hunt-1 -- Become part of our dynasty franchise * -
*by wearing a cool jersey - - - - -We're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next event to join the movement!
-Past winners rocking their merch from completing the hunt!
-- @onelittlebecca - - - - - at DrupalGovCon '19 - - - -
- @JProffitt - - - - - at DrupalGovCon '19 - - -
- @natefollmer
-
-
- - IRL Aug '19
- - ]]> - - https://haxtheweb.org//scavenger-hunt-1 -Wed, 24 Jul 2019 12:15:37 +0000 -
- -
-
Life cycle - https://haxtheweb.org//documentation-1/haxcms/life-cycle -- This is a general life cycle that happens when HAXcms "boots up". When web components are unpacking the contents of what to do it generally will work this way. - -- page load, should it be no-js or a web component delivered, preflight -
- haxcms-site-builder loads site.json, reads JSON Outline Schema and starts to bootstrap that into a theme, items, title, etc -
- Appends a haxcms-editor-builder tag which checks for "context" -
- Context is established based on global values for php, nodejs, beaker, etc
- Uses a login end point to check if there's a JWT in the user's local data -
- When it finds a backend, it injects a tag to bridge that backend - -
- HAXeditor gets injected into the correct place in the theme which then all of that unpacks and does its thing -
Event driven architecture
-HAXcms allows for jumping in at different core operational steps and reacting to these changes based on an event driven design pattern. This means that an event "fires" in PHP, much like it does in JavaScript and code written to react to it can make changes at that point in the operation.
-Here is an example from HAXiam which implements custom configuration event listeners
-// file included which has the class in question -include_once str_replace('_iamConfig/HAXcmsConfig.php', '', __FILE__) . '/system/lib/IAM.php'; -// in the configuration file HAXcmsConfig.php -// this adds an event listener for the haxcms-jwt-get event -// and then says to pass the data in question to class $IAM->getJwtUser(); -$HAXCMS->addEventListener('haxcms-jwt-get', array($IAM, 'getJwtUser')); -// later on in additionally included code -class IAM { -/** - * Callback for event: haxcms-jwt-get - */ - public function getJwtUser(&$token) { - if ($this->enterprise->userVar) { - $token['user'] = $this->enterprise->userVar; - } - } -} -// this ensures that there is a global $IAM object -// it also ensures there's an instance so that when our above -// listener fires it'll correctly associate to this code -global $IAM; -$IAM = new IAM(); -Core listeners
-Core listeners to influence how the data is constructed. You can add these to your _config/config.php file
-- haxcms-init - - just after HAXcms bootstraps its initial configuration -
- haxcms-site-metadata - - when constructing metadata block at the top of the document -
- haxcms-connection-settings - - for authorized users, this is the block of end points for connecting to and modifying HAXcms logic as far as where data flows. -
Enterprise integrations and SSO
-The following hooks allow for supplanting the HAXcms (intentionally) simplistic login system. This allows you to do custom integrations for your organization. HAXiam implements many of these - if you need specific examples.
-- haxcms-login-test - - when a login didn't pass our simplistic built in checks. Useful for enterprise integrations and other SSO methods of access -
- haxcms-validate-user - - same as login-test except this fires to validate every transaction to ensure the user name matches when decoding the JWT -
- haxcms-jwt-get - - when we ask for the JWT. This allows SSO to supply the token manually via a different methodology than our core one -
- haxcms-refresh-token-get - - when our connection is deemed needing to refresh, this supplies the refresh token for when and what that looks like -
- https://haxtheweb.org//documentation-1/haxcms/life-cycle -Fri, 05 Apr 2019 20:27:27 +0000 -
- -
-
I have issues - https://haxtheweb.org//welcome/i-have-issues -- You have a problem or would like to contribute to anything in our universe? That's awesome! All issues, feature requests and general thumbs up should happen in our issue queue on github: https://github.com/elmsln/issues/issues - - -- ]]> - - https://haxtheweb.org//welcome/i-have-issues -Mon, 25 Mar 2019 23:24:55 +0000 -
- -
-
Troubleshooting - https://haxtheweb.org//documentation-1/haxcms/troubleshooting -- These are some common issues / resolutions in HAXcms related to installation, publishing, etc. - -I installed HAXcms and forgot my password
-Your username and password can be found in _config/config.php on the server (assuming local development)
-I clicked login and nothing happened and now I'm locked out.
-- Clear your browser cache. A cookie is set that might be invalid. - -
- Open a new browser and try to login again -
I clicked publish and nothing happened
-- Publishing can take up to a minute or so at times since it's creating a commit, rewriting files and then the front end is waiting on the push to github before it triggers a successful response. -
- If it did fail to publish, you might not have git setup. Click the gear icon on the dashboard (site listing) and ensure you've setup github / git integration correctly. -
Realize that everything is just a file and that our json outline schema is very easy to read. So if there's an issue with something related to publishing, check _sites/mysite/site.json for publishing, then _config/config.json. All settings and variables cascade in this way. Settings are stored globally, then replicated locally to allow them to be pealed off and more easily imported / exported into other setups.
- ]]> -- https://haxtheweb.org//documentation-1/haxcms/troubleshooting -Mon, 25 Mar 2019 23:16:04 +0000 -
- -
-
Skin a site - https://haxtheweb.org//documentation-1/haxcms/theming/skin-a-site -- Theme skinning is the easiest way to build a decent looking theme in HAXcms. This method is geared toward people that know CSS and HTML but can't get into the weeds of web components or javascript. - -Workflow
-- Make a new site in the HAXcms UI - -
- Select "Custom theme" as your theme -
- In the file system go to _sites/mynewsite -/theme -
- Edit theme.html to modify the structure -
- Edit theme.css to modify the design -
This is the easiest way to skin HAXcms to your liking. It's able to ship and work in CDNs and is the minimal barrier to entry for those used to seeing HTML and CSS files that they can touch and see the change. It requires no tooling to utilize either!
-- ]]> - - https://haxtheweb.org//documentation-1/haxcms/theming/skin-a-site -Sat, 23 Mar 2019 15:21:47 +0000 -
- -
-
Dev workflows - https://haxtheweb.org//documentation-1/haxcms/theming/dev-workflows -- Our development workflow is as follows (for themes) - -- All custom theme work happens in your _config directory - -
- Make my-theme.js, pull everything together, either in this directory or in a wcfactory - catalog of elements you've made -
- Reference this in you _config/my-custom-elements.js element -
- Update the _config/config.json block that says themes - to include something like... -
"themes": { - "odl-haxtheme": { - "element": "odl-haxtheme", - "path": "@myorganization/odl-haxtheme/odl-haxtheme.js", - "name": "Eberly ODL" - } - }, - -This tells HAXcms UI that you can now select the theme (but don't yet, it won't be valid)
-Local development workflow during theme development
-We use polymer cli to serve up and work on web components locally and while you don't have to, it's recommended as part of the WCFactory workflow.
-- Make a new site in the HAXcms UI - -
- Go to _sites/mynewsite and run polymer serve --npm --open --entrypoint dist/dev.html - - -
- Adjust the URL that opens to only be the IP address with no path after it -
- You'll see your site open up for local development work, which will be leveraging any assets referenced in your node_modules directory at the HAXcms project root. -
- To add / install new assets run yarn (or npm) add @what/ever-you-want --save -, just like you would any other project you work on in FE dev -
- edit your site's site.json manually to update the theme to point to the theme location your actively working on -
- Develop away until it is to your liking -
Shipping the theme
-To ship the theme, you'll need to do a polymer build routine
-important note
-This currently forks you from the original source of HAXcms core (because it will recompile the assets). If you're ok with this cool, just know we're trying to find ways around this involving rollup -.
-- Go to the HAXcms project root - -
- run polymer build - - -
- Copy the build directory and go to your site -
- Delete the symlink and replace it with your build directory -
- Now you can publish via the UI so long as you do not leverage a CDN -
The future
-Admittedly, the full on custom theme / web component development workflow is rough. It's hard to maintain a built copy in a modular system without tooling. In the future we plan on having tooling workflows built directly into WCFactory that allow you to streamline the development and creation of HAXcms themes.
-Current limitations
-You can't leverage existing CDNs (like webcomponents.psu.edu and whatever else is out there) that are pegged to the HAXcms project's source. You'll be creating a custom theme which then creates a custom build in effect so you'll want to ensure that you have some place that you can host the assets in order to power your site.
- ]]> -- https://haxtheweb.org//documentation-1/haxcms/theming/dev-workflows -Sat, 23 Mar 2019 13:58:38 +0000 -
- -
-
CSS vars - https://haxtheweb.org//documentation-1/haxcms/theming/css-vars -- CSS can be modified via CSS variables -. CSS variables create a happy middle ground between the constraints of Shadow DOM (namely that styles are fully encapsulated) and designers wanting flexibility and control over design. We leverage CSS variables heavily in our template layer to allow you to "skin" just about any theme we have already. - -A note about @apply
-Unlike normal css variables, Polymer (the library we build our theme layer on) supports a convention for CSS variables that operate a bit more like Saas mixins. You can write blocks of code like @apply --my-variable-blob; - which will then allow someone to mix in and apply whatever valid CSS attributes they want at that level. You can see several implemented below (both CSS variables and @apply blocks).
-Example
-This is an example from the haxcms-basic-theme -which forms a clean baseline for most sites.
-// this is from the haxcms-basic-theme -site-top-menu { - --site-top-menu-bg: #37474f; - --site-top-menu-link-color: #ffffff; - --site-top-menu-indicator-color: #ffffff; - --site-top-menu-link-active-color: var( - --haxcms-basic-theme-accent-color - ); - --site-top-menu-indicator-arrow: 8px; -} -site-children-block { - --site-children-block-button: { - color: #ffffff; - } - --site-children-block-button-active: { - background-color: #37474f; - color: var(--haxcms-basic-theme-accent-color); - } -} -.left-col { - min-height: 250px; - border: 2px solid black; - background-color: #37474f; - color: white; - padding: 16px; -} -site-active-title { - display: inline-flex; - --site-active-title-heading: { - font-family: "Montserrat", "Helvetica", "Tahoma", "Geneva", "Arial", - sans-serif; - font-size: 16px; - line-height: 32px; - margin-bottom: 8px; - text-rendering: optimizelegibility; - font-weight: 600; - color: white; - } -} - - ]]> -- https://haxtheweb.org//documentation-1/haxcms/theming/css-vars -Sat, 23 Mar 2019 13:58:38 +0000 -
- -
-
Query examples - https://haxtheweb.org//documentation-1/haxcms/theming/core-elements/query-examples -- Hold up there. You didn't cover any of the query tags in that last section! - - -Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that now. The site- - - - - query elements are incredibly powerful aspects of HAXcms theming that deserve their own section anyway.
-site-query - -
-Code Example
-< site-query -result="{{result}}" -conditions='{"metadata.tag": "funny"}' -> -< /site-query> - - -- -- Spoken Example
-"Give me all of the
-Give me all of the pages who have a tag "Funny" - -When it's useful
-Always. This is by far the most powerful element in our library. It can query the site structure and effectively return anything, anywhere that matches the criteria. It is for exact criteria matching though so you won't be getting children of page X unless you specifically requested them.
-This is great for getting things like getting all the pages that don't have parents (top level items) which is exactly how the site-top-menu - - tag does it in conjunction with a dom-repeat tag (in that example).
-Caveats
-- This doesn't render anything by itself - - -
- You have to then know how to do a two way template bind (Polymer convention looking like {{result}} - -or know how to use javascript in order to bind the results to visual output - -
- Its incredibly powerful - -
A menu slice query is one which takes part of a hierarchy and chops it out to return the items.
-< - site-query-menu-slice - result="{{__items}}" - dynamic-methodology="[[dynamicMethodology]]" - start="[[start]]" - end="[[end]]" - parent="[[parent]]" - fixed-id="[[fixedId]]" - > - < /site-query-menu-slice> - -- - - - -Spoken example
-Give me all child pages -
-that are 2 to 4 levels deep. -Delivered results
-What type of query is this leveraging again? - site-query-menu-slice - -Dynamic leveling
-The dynamic leveling flag would allow you to create a query that analyzes the current active item (as example). And then say "Always give me 2-3 levels below this". In that instance you've got a dynamic sub-set of children being returned.
-When it's useful
-This can be useful for a block that always shows the children of the current page in a documentation site.
-site-render-query - -
-A site render query attempts to standardize the practice of wiring site-query up to something visual. It requires you supply something visual to get going and has the unfortunate limitation though that what you render must not be dynamic in nature.
-Example
-- - --- -- ---description: [[item.description]]-location: [[item.location]]-changed: [[item.metadata.updated]]---Set as active -
-- When it's useful
-When you have a static set of items you want to query once and have it be dynamic based on site infrastructure yet not be changing dynamically during site view.
-Possible usage
-As we haven't rolled this into any themes at the time, this could be useful for placing a "latest posts" block or "upcoming events" block. Anything that's dynamic based on the data being passed in but yet unchanging once it's loaded. Think of this as a simple "views" construct if you are from the Drupal worldview.
- ]]> -- https://haxtheweb.org//documentation-1/haxcms/theming/core-elements/query-examples -Sat, 23 Mar 2019 13:58:38 +0000 -
- -
-
Web components - https://haxtheweb.org//documentation-1/haxcms/theming/web-components -- Do you know full on web component development? Well, you can build a new theme from scratch. The best way to learn is by picking a part some of our examples. For this we'll analyze the haxcms-slide-theme - -. - -Import classes / web components
-import { html, PolymerElement } from "@polymer/polymer/polymer-element.js"; -import { HAXCMSTheme } from "@lrnwebcomponents/haxcms-elements/lib/core/HAXCMSThemeWiring.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-title.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-print-button.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/active-item/site-active-title.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-dot-indicator"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu-button.js"; -import "@polymer/paper-icon-button/paper-icon-button.js"; -import "@polymer/iron-icons/iron-icons.js"; -import "@polymer/paper-tooltip/paper-tooltip.js"; -import "@lrnwebcomponents/simple-colors/simple-colors.js"; -import "@lrnwebcomponents/hax-body/lib/hax-shared-styles.js"; - -As you can see this theme imports a few basic components helpful in the development of most themes. First we import PolymerElement and the HAXCMSTheme mix-in from our theme wiring library. Theme wiring provides a basis for wiring any custom element into the state management of HAXcms, typically without having to deal with any concepts of state!
-Mix-ins
-class HAXCMSSlideTheme extends HAXCMSTheme(PolymerElement) { - -Next we get the mix-in statement. Note how HAXCMSTheme wraps the PolymerElement class, thereby giving us a mix of the two together.
-HAXCMSTheme mix-in class
-You can learn more about what the mix-in class provides by digging into the HAXCMSThemeWiring.js - - class. This class bridges the HAXcms store (written in mobx) with the design layer. This way you can leverage anything in the store by writing the polymer convention for referencing a data bound variable in the template.
-Here's the variables you'll commonly see - - in our themes, direct from the store with an example of what a dom bind of that would look like in a template
-[[siteTitle]]
-[[ancestorTitle
-[[parentTitle]]
-[[activeTitle]]
-- [[activeItemFields.images.0.url]] --That last line with activeItemFields is part of the raw power under the hood of this approach. You can use HAXcms to create field definitions (in HAXschema - -) that then extend the capabilities of your pages.
-Required CSS
-There is one small required block of CSS when doing web component / theme development for HAXcms. It is the following:
-/** - * Hide the slotted content during edit mode. This must be here to work. - */ -:host([edit-mode]) #slot { - display: none; -} - -This helps ensure that when your user clicks the edit button that they see the HAXeditor as opposed to the body of content they are currently working with. Then when they hit save, the HAXeditor sends the content to the backend which then updates the front end and they see the changes. This CSS ensures that it isn't visible during editing.
-Required HTML
-Related to the CSS, the following block of HTML must appear in your template somewhere (or in the case of simple-blog -, an element leveraged by your theme). You can make this look like whatever you want beyond this but this ensures the HAXeditor can correctly target and be integrated using the HAXCMSTheme mix-in. There are ways to position and reposition the HAXeditor dynamically that will not be covered here but can be seen in simple-blog -.
-From there, design away. Write whatever CSS and HTML and JS you want! The example themes referenced in our docs all provide blue prints for different ways of leveraging our template system.
-Next we'll discuss our Core template elements which you'll want to leverage in order to make theme development even cleaner!
- ]]> -- https://haxtheweb.org//documentation-1/haxcms/theming/web-components -Sat, 23 Mar 2019 13:58:38 +0000 -
- -
-
Get Involved! - https://haxtheweb.org//get-involved-1 -- Join our community - -- Join us on the HAXTheWeb Slack - channel -
- Join us for HAXcamp Un-code - every Friday 3 pm - 5 pm (EST) -
- Follow / use the #HAXTheWeb hash tag - -
Join our projects
-- HAXcms - - That which powers this website -
- Unbundled-Webcomponents - - A methodology for building and deploying web components to CDNs that we use in all our projects -
- Web components monorepo - - That which powers our editing experience (and all our other tags for that matter) -
- WCFactory
- - Build and maintain your own web component library, why should we be special.
- Check out our integrations page - for platform specific repos -
Organization that wants to get involved?
-Great! Here's some of the best ways for organizations to try "HAX" and get involved in the project.
-- Reach out to any of the members of the core project team on our slack -. We're happy to do conference calls to forge partnerships especially around HAX or OER production solution though it has implications for any public site! -
- Try out the HAXcms live demo - (reset hourly) -
- Reach out in the issue queue - with questions -
- Bring this website to developers in your organization or other code junkies and tell them to explore -
- Host a HAX camp - (ask for more details) -
HAX makes up multiple projects across hundreds of web components and various other repos. It can be a bit overwhelming but we want you to imagine something... Imagine being a developer on HAX.
-- -Step 'ight up-
- urz te next contribBecause all it takes to get involved in HAX is, that's right, showing up in our repos and getting involved! Yes you too can be just as meme-able as we are!
-All things HAX are powered by people just like you, wanting to make the web a better, more accessible, easier to use, less painful to develop for... place.Help us make that a reality and you too could have Snoop Dawg escorting you over to a brand new car*
-Anything is possible with HAXTheWeb. The only limit...is yourself -.
-*Claims vs reality may vary. Just help us out and we'll see where it goes.. -
- ]]> -- https://haxtheweb.org//get-involved-1 -Thu, 21 Mar 2019 19:46:24 +0000 -
- -
-
Presentations - https://haxtheweb.org//welcome/presentations -- This is the youtube playlist - of all things HAXTheWeb - - -This playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists related to all things ELMS:LN, WCFactory, HAXcms and web components in general.
- ]]> -- https://haxtheweb.org//welcome/presentations -Mon, 18 Mar 2019 12:06:57 +0000 -
- -
-
Core elements - https://haxtheweb.org//documentation-1/haxcms/theming/core-elements -- While you're not required to use them, HAXcms supplies a series of elements that can make theme development effortless. You can see the source of these in greater detail under the theme directory of haxcms-elements - - -. This is a brief overview of what they are and what they provide to your interface. - -HAXcms seeks to apply the SDS pattern, a technique we made up just for this sentence, for dramatic effect -. As everyone knows who is about to read the next heading, SDS stands for:
-So. Damn. Semantic.
-Whew, I need an ice cold drink to wash away the semantic sweats.
-Yes, that's right, HAXcms allows you to theme a complex state managed system without needing to understand state management... like... at all.
-"But I understand state management and it's important to me"
-That's awesome, four people on twitter, but most designers just want to design! They don't need or want to understand the intricacies of making a collapsed field area expand relative to what item has been dictated as active in the store*.
-*an intentionally confusing worded sentence - - -
-We use MobX to do our state management if that's something you care about and some of our themes directly implement and interface with the state management layer. See Simple Blog's footer element - - - for a great example of why state management is a PITA. - -
-Back to the elements jerk
-Ok fine, here they are. Here's the list of ES module imports to get them
-{ - "dependencies": { - "@lrnwebcomponents/haxcms-elements": "latest" - } -} - -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/active-item/site-active-title.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/blocks/site-children-block.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/blocks/site-outline-block.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/layout/site-footer.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/layout/site-modal.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-breadcrumb.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-dot-indicator.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu-button.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-menu.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/navigation/site-top-menu.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-query-menu-slice.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-query.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/query/site-render-query.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-print-button.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-rss-button.js"; -import "@lrnwebcomponents/haxcms-elements/lib/ui-components/site/site-title.js"; - -Now here's what each of them provide you (pretty self explanatory because #SDS)
-- site-active-title -
-the title of the active item wrapped in a h1 tag
-
- site-children-block - - all child menu items based on a criteria match -
- site-outline-block - - part of the outline based on criteria match -
- site-footer - - a basic footer with license element based on site details -
- site-modal - - a basic modal with button that can house other elements -
- site-breadcrumb - - - a breadcrumb trail for the active menu item -
- site-dot-indicator - - site links but as a simple line of dots -
- site-menu-button
- - buttons for navigating through the active items in the menu. This is next, previous, parent and first child kinds of options.
- site-menu - - - A visualization of the hierarchy of your site, complete with checkmarks given per page the user goes to (optional) as well as a lot of styling options and a highlighted bar that scrolls the menu into view for small screens. It's fantastic and one line. -
- site-top-menu - - Top level menu links with indicator that scrolls to focus -
- site-print-button
- - print button with support for 4 levels of printing the site
- site-rss-button
- - a button that displays a link (opened in a new window) to get the RSS feed in RSS 2.0 or Atom 1.0 format (also applies correct semantic values for bots to discover)
- site-title
- - a link to the homepage of the site wrapped in an h1 tag
See the elements themselves for more details API examples and check out our themes as we leverage them heavily across the core themes.
-A word about style
-We use CSS variables to style all the bits inside of our custom elements. So if you don't like the styling, look at the CSS variables we make available and style away. The "Learn 2 theme" - - - is a great example implementing multiple levels of styling against multiple HAXcms site elements. You can always you know, go back and reread the CSS variables section -.
-- ]]> - - https://haxtheweb.org//documentation-1/haxcms/theming/core-elements -Wed, 13 Mar 2019 00:45:37 +0000 -
- - site-active-title -
-the title of the active item wrapped in a h1 tag
-
-
-
Publishing - https://haxtheweb.org//documentation-1/haxcms/publishing -- HAXcms requires being published in order to be visible to other people. Working locally or on Desktop or on a server, is akin to you writing a document on your computer. It's not shared with anyone. We recommend you setup publishing ahead of time to save hassle later. - -Setting up publishing
-From the HAXcms site listing - page, click the settings gear in the top right corner.
-Next you'll see a modal that has options for plugging in your github credentials. We don't save your password and this aspect is optional. If you do enter your password, a one time API call is made on your behalf from your container which will setup an ssh key pair. This allows for all future requests to publish to happen automatically on your behalf. Your password is not stored. If you don't want to set this part up, you can plug in the rest of the git settings, save, and then manually publish files after using the UI (see last heading on this page).
-NPublishing from your sites / new sites
-When you want to share your site with people or update your website, hitting the Publish button inside of your site is how to do this. Click the settings gear in the bottom right to get started.
-Currently GitHub is the only provider supported in the local installation method (or from DDEV / one of the supported container providers). In the future hitting publish will have additional development flexibility.
-Understanding what's actually happening
-- When you hit publish, a few things happen to make your site "web ready". This is the general order of those operations:
-- HAXcms takes the underlying files and commits them all to version control (though they already should be) - - -
- It then pushes these to the origin of the git repository (likely github) - -
- Then it switches to the branch you do your publishing from. In github, this is the gh-pages - - branch, but can deviate as needed. - -
- Next it deletes symlinks and replaces them with the correct references as needed and leverages the "cdn provider" you specified when setting up HAXcms in order to super charge your files for end users. - -
- It uses twig - - to step through and correctly rewrite references in the index.html of your site to match the paths of where it's going to be sent - -
- Then it adds all this to version control and sends it up to your gh-pages branch. - -
- It does some local file clean up and sets things back to master branch for the next time you go to work on everything - -
When this is all done, in the UI you'll see a link to your site after it's indicated a successful publish (meaning it pushed the files up there). Depending on where you host your content it may take a few minutes to see the change, though GitHub is usually up within about 2 minutes.
-Once about 2 minutes or so has passed, refresh your live site address or type in the URL of the site. If you've been there previously, you'll probably see the same content / theme as the last time you were there. After about 5 seconds, a message will pop up indicating "new content available" and clicking it (or refreshing the browser) will give you your updated content.
-This last step happens because of what's called a "service worker". This enables your site to be 100% offline capable and ensures that your site only uses traffic and data when it's absolutely necessary.
-A note on non UI publishing workflows
-You might not have (or want to) setup the credentials between HAXcms and github / your git repo. That's ok. After you hit publish go to terminal / a Git GUI and run the following to publish your site:
-cd haxcms/_sites/YOURSITE -git checkout gh-pages -git push origin gh-pages -git checkout master -git push origin master - -HAXcms will have made sure that the gh-pages and master branches are valid for distribution, even if it wasn't able to actually send these files to their publishing destination.
-- ]]> - - https://haxtheweb.org//documentation-1/haxcms/publishing -Wed, 20 Feb 2019 06:10:05 +0000 -
- -
-
HAXcms - https://haxtheweb.org//documentation-1/haxcms -- HAXcms, that which powers the site you are currently reading is a powerful "static site generator" paradigm. It leverages server technology in order to orchestrate a static site. That way the "server" is only used when needed for a user to securely develop their content. - -Difference from past static generators
-Unlike solutions like Jekyll - -, HAXcms is for anyone to publish a website, not just those that understand command line. HAXcms is intended to be installed and then allow users to entirely use a UI to create, publish and manage micro-sites.
-Visualization
- ]]>
- - https://haxtheweb.org//documentation-1/haxcms -Wed, 20 Feb 2019 06:10:05 +0000 -
- -
-
Structure - https://haxtheweb.org//documentation-1/haxcms/structure -- By design we've got a very simple structure. The goal of HAXcms isn't to lock you into anything and so we've simplified our file structure over other solutions. - -The key directories / files include:
-- files - any files you've uploaded through the HAX interface - -
- pages - folders named by their content uri that have index.html in it, no structure other then what you created when hitting save -
- site.json - JSON Outline Schema object that defines the pages in your site and their relationship to each other
- index.html - front page of the PWA that stitch it all together -
- service-worker.js - makes it a PWA, no need to edi this -
Screen grab of a microsite
- ]]>
- - https://haxtheweb.org//documentation-1/haxcms/structure -Wed, 20 Feb 2019 06:10:05 +0000 -
- -
-
Installation - https://haxtheweb.org//documentation-1/haxcms/installation -- Generic PHP install directions - -Have PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is to create two basic folders). If all goes well you'll see some ASCii art telling you what your password is. HAXcms seeks to be a 0 config installation so if anything didn't work or make sense, just drop us a line in the issue queues.
-Or from Command Line...
-Just run this one command and you'll be HAXing the web in no time! This will step you through prompts (which can be scripted via arguments) to feed the backend what it needs to create the few configuration files it uses to load.
-# HAX the web and answer the prompts -bash scripts/haxtheweb.sh - -A note on bash - - -
- -If you're having issues installing via the bash script, ensure you are on bash version 4.x. Some OS flavors start at 3.x which won't work. - - -
- -MAMP
-MAMP - - - - - - - allows Mac and PC users to rapidly install a working webdev stack on their machine. Here's the steps you need to take if using this (or on similar site hosting).
-Download the latest copy of HAXcms from github - - - - and place this in MAMP/htdocs - -either at the root level (as in copying the files you download into htdocs as shown in the image below) or by placing the folder in the directory (in the case where you have MAMP already installed / want to keep things tidy).
-- Open MAMP and hit the Start Servers Button - - - -
-- Click MY WEBSITE in MAMP start page to get started - - - -
-Now you can build website organically off of MAMP!
-DDEV / Docksal / Lando / Vagrant
-We recommend using HAXcms in a docker container manager like ddev - - - - - - -, though based on above you can see basically we're just downloading and running one command to get going. We support all of the above methods so pick the one you work with most often.
--
-
- Clone this repo:
git clone https://github.com/elmsln/haxcms.git- - - - - - - -
-
-
-
-
-
-
-
-
- - install docker - - - - - - - - - - - - - - - - -
- install ddev - - - - - - - - or install docksal - - - - - - - - or install lando - - - - - - - - or install vagrant - - - - - - - - (We support 'em all!) - - - - - - - - -
- open a terminal window, go to the directory and type
ddev start- - - - - - - - (for ddev) orfin init- - - - - - - - (for docksal) orlando start && lando magic- - - - - - - - (for lando) orvagrant up- - - - - - - - (for vagrant)
-
-
-
-
-
-
-
-
- - go to the link any of them give you in a browser - - - - - - - - -
- username/password is
admin- - - - - - - -/admin- - - - - - - - to get building out static sites locally that you can push up anywhere!
-
-
-
-
-
-
-
-
- - Click the icon in the top right and you're off and running! - - - - - - - - -
Apache gotchas
-If installing on an existing server it might already have apache configurations that would cause HAXcms to have issues out of the gate - (or any CMS for that matter). Make sure local overrides are allowed with something like the following:
-
-# /etc/apache2/apache2.conf - -<directory var/www/haxlocation> - Options Indexes FollowSymLinks - AllowOverride All - Require all granted -</directory> - - ]]> -- https://haxtheweb.org//documentation-1/haxcms/installation -Wed, 20 Feb 2019 06:10:05 +0000 -
- - Clone this repo:
-
-
Concepts - https://haxtheweb.org//documentation-1/haxcms/concepts -- HAXcms seeks to be a microsite generator and manager that doesn't require any command line in order to operate -. HAXcms leverages HAX to give a best in class authoring experience while HAXcms seeks to eliminate all the barriers to then publishing that content online. - -Some words and phrases worth understanding in HAXcms
-- HAXeditor - the HAX editor -
- microsite - An individual site that's been created by a user -
- Outline - All sites are an outline, we use JSON Outline Schema to manage this -
- Theme - A single web component based theme that's agnostic of content -
- Elements / web components - design assets that work anywhere -
- https://haxtheweb.org//documentation-1/haxcms/concepts -Wed, 20 Feb 2019 06:10:05 +0000 -
-
Who's involved
+HAX is the brainchild of Bryan Ollendyke, Michael Potter, Nikki Massaro Kaufman, Charles Lavera and a chorus of contributors. We've had contributions from:
+- \ No newline at end of file diff --git a/service-worker.js b/service-worker.js index b53ec96..48dda06 100644 --- a/service-worker.js +++ b/service-worker.js @@ -37,472 +37,7 @@ /* eslint-disable indent, no-unused-vars, no-multiple-empty-lines, max-nested-callbacks, space-before-function-paren, quotes, comma-spacing */ 'use strict'; -var precacheConfig = [ - [ - "pages\/documentation-1\/hax-development\/index.html", - "21AxbuTjN8wcpfx51zRnA" - ], - [ - "pages\/item-587de126-437b-4864-a3ea-54078837127c\/index.html", - "mk06H7oladBb5rwx9mc7Ag" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/core-elements\/query-examples\/index.html", - "NjdVdnJSw9mZgPgscq2Lwg" - ], - [ - "pages\/welcome\/what-is-hax\/index.html", - "DcxE2t11M6NhTN2KrQACg" - ], - [ - "pages\/documentation-1\/hax-development\/wcfactory-tooling\/index.html", - "pJGvifIFd9uCxillmeoYVA" - ], - [ - "pages\/welcome\/index.html", - "8NWgFO10VLBcjRpV8g" - ], - [ - "pages\/documentation-1\/hax-development\/hax-app-store\/apps\/index.html", - "assMXoMHYMwMhBBFi8ugpQ" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/css-vars\/index.html", - "XrqKTnxrCsCIUYR7H2g" - ], - [ - "pages\/documentation-1\/haxcms\/concepts\/index.html", - "z4I1O6SuABBc1kQwxIHzw" - ], - [ - "pages\/documentation-1\/ux-concepts\/add\/index.html", - "Qo5DLal3zYH08jeETxpFnA" - ], - [ - "pages\/documentation-1\/core-concepts\/index.html", - "ZDTuwJjNoVGV5eEItTppQ" - ], - [ - "pages\/documentation-1\/hax-development\/hello-world-element\/index.html", - "WmPcKWmkjVC4CCa9xxD7Q" - ], - [ - "pages\/welcome\/why-haxcms-1\/index.html", - "LZNJYTROu6Uw2EqwMOPoDQ" - ], - [ - "pages\/documentation-1\/haxcms\/installation\/index.html", - "uW0I21adGvvNVU7CnpaH0g" - ], - [ - "pages\/documentation-1\/hax-development\/hax-app-store\/blox\/index.html", - "zW9NtwyON8L1EmhhuBw" - ], - [ - "pages\/get-involved-1\/index.html", - "Utz09RNthS38ismk9PjOg" - ], - [ - "pages\/integrations-1\/index.html", - "z2egUjGk3t2HhVN5P8dpA" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/skin-a-site\/index.html", - "XHjxYL3auHdxcjkbqc70w" - ], - [ - "pages\/item-eca7c8a4-393a-4e68-8cb4-440e94683738\/index.html", - "oyf0GDyr0oZYLczWQ9w" - ], - [ - "pages\/documentation-1\/haxcms\/structure\/index.html", - "GDXNqZT3IEz2W3FGJaA" - ], - [ - "pages\/documentation-1\/hax-development\/hax-schema\/index.html", - "VjnaSMcRz9fRPwuxJXh1w" - ], - [ - "pages\/welcome\/solutions\/index.html", - "ObC0pyRkdR327PpUAZikjQ" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/web-components\/index.html", - "PZJFTK19QnrLVkihUttFfw" - ], - [ - "pages\/integrations-1\/wordpress\/index.html", - "2RHDEPqfrcIhokRcg8gdg" - ], - [ - "pages\/documentation-1\/index.html", - "DqALsfCYqsu7SrahklWnJg" - ], - [ - "pages\/documentation-1\/hax-development\/hax-app-store\/stax\/index.html", - "JQaN7C71aosIYkeZ8yL7A" - ], - [ - "pages\/documentation-1\/ux-concepts\/find\/index.html", - "6y04dMru1pok7ewW9pXC5Q" - ], - [ - "pages\/documentation-1\/ux-concepts\/index.html", - "FJlDjMOAAj4IFohx1TUidg" - ], - [ - "pages\/documentation-1\/related-technologies\/index.html", - "7GUIvUTyuOVDIKllAZe6A" - ], - [ - "pages\/documentation-1\/hax-development\/hax-app-store\/autoloader\/index.html", - "TvseVCg664tQxEInGPRjA" - ], - [ - "pages\/item-aa589faa-e860-4221-82fa-df6d57328ac2\/index.html", - "j3ivxcWezc7zLbIwIXf5ag" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/core-elements\/index.html", - "RJdXjluG8P1drayyA5qatw" - ], - [ - "pages\/f-a-q-1\/index.html", - "0xf8Mz3wYpEslih5aKEmpQ" - ], - [ - "pages\/integrations-1\/drupal\/index.html", - "xBEKR2l4VgUwiwqjT9aSg" - ], - [ - "pages\/welcome\/roadmap-1\/index.html", - "7ASlq2i4eihExd5HhfGsA" - ], - [ - "pages\/documentation-1\/haxcms\/publishing\/index.html", - "VW7CiO7Ay2R1MXZtLE33KA" - ], - [ - "pages\/item-44cc230b-07db-442a-90cf-687e2d089a5d\/index.html", - "d0qMBnt0wHP696fHdFhWA" - ], - [ - "pages\/welcome\/presentations\/index.html", - "ssik6P0CMBwzp23yv5HwEA" - ], - [ - "pages\/integrations-1\/backdropcms\/index.html", - "GS5wg4QVKUTLAj0HGXVaA" - ], - [ - "pages\/scavenger-hunt-1\/index.html", - "agzm2ngjYVpLONL4VP7Uw" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/dev-workflows\/index.html", - "uMa5s9ZNkKwbcqxpRW5b4Q" - ], - [ - "pages\/documentation-1\/haxcms\/life-cycle\/index.html", - "1mFZTBuHt9Ga2B9b08ZTw" - ], - [ - "pages\/documentation-1\/haxcms\/index.html", - "VEFONa2ClV3mbPmEShCB4A" - ], - [ - "pages\/item-cdd303d0-4490-4433-94fa-0e78cf849e80\/index.html", - "bsh9XWtX3uGbNkpVIiMIg" - ], - [ - "pages\/documentation-1\/hax-development\/hax-element-schema\/index.html", - "T3pwS38Un5Gj0OaKDST6yg" - ], - [ - "pages\/welcome\/i-have-issues\/index.html", - "2MKtlrsbYX6Z5WhX6ObuQ" - ], - [ - "pages\/integrations-1\/classicpress-1\/index.html", - "ParLrbIwU9c8OwP2PQvtw" - ], - [ - "pages\/documentation-1\/haxcms\/troubleshooting\/index.html", - "8EIuTdwmwi2DArqZJPjsIA" - ], - [ - "pages\/documentation-1\/hax-development\/hax-app-store\/index.html", - "fsGSBcIKWzrC559gbMgHw" - ], - [ - "pages\/integrations-1\/gravcms\/index.html", - "Ql37Zrrt59RUIJjBM1V6mg" - ], - [ - "pages\/documentation-1\/haxcms\/theming\/index.html", - "GIqNP3LJcHIxjKEjICN4Q" - ], - [ - "pages\/integrations-1\/creating-new-ones\/index.html", - "9lAPWsnKOXLsjkdelxENA" - ], - [ - "index.html", - "Dkp0PBqslnscvL652AY0g" - ], - [ - "manifest.json", - "NQ6UNvs0WLO64hLCcFE39A" - ], - [ - "site.json", - "s2UBPuG8LAnOXtostaqmA" - ], - [ - "files\/haxcms-managed\/512x512-3450183.png", - "jcfmjnOGcJbDqOl4ZvDGg" - ], - [ - "files\/haxcms-managed\/310x310-3450183.png", - "n40lEuJkrTEVnSC6g" - ], - [ - "files\/haxcms-managed\/192x192-3450183.png", - "P7JoPuNqHJrutz20I5fg" - ], - [ - "files\/haxcms-managed\/150x150-3450183.png", - "HRrXoOysh7d9CzrkFYyBg" - ], - [ - "files\/haxcms-managed\/144x144-3450183.png", - "zLnxoWl5eb5KzsfhmqgWJg" - ], - [ - "files\/haxcms-managed\/96x96-3450183.png", - "SRSagMlMYoiJTs02sZDLA" - ], - [ - "files\/haxcms-managed\/72x72-3450183.png", - "77g5cPsEYDobTAFd0cl7g" - ], - [ - "files\/haxcms-managed\/70x70-3450183.png", - "vp0BBkaAisUdUqayUp0g" - ], - [ - "files\/haxcms-managed\/48x48-3450183.png", - "PwTBf70b77AnQGQXAeSmw" - ], - [ - "files\/haxcms-managed\/36x36-3450183.png", - "qvIEbavd98wrqZlUBptxQ" - ], - [ - "files\/haxcms-managed\/16x16-3450183.png", - "nBQfdTExKIC19E72heCQ" - ], - [ - "404.html", - "QEzLbAYRfRrqwxyIGIpfNQ" - ], - [ - "files\/2019-01-25_14-05-59.png", - "6WQ28zgmkTgXqluj7HBNBg" - ], - [ - "files\/2019-01-27_10-10-39.png", - "wILedZJIMsevf3B9Q6JnFw" - ], - [ - "files\/Screenshot from 2020-08-17 14-34-32.png", - "z9Nx0tbzmmEFCryi2nXurg" - ], - [ - "files\/2019-01-27_17-39-01.png", - "6SiXrdVbeaDaffgT317zWg" - ], - [ - "files\/2019-01-27_17-39-31.png", - "tlYT0GX9y1Q1VmHlddgvmw" - ], - [ - "files\/2019-01-27_17-33-57.png", - "eC9DC3H2BWSxzcSHHYpuw" - ], - [ - "files\/2019-01-27_10-10-58.png", - "VdWRH9717QXDzDu6e9imug" - ], - [ - "files\/2019-01-25_14-04-31.png", - "TbwdTI6FF4xbVdVUEMzK7Q" - ], - [ - "files\/2019-03-12_16-45-51.png", - "rvEknEJJwwxnbjQ862kg" - ], - [ - "files\/3450183.png", - "2vPNkZKZ5sW8UVQoThAcRA" - ], - [ - "files\/2019-01-27_09-23-44.png", - "Di9FJlwLIocBUvhnVi4A9w" - ], - [ - "files\/2019-01-27_09-23-59.png", - "VEgN6kvHZPbXmOPEYaJA" - ], - [ - "files\/gitpublishingdata.jpg", - "yKPwn9PbiCrE1nJqiy1JA" - ], - [ - "files\/2019-01-27_18-05-51.png", - "xXmIr2GwnSmioMUNQolAYQ" - ], - [ - "files\/Screenshot from 2020-08-17 14-46-06.png", - "tav8rnDaVHVsCuFZwJS0qg" - ], - [ - "files\/2019-01-29_22-47-53.png", - "Lpbo3XZIKV6Dok6o2Afg" - ], - [ - "files\/pubwork1.jpg", - "L2NfHWUo5GnFhNoKlNr9A" - ], - [ - "files\/HAXCms workflow.jpg", - "h0QfGEQyTSwbkL9uFWojqw" - ], - [ - "files\/2019-01-27_09-23-33.png", - "ySz3BTqt0BczeIJKCH4Q" - ], - [ - "files\/2019-01-27_10-25-22.png", - "4eYa7xjiWdQ59ehcX3XGw" - ], - [ - "files\/Screenshot from 2020-08-17 14-42-07.png", - "RT69Ri3DZJfn4C238YPtlg" - ], - [ - "files\/mamppage.jpg", - "EfYuCCY2S2iOlf6VQ9b0w" - ], - [ - "files\/d8cdnimage.jpg", - "wBPjaGz0B5mZFgb66I3HA" - ], - [ - "files\/mampstructure.jpg", - "MKuoeUCwGLJrEO0UjmNLw" - ], - [ - "files\/2019-03-21_15-12-05.jpg", - "TUnlTQRl7ktIFBVcwcPOQ" - ], - [ - "files\/Screenshot from 2020-08-17 14-43-47.png", - "2hotxLkyeobZ9l7FuVi5Zw" - ], - [ - "files\/pubwork2.jpg", - "rTTHXtetyfaaEWHgKBPg" - ], - [ - "files\/haxd8simply.jpg", - "ZthRjMDItwiLMaIs4UF8A" - ], - [ - "files\/mampstart.jpg", - "nRZdPZcrLcm67xIp3TYdQ" - ], - [ - "files\/Picture1.png", - "9xJNkS7qmKy4hufccLOZqg" - ], - [ - "files\/2019-02-20_01-26-10.png", - "vmeIeTNm1hK7GRG3Zwjp1A" - ], - [ - "files\/2019-02-20_01-26-01.png", - "xRAxgZYXkmteGfclP7WQg" - ], - [ - "files\/sourceviewthispage.jpg", - "4uHTjQlOpHSfDXLN1cP8w" - ], - [ - "files\/2019-01-27_10-22-28.png", - "sTnTmDnmLQ9zb7lJUvukg" - ], - [ - "files\/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", - "oTxKP22mGGCaMUMvUy4Ew" - ], - [ - "files\/IMG_20190127_153429.jpg", - "yd4LYpwHWIv1yKGKmkQd4Q" - ], - [ - "files\/2019-02-25_16-22-25.png", - "9FCh9SAIZNBrikiISCaHcA" - ], - [ - "files\/lego.jpg", - "VXAkmIpVUqB2wzcVyd3x2Q" - ], - [ - "files\/ngdle.png", - "zLtkcC36w1jGZoopv6kwAw" - ], - [ - "files\/2019-01-27_09-35-28.png", - "feg5NUoR9fucYByzHfDJXA" - ], - [ - "files\/2019-01-27_09-45-04.png", - "zDC1pmhvnlHuW6E51yQE5A" - ], - [ - "files\/Roadmap.jpg", - "iFFmAFs0MRszoNRpIOTXTQ" - ], - [ - "files\/headshot272229.61999999825.jpg", - "zMvFZhCgmpmbCyKaTp3bRQ" - ], - [ - "files\/Screenshot from 2020-08-17 14-36-15.png", - "ZAZDTC8VyHUOfSKtGilhZg" - ], - [ - "files\/haxrelationships.jpg", - "qtLhHIKnm1HCCAFnD96mA" - ], - [ - "files\/2019-01-27_10-22-48.png", - "i3RibHTk0kxkChXembJFGg" - ], - [ - "files\/HAXshort.vtt", - "nsneskvQ7H996xTa3DGH7Q" - ], - [ - "files\/2019-03-23_10-51-10.jpg", - "uA3RmjTPTucU4zU3epjA" - ], - [ - "files\/demo.csv", - "3Id2QkyorDuLUvz6MlRhA" - ] -]; +var precacheConfig = {{ swhash|json_encode(constant('JSON_PRETTY_PRINT'))|raw }}; var cacheName = 'sw-precache-v3--' + (self.registration ? self.registration.scope : ''); @@ -750,3 +285,6 @@ self.addEventListener('fetch', function (event) { // Runtime cache configuration, using the sw-toolbox library. +{% if cdnRegex %} +toolbox.router.get(/{{ cdnRegex|raw }}/, toolbox.fastest, {}); +{% endif %} \ No newline at end of file diff --git a/site.json b/site.json index d8f2d84..6e7460c 100644 --- a/site.json +++ b/site.json @@ -1,1571 +1,1594 @@ { - "id": "95f2b045-cfdb-4e35-b29b-e7f71c859987", - "title": "hax-the-web", - "author": "elmsln", - "description": "Project home and documentation for all things HAX", - "license": "by-sa", - "metadata": { - "author": { - "name": "ELMS:LN", - "image": "", - "socialLink": "https:\/\/twitter.com\/elmsln", - "email": "hax@psu.edu" - }, - "site": { - "name": "haxtheweb", - "created": 1547138719, - "updated": 1617805490, - "domain": "https:\/\/haxtheweb.org\/", - "git": { - "vendor": "github", - "branch": "master", - "staticBranch": "gh-pages", - "url": "git@github.com:elmsln\/haxtheweb.org.git", - "autoPush": false, - "publicRepoUrl": "https:\/\/github.com\/elmsln\/haxtheweb.org\/tree\/master\/" - }, - "static": { - "cdn": "cdn.waxam.io", - "lastPublished": 1617979997, - "publishedLocation": "https:\/\/haxtheweb.org\/", - "offline": false - }, - "settings": { - "pathauto": false, - "publishPagesOn": true, - "sw": false, - "forceUpgrade": false - }, - "version": "1.3.0", - "logo": "files\/3450183.png" - }, - "theme": { - "element": "clean-two", - "path": "@lrnwebcomponents\/clean-two\/clean-two.js", - "name": "Course theme 2", - "variables": { - "image": "assets\/banner.jpg", - "hexCode": "#009dc7", - "cssVariable": "--simple-colors-default-theme-purple-7", - "icon": "lrn:network" + "id": "95f2b045-cfdb-4e35-b29b-e7f71c859987", + "title": "hax-the-web", + "author": "elmsln", + "description": "Project home and documentation for all things HAX", + "license": "by-sa", + "metadata": { + "author": { + "name": "ELMS:LN", + "image": "", + "socialLink": "https://twitter.com/elmsln", + "email": "hax@psu.edu" + }, + "site": { + "name": "haxtheweb", + "created": 1547138719, + "updated": 1726516452, + "domain": "https://haxtheweb.org/", + "git": { + "vendor": "github", + "branch": "master", + "staticBranch": "gh-pages", + "url": "git@github.com:elmsln/haxtheweb.org.git", + "autoPush": false, + "publicRepoUrl": "https://github.com/elmsln/haxtheweb.org/tree/master/" + }, + "static": { + "cdn": "", + "lastPublished": 1617979997, + "publishedLocation": "https://haxtheweb.org/", + "offline": false + }, + "settings": { + "pathauto": false, + "publishPagesOn": true, + "sw": false, + "forceUpgrade": false, + "gaID": null + }, + "version": "9.0.5", + "logo": "files/3450183.png", + "tags": null + }, + "theme": { + "element": "clean-two", + "path": "@haxtheweb/clean-two/clean-two.js", + "name": "Clean two theme", + "thumbnail": "build/es6/node_modules/@haxtheweb/app-hax/lib/assets/images/PartyStyle.svg", + "variables": { + "image": "assets/banner.jpg", + "imageAlt": null, + "imageLink": null, + "hexCode": "#009dc7", + "cssVariable": "--simple-colors-default-theme-purple-7", + "icon": "lrn:network" + }, + "regions": {} + }, + "node": { + "dynamicElementLoader": { + "h5p-element": "@lrnwebcomponents/h5p-element/h5p-element.js", + "hax-logo": "@lrnwebcomponents/hax-logo/hax-logo.js", + "a11y-gif-player": "@lrnwebcomponents/a11y-gif-player/a11y-gif-player.js", + "code-sample": "@lrnwebcomponents/code-sample/code-sample.js", + "citation-element": "@lrnwebcomponents/citation-element/citation-element.js", + "hero-banner": "@lrnwebcomponents/hero-banner/hero-banner.js", + "image-compare-slider": "@lrnwebcomponents/image-compare-slider/image-compare-slider.js", + "license-element": "@lrnwebcomponents/license-element/license-element.js", + "lrn-aside": "@lrnwebcomponents/lrn-aside/lrn-aside.js", + "lrn-math": "@lrnwebcomponents/lrn-math/lrn-math.js", + "lrn-table": "@lrnwebcomponents/lrn-table/lrn-table.js", + "lrn-vocab": "@lrnwebcomponents/lrn-vocab/lrn-vocab.js", + "lrndesign-blockquote": "@lrnwebcomponents/lrndesign-blockquote/lrndesign-blockquote.js", + "magazine-cover": "@lrnwebcomponents/magazine-cover/magazine-cover.js", + "media-behaviors": "@lrnwebcomponents/media-behaviors/media-behaviors.js", + "media-image": "@lrnwebcomponents/media-image/media-image.js", + "meme-maker": "@lrnwebcomponents/meme-maker/meme-maker.js", + "grid-plate": "@lrnwebcomponents/grid-plate/grid-plate.js", + "md-block": "@lrnwebcomponents/md-block/md-block.js", + "multiple-choice": "@lrnwebcomponents/multiple-choice/multiple-choice.js", + "paper-audio-player": "@lrnwebcomponents/paper-audio-player/paper-audio-player.js", + "person-testimonial": "@lrnwebcomponents/person-testimonial/person-testimonial.js", + "place-holder": "@lrnwebcomponents/place-holder/place-holder.js", + "q-r": "@lrnwebcomponents/q-r/q-r.js", + "full-width-image": "@lrnwebcomponents/full-width-image/full-width-image.js", + "self-check": "@lrnwebcomponents/self-check/self-check.js", + "simple-concept-network": "@lrnwebcomponents/simple-concept-network/simple-concept-network.js", + "stop-note": "@lrnwebcomponents/stop-note/stop-note.js", + "tab-list": "@lrnwebcomponents/tab-list/tab-list.js", + "task-list": "@lrnwebcomponents/task-list/task-list.js", + "video-player": "@lrnwebcomponents/video-player/video-player.js", + "wave-player": "@lrnwebcomponents/wave-player/wave-player.js", + "wikipedia-query": "@lrnwebcomponents/wikipedia-query/wikipedia-query.js", + "lrndesign-gallery": "@lrnwebcomponents/lrndesign-gallery/lrndesign-gallery.js", + "lrndesign-timeline": "@lrnwebcomponents/lrndesign-timeline/lrndesign-timeline.js", + "html-block": "@lrnwebcomponents/html-block/html-block.js", + "user-action": "@lrnwebcomponents/user-action/user-action.js", + "rss-items": "@lrnwebcomponents/rss-items/rss-items.js" + }, + "fields": {} + } + }, + "items": [ + { + "id": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "indent": "1", + "location": "pages/documentation-1/hax-development/index.html", + "slug": "documentation-1/hax-development", + "order": "0", + "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "title": "HAX development", + "description": "Include HAX in your projectThe developers docs will lay out the many specifications that make HAX possible including core concepts, different schema's it leverages ad how to define app store spec in ", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-587de126-437b-4864-a3ea-54078837127c", + "indent": "1", + "location": "pages/item-587de126-437b-4864-a3ea-54078837127c/index.html", + "slug": "integrations-1/hax11ty", + "order": "0", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "HAX11ty", + "description": "HAX + 11ty = HAX11ty! HAX11ty gives you the best of SEO from 11ty while using the HAX editor and the HAXcms theme engine for presenting material. This gives you the SPA capabilities of fast loading r", + "metadata": { + "created": 1597690877, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 4, + "schema": [ + { + "resource": "#d8a4a0fc-7cf5-800c-41cd-cdae27ae49c4", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - "node": { - "dynamicElementLoader": { - "h5p-element": "@lrnwebcomponents\/h5p-element\/h5p-element.js", - "hax-logo": "@lrnwebcomponents\/hax-logo\/hax-logo.js", - "a11y-gif-player": "@lrnwebcomponents\/a11y-gif-player\/a11y-gif-player.js", - "code-sample": "@lrnwebcomponents\/code-sample\/code-sample.js", - "citation-element": "@lrnwebcomponents\/citation-element\/citation-element.js", - "hero-banner": "@lrnwebcomponents\/hero-banner\/hero-banner.js", - "image-compare-slider": "@lrnwebcomponents\/image-compare-slider\/image-compare-slider.js", - "license-element": "@lrnwebcomponents\/license-element\/license-element.js", - "lrn-aside": "@lrnwebcomponents\/lrn-aside\/lrn-aside.js", - "lrn-math": "@lrnwebcomponents\/lrn-math\/lrn-math.js", - "lrn-table": "@lrnwebcomponents\/lrn-table\/lrn-table.js", - "lrn-vocab": "@lrnwebcomponents\/lrn-vocab\/lrn-vocab.js", - "lrndesign-blockquote": "@lrnwebcomponents\/lrndesign-blockquote\/lrndesign-blockquote.js", - "magazine-cover": "@lrnwebcomponents\/magazine-cover\/magazine-cover.js", - "media-behaviors": "@lrnwebcomponents\/media-behaviors\/media-behaviors.js", - "media-image": "@lrnwebcomponents\/media-image\/media-image.js", - "meme-maker": "@lrnwebcomponents\/meme-maker\/meme-maker.js", - "grid-plate": "@lrnwebcomponents\/grid-plate\/grid-plate.js", - "md-block": "@lrnwebcomponents\/md-block\/md-block.js", - "multiple-choice": "@lrnwebcomponents\/multiple-choice\/multiple-choice.js", - "paper-audio-player": "@lrnwebcomponents\/paper-audio-player\/paper-audio-player.js", - "person-testimonial": "@lrnwebcomponents\/person-testimonial\/person-testimonial.js", - "place-holder": "@lrnwebcomponents\/place-holder\/place-holder.js", - "q-r": "@lrnwebcomponents\/q-r\/q-r.js", - "full-width-image": "@lrnwebcomponents\/full-width-image\/full-width-image.js", - "self-check": "@lrnwebcomponents\/self-check\/self-check.js", - "simple-concept-network": "@lrnwebcomponents\/simple-concept-network\/simple-concept-network.js", - "stop-note": "@lrnwebcomponents\/stop-note\/stop-note.js", - "tab-list": "@lrnwebcomponents\/tab-list\/tab-list.js", - "task-list": "@lrnwebcomponents\/task-list\/task-list.js", - "video-player": "@lrnwebcomponents\/video-player\/video-player.js", - "wave-player": "@lrnwebcomponents\/wave-player\/wave-player.js", - "wikipedia-query": "@lrnwebcomponents\/wikipedia-query\/wikipedia-query.js", - "lrndesign-gallery": "@lrnwebcomponents\/lrndesign-gallery\/lrndesign-gallery.js", - "lrndesign-timeline": "@lrnwebcomponents\/lrndesign-timeline\/lrndesign-timeline.js", - "html-block": "@lrnwebcomponents\/html-block\/html-block.js", - "user-action": "@lrnwebcomponents\/user-action\/user-action.js", - "rss-items": "@lrnwebcomponents\/rss-items\/rss-items.js" - }, - "fields": {} + ], + "tags": { + "p": 4, + "video-player": 1 + }, + "elements": 5 } + } }, - "items": [ - { - "id": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "indent": "1", - "location": "pages\/documentation-1\/hax-development\/index.html", - "slug": "documentation-1\/hax-development", - "order": "0", - "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "title": "HAX development", - "description": "Include HAX in your projectThe developers docs will lay out the many specifications that make HAX possible including core concepts, different schema's it leverages ad how to define app store spec in ", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-587de126-437b-4864-a3ea-54078837127c", - "indent": "1", - "location": "pages\/item-587de126-437b-4864-a3ea-54078837127c\/index.html", - "slug": "integrations-1\/hax11ty", - "order": "0", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "HAX11ty", - "description": "HAX + 11ty = HAX11ty! HAX11ty gives you the best of SEO from 11ty while using the HAX editor and the HAXcms theme engine for presenting material. This gives you the SPA capabilities of fast loading r", - "metadata": { - "created": 1597690877, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 4, - "schema": [ - { - "resource": "#d8a4a0fc-7cf5-800c-41cd-cdae27ae49c4", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 4, - "video-player": 1 - }, - "elements": 5 - } - } - }, - { - "id": "item-36c4fc60-67c0-43c2-8f71-c6a117e8b7d6", - "indent": "4", - "location": "pages\/documentation-1\/haxcms\/theming\/core-elements\/query-examples\/index.html", - "slug": "documentation-1\/haxcms\/theming\/core-elements\/query-examples", - "order": "0", - "parent": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550", - "title": "Query examples", - "description": " Hold up there. You didn't cover any of the query tags in that last section!Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that n", - "metadata": { - "created": 1553349518, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/2019-03-23_10-51-10.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/2019-03-23_10-51-10.jpg", - "url": "files\/2019-03-23_10-51-10.jpg", - "type": "image\/jpeg", - "name": "2019-03-23_10-51-10.jpg", - "size": 54637 - } - ] - } - }, - { - "id": "item-asd7dab5-8208-65e3-c3e4-267f233f60553", - "indent": "1", - "location": "pages\/welcome\/what-is-hax\/index.html", - "slug": "welcome\/what-is-hax", - "order": "0", - "parent": "item-welcome", - "title": "What is HAX", - "description": "HAX - Headless Authoring eXperienceHAX is a WYSIWYG unlike any other. You extend your world by extending the web through the web component standard. HAX has a simple schema and integrations to allow", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/\/sourceviewthispage.jpg", - "fullUrl": "\/sites\/haxtheweb\/files\/sourceviewthispage.jpg", - "url": "files\/sourceviewthispage.jpg", - "type": "image\/jpeg", - "name": "sourceviewthispage.jpg", - "size": 34616 - } - ], - "readtime": 2, - "contentDetails": { - "headings": 4, - "paragraphs": 8, - "schema": [], - "tags": { - "full-width-image": 1, - "h2": 4, - "p": 8, - "code-sample": 1, - "meme-maker": 1, - "ul": 1, - "img": 1 - }, - "elements": 17 - } - } - }, - { - "id": "item-692eb91c-4003-3429-5d9f-caac64691849", - "indent": "2", - "location": "pages\/documentation-1\/hax-development\/wcfactory-tooling\/index.html", - "slug": "documentation-1\/hax-development\/wcfactory-tooling", - "order": "0", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "WCFactory Tooling", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-welcome", - "indent": 0, - "location": "pages\/welcome\/index.html", - "slug": "welcome", - "order": "0", - "parent": null, - "title": "Our Mission", - "description": "We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless of ability,\u00a0platform,tribe\u00a0or income.Will you he", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/demo.csv", - "fullUrl": "\/_sites\/haxtheweb\/files\/demo.csv", - "url": "files\/demo.csv", - "type": "text\/plain", - "name": "demo.csv", - "size": 830 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/demo.csv", - "fullUrl": "\/_sites\/haxtheweb\/files\/demo.csv", - "url": "files\/demo.csv", - "type": "text\/plain", - "name": "demo.csv", - "size": 830 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/ngdle.png", - "fullUrl": "\/_sites\/haxtheweb\/files\/ngdle.png", - "url": "files\/ngdle.png", - "type": "image\/png", - "name": "ngdle.png", - "size": 307196 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 6, - "paragraphs": 10, - "schema": [ - { - "resource": "#18d556e9-a1d7-3069-81d9", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 10, - "h3": 6, - "code-sample": 2, - "ul": 2, - "video-player": 1 - }, - "elements": 21 - }, - "published": true - } - }, - { - "id": "item-96d00871-d866-c65e-b7f0-4e242bde5b15", - "indent": "3", - "location": "pages\/documentation-1\/hax-development\/hax-app-store\/apps\/index.html", - "slug": "documentation-1\/hax-development\/hax-app-store\/apps", - "order": "0", - "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", - "title": "apps", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-f0af8879-a79c-4d1c-afc4-e23c32f52dc4", - "indent": "3", - "location": "pages\/documentation-1\/haxcms\/theming\/css-vars\/index.html", - "slug": "documentation-1\/haxcms\/theming\/css-vars", - "order": "0", - "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "title": "CSS vars", - "description": "CSS can be modified via CSS variables. CSS variables create a happy middle ground between the constraints of Shadow DOM (namely that styles are fully encapsulated) and designers wanting flexibility a", - "metadata": { - "created": 1553349518, - "updated": 1617805490 - } - }, - { - "id": "item-dfd62788-ba48-4051-a869-986e5956864f", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/concepts\/index.html", - "slug": "documentation-1\/haxcms\/concepts", - "order": "0", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Concepts", - "description": "HAXcms seeks to be a microsite generator and manager that doesn't require any command line in order to operate. HAXcms leverages HAX to give a best in class authoring experience while HAXcms seeks to", - "metadata": { - "created": 1550643005, - "updated": 1617805490 - } - }, - { - "id": "item-e3dafe1a-1f50-1834-68f3-9f378e4ddda5", - "indent": "2", - "location": "pages\/documentation-1\/ux-concepts\/add\/index.html", - "slug": "documentation-1\/ux-concepts\/add", - "order": "0", - "parent": "item-06233713-d866-3351-81da-841d3931144c", - "title": "Add Content", - "description": "Add Content\u00a0is how you create and add complex blocks to the HAX page editor. These blocks can be variable based on what you chose to include (see appstore) but ultimately are just adding web compon", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-34-32.png", - "fullUrl": "\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-34-32.png", - "url": "files\/Screenshot from 2020-08-17 14-34-32.png", - "type": "image\/png", - "name": "Screenshot from 2020-08-17 14-34-32.png", - "size": 78391 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "img": 1 - }, - "elements": 2 - } - } - }, - { - "id": "item-275a0928-60ab-b7ce-c2b6-d0e35826498b", - "indent": "1", - "location": "pages\/documentation-1\/core-concepts\/index.html", - "slug": "documentation-1\/core-concepts", - "order": "1", - "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "title": "Core concepts", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-39074718-758f-d51b-1dc5-15cfbb79e44c", - "indent": "2", - "location": "pages\/documentation-1\/hax-development\/hello-world-element\/index.html", - "slug": "documentation-1\/hax-development\/hello-world-element", - "order": "1", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "hello-world element", - "description": "Let's see what goes into the element called @lrnwebcomponents\/example-hax-element\u00a0in order to learn how we can wire anything up to HAXeditor.@lrnwebcomponents\/example-hax-element\/example-hax-elem", - "metadata": { - "created": 1548826475, - "updated": 1617806663, - "readtime": 1, - "contentDetails": { - "headings": 1, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "h2": 1, - "code-sample": 1 - }, - "elements": 3 - } - } - }, - { - "id": "item-650eaa59-478c-4674-8ef3-93e4b43e2310", - "indent": "1", - "location": "pages\/welcome\/why-haxcms-1\/index.html", - "slug": "welcome\/why-haxcms-1", - "order": "1", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "HAXcms", - "description": "HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web ", - "metadata": { - "created": 1563972322, - "updated": 1617805490, - "readtime": 2, - "contentDetails": { - "headings": 6, - "paragraphs": 5, - "schema": [ - { - "typeof": "oer:Assessment", - "resource": "#dd2feacf-ed4a-dcb0-b85d", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "grid-plate": 1, - "h2": 2, - "ul": 3, - "p": 5, - "h4": 4, - "img": 1, - "multiple-choice": 1 - }, - "elements": 17 - } - } - }, - { - "id": "item-5a6e6643-3834-4ac5-ae70-0090263759cb", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/installation\/index.html", - "slug": "documentation-1\/haxcms\/installation", - "order": "1", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Installation", - "description": "Generic PHP install directionsHave PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is ", - "metadata": { - "created": 1550643005, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/mampstructure.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/mampstructure.jpg", - "url": "files\/mampstructure.jpg", - "type": "image\/jpeg", - "name": "mampstructure.jpg", - "size": 15099 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/mampstart.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/mampstart.jpg", - "url": "files\/mampstart.jpg", - "type": "image\/jpeg", - "name": "mampstart.jpg", - "size": 12670 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/mamppage.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/mamppage.jpg", - "url": "files\/mamppage.jpg", - "type": "image\/jpeg", - "name": "mamppage.jpg", - "size": 17086 - } - ], - "readtime": 2, - "contentDetails": { - "headings": 6, - "paragraphs": 13, - "schema": [ - { - "resource": "#990ebe5c-04c8-58b2-385a", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - }, - { - "resource": "#4e5cac2b-786f-596c-b394", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "h2": 4, - "p": 13, - "code-sample": 2, - "h3": 2, - "media-image": 2, - "img": 1, - "ul": 1 - }, - "elements": 25 - } - } - }, - { - "id": "item-a91393ea-31f8-30bd-888f-275a05e08e0a", - "indent": "3", - "location": "pages\/documentation-1\/hax-development\/hax-app-store\/blox\/index.html", - "slug": "documentation-1\/hax-development\/hax-app-store\/blox", - "order": "1", - "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", - "title": "blox", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-504d6323-873d-49e3-9de0-ffa56c28fdf5", - "indent": "1", - "location": "pages\/get-involved-1\/index.html", - "slug": "get-involved-1", - "order": "1", - "parent": "item-welcome", - "title": "Get Involved!", - "description": "Join our communityJoin us on the\u00a0HAXTheWeb Slack\u00a0channelJoin us for\u00a0HAXcamp Un-code every Friday 3 pm - 5 pm (EST)Follow \/ use the #HAXTheWeb hash tagJoin our projectsHAXcms - That which ", - "metadata": { - "created": 1553197584, - "updated": 1617805490, - "readtime": 2, - "contentDetails": { - "headings": 3, - "paragraphs": 6, - "schema": [], - "tags": { - "h2": 3, - "ul": 3, - "p": 6, - "meme-maker": 1 - }, - "elements": 13 - } - } - }, - { - "id": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "indent": 0, - "location": "pages\/integrations-1\/index.html", - "slug": "integrations-1", - "order": "1", - "parent": null, - "title": "Integrations", - "description": "HAX provides plenty of ways to integrate into the platforms you already use! Here are some of the plugins and integrations below this heading.Some things a liittle bit crazyCode Pen?!Demonstration", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 1, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "h2": 1, - "ul": 1 - }, - "elements": 3 - } - } - }, - { - "id": "item-3859b3ac-1ef5-45b4-909c-3892f97a9f4c", - "indent": "3", - "location": "pages\/documentation-1\/haxcms\/theming\/skin-a-site\/index.html", - "slug": "documentation-1\/haxcms\/theming\/skin-a-site", - "order": "1", - "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "title": "Skin a site", - "description": "Theme skinning is the easiest way to build a decent looking theme in HAXcms. This method is geared toward people that know CSS and HTML but can't get into the weeds of web components or javascript.Wo", - "metadata": { - "created": 1553354507, - "updated": 1617805490 - } - }, - { - "id": "item-eca7c8a4-393a-4e68-8cb4-440e94683738", - "indent": "2", - "location": "pages\/item-eca7c8a4-393a-4e68-8cb4-440e94683738\/index.html", - "slug": "documentation-1\/ux-concepts\/block-settings", - "order": "1", - "parent": "item-06233713-d866-3351-81da-841d3931144c", - "title": "Block settings", - "description": "Block settings will change contextually based on which block has been selected in the editable area of the page. In this screenshot, a paragraph has been selected and so the icon associated with it is", - "metadata": { - "created": 1597689709, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-42-07.png", - "fullUrl": "\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-42-07.png", - "url": "files\/Screenshot from 2020-08-17 14-42-07.png", - "type": "image\/png", - "name": "Screenshot from 2020-08-17 14-42-07.png", - "size": 46191 - }, - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-46-06.png", - "fullUrl": "\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-46-06.png", - "url": "files\/Screenshot from 2020-08-17 14-46-06.png", - "type": "image\/png", - "name": "Screenshot from 2020-08-17 14-46-06.png", - "size": 66054 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 2, - "paragraphs": 2, - "schema": [], - "tags": { - "p": 2, - "h2": 2, - "img": 2 - }, - "elements": 6 - } - } - }, - { - "id": "item-44a138ea-5122-4a2b-b2ce-8bf1fb11bb29", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/structure\/index.html", - "slug": "documentation-1\/haxcms\/structure", - "order": "2", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Structure", - "description": "By design we've got a very simple structure. The goal of HAXcms isn't to lock you into anything and so we've simplified our file structure over other solutions.The key directories \/ files include:fi", - "metadata": { - "created": 1550643005, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/2019-02-20_01-26-01.png", - "fullUrl": "\/_sites\/haxtheweb\/files\/2019-02-20_01-26-01.png", - "url": "files\/2019-02-20_01-26-01.png", - "type": "image\/png", - "name": "2019-02-20_01-26-01.png", - "size": 19448 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/2019-02-20_01-26-10.png", - "fullUrl": "\/_sites\/haxtheweb\/files\/2019-02-20_01-26-10.png", - "url": "files\/2019-02-20_01-26-10.png", - "type": "image\/png", - "name": "2019-02-20_01-26-10.png", - "size": 59026 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/2019-02-25_16-22-25.png", - "fullUrl": "\/_sites\/haxtheweb\/files\/2019-02-25_16-22-25.png", - "url": "files\/2019-02-25_16-22-25.png", - "type": "image\/png", - "name": "2019-02-25_16-22-25.png", - "size": 37234 - } - ] - } - }, - { - "id": "item-f1c8e3a4-eddb-806a-8a3a-206c1e33f7a9", - "indent": "2", - "location": "pages\/documentation-1\/hax-development\/hax-schema\/index.html", - "slug": "documentation-1\/hax-development\/hax-schema", - "order": "2", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "HAX schema", - "description": "Implementing HAXSchemaIn order for your element to talk to the HAX editor, you need to implement static get haxProperties() on your element. This callback either returns a String based location of ", - "metadata": { - "created": 1548826475, - "updated": 1617979979, - "readtime": 5, - "contentDetails": { - "headings": 6, - "paragraphs": 7, - "schema": [], - "tags": { - "h2": 5, - "p": 7, - "ul": 1, - "code-sample": 5, - "h3": 1, - "grid-plate": 1, - "img": 3 - }, - "elements": 23 - } - } - }, - { - "id": "item-29e7d7f5-db3e-3ef0-733a-ed41d88f2835", - "indent": "1", - "location": "pages\/welcome\/solutions\/index.html", - "slug": "welcome\/solutions", - "order": "2", - "parent": "item-welcome", - "title": "Solutions", - "description": "Modularity is key to HAX success. Here are some of the solutions that HAX provides which leverage the HAXeditor interface.HAX editorHAX or HAXeditor is the editor of the future you're using in this ", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 2, - "contentDetails": { - "headings": 4, - "paragraphs": 9, - "schema": [ - { - "resource": "#832335f3-7442-7d40-0d56", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 9, - "h2": 3, - "h3": 1, - "media-image": 1 - }, - "elements": 14 - }, - "published": true - } - }, - { - "id": "item-17449951-7504-468a-b315-4388b85c00e3", - "indent": "3", - "location": "pages\/documentation-1\/haxcms\/theming\/web-components\/index.html", - "slug": "documentation-1\/haxcms\/theming\/web-components", - "order": "2", - "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "title": "Web components", - "description": "Do you know full on web component development? Well, you can build a new theme from scratch. The best way to learn is by picking a part some of our examples. For this we'll analyze the haxcms-slide-th", - "metadata": { - "created": 1553349518, - "updated": 1617805490 - } - }, - { - "id": "item-5a9ea17e-63ce-96f3-e94f-d5282b290661", - "indent": "1", - "location": "pages\/integrations-1\/wordpress\/index.html", - "slug": "integrations-1\/wordpress", - "order": "2", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "WordPress", - "description": "We support WordPress too! In order to use HAX though you'll want to replace the Gutenberg editor. The following steps will help you get it up and running.Get the Classic Editor. This plugin helps re", - "metadata": { - "created": 1549428503, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "ol": 1 - }, - "elements": 2 - } - } - }, - { - "id": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "indent": 0, - "location": "pages\/documentation-1\/index.html", - "slug": "documentation-1", - "order": "2", - "parent": null, - "title": "Documentation", - "description": "HAX may seem complex, but it's built on a series of standards that will never break. As a result of the complexity of these standards, there are things you should know prior to digging into HAXedito", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 1, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/3450183.png", - "fullUrl": "\/sites\/haxtheweb\/files\/3450183.png", - "url": "files\/3450183.png", - "type": "image\/png", - "name": "3450183.png", - "size": 9992 - } - ], - "contentDetails": { - "headings": 1, - "paragraphs": 3, - "schema": [ - { - "resource": "#5749cf56-70cf-cf6f-508a-b3bc12320734", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 3, - "h2": 1, - "video-player": 1 - }, - "elements": 5 - } - } - }, - { - "id": "item-faaa1198-10c7-ff30-ece6-01b30a9c0f85", - "indent": "3", - "location": "pages\/documentation-1\/hax-development\/hax-app-store\/stax\/index.html", - "slug": "documentation-1\/hax-development\/hax-app-store\/stax", - "order": "2", - "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", - "title": "stax", - "description": "Stax are what most WYSIWYG systems would call Templates. Stax in HAX are a series of HAX element schema's in succession.Below is a definition for the \"example lesson\" seen above. This is a larger ex", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 4 - } - }, - { - "id": "item-251f207e-4046-a4b0-40ce-7c28fe38ae23", - "indent": "2", - "location": "pages\/documentation-1\/ux-concepts\/find\/index.html", - "slug": "documentation-1\/ux-concepts\/find", - "order": "2", - "parent": "item-06233713-d866-3351-81da-841d3931144c", - "title": "Search", - "description": "Search is a data interoperability layer to HAX where web components data binding shines. Search is able to stitch remote data together with local web components in order to streamline workflows. You ", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "published": true, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-36-15.png", - "fullUrl": "\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-36-15.png", - "url": "files\/Screenshot from 2020-08-17 14-36-15.png", - "type": "image\/png", - "name": "Screenshot from 2020-08-17 14-36-15.png", - "size": 135869 - }, - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-43-47.png", - "fullUrl": "\/sites\/haxtheweb\/files\/Screenshot from 2020-08-17 14-43-47.png", - "url": "files\/Screenshot from 2020-08-17 14-43-47.png", - "type": "image\/png", - "name": "Screenshot from 2020-08-17 14-43-47.png", - "size": 105778 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "img": 1 - }, - "elements": 2 - } - } - }, - { - "id": "item-06233713-d866-3351-81da-841d3931144c", - "indent": "1", - "location": "pages\/documentation-1\/ux-concepts\/index.html", - "slug": "documentation-1\/ux-concepts", - "order": "2", - "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "title": "UX concepts", - "description": "The HAX UI can be broken down into three major production concepts. Content authors are either:Adding something they already haveEditing the Settings of the activated element on the pageSearch for ", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "ol": 1 - }, - "elements": 2 - } - } - }, - { - "id": "item-0e4cc53c-944f-658a-5440-eacc5a1c0358", - "indent": "1", - "location": "pages\/documentation-1\/related-technologies\/index.html", - "slug": "documentation-1\/related-technologies", - "order": "3", - "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "title": "Related technologies", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 - } - }, - { - "id": "item-a839d5c1-3321-a395-c032-4ea8ea2cfa27", - "indent": "3", - "location": "pages\/documentation-1\/hax-development\/hax-app-store\/autoloader\/index.html", - "slug": "documentation-1\/hax-development\/hax-app-store\/autoloader", - "order": "3", - "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", - "title": "autoloader", - "description": "Autoloader is waaayyy easier to implement then the other parts of the appstore spec and is probably the most important as it loads all the elements that will be available to your users. All it is is a", - "metadata": { - "created": 1548826475, - "updated": 1617979603, - "readtime": 2, - "contentDetails": { - "headings": 4, - "paragraphs": 5, - "schema": [], - "tags": { - "p": 5, - "ol": 1, - "h3": 1, - "code-sample": 1, - "h4": 3 - }, - "elements": 11 - } - } - }, - { - "id": "item-aa589faa-e860-4221-82fa-df6d57328ac2", - "indent": "2", - "location": "pages\/item-aa589faa-e860-4221-82fa-df6d57328ac2\/index.html", - "slug": "documentation-1\/ux-concepts\/templates-and-layouts", - "order": "3", - "parent": "item-06233713-d866-3351-81da-841d3931144c", - "title": "Templates and Layouts", - "description": "Templates and layouts allow you to drop in pre-built pieces of content structure. This might be a series of images or an example of content that could be written.", - "metadata": { - "created": 1597689709, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [], - "tags": { - "p": 1, - "img": 1 - }, - "elements": 2 - } - } - }, - { - "id": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550", - "indent": "3", - "location": "pages\/documentation-1\/haxcms\/theming\/core-elements\/index.html", - "slug": "documentation-1\/haxcms\/theming\/core-elements", - "order": "3", - "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "title": "Core elements", - "description": "While you're not required to use them, HAXcms supplies a series of elements that can make theme development effortless. You can see the source of these in greater detail under the theme directory of h", - "metadata": { - "created": 1552437937, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/2019-03-12_16-45-51.png", - "fullUrl": "\/_sites\/haxtheweb\/files\/2019-03-12_16-45-51.png", - "url": "files\/2019-03-12_16-45-51.png", - "type": "image\/png", - "name": "2019-03-12_16-45-51.png", - "size": 212153 - } - ] - } - }, - { - "id": "item-49d727fb-b5c8-871a-3979-a5143116946d", - "indent": 0, - "location": "pages\/f-a-q-1\/index.html", - "slug": "f-a-q-1", - "order": "3", - "parent": null, - "title": "F.A.Q.", - "description": "Are web components ready for prime time?Yes. Web components effectively\u00a0turn the HTML of a site into a consistent API. HAXeditor leverages this approach and standardizes its usage in order to suppl", - "metadata": { - "created": 1548826475, - "updated": 1617806639, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/pubwork1.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/pubwork1.jpg", - "url": "files\/pubwork1.jpg", - "type": "image\/jpeg", - "name": "pubwork1.jpg", - "size": 51662 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/IMG_20190127_153429.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/IMG_20190127_153429.jpg", - "url": "files\/IMG_20190127_153429.jpg", - "type": "image\/jpeg", - "name": "IMG_20190127_153429.jpg", - "size": 27242 - } - ], - "readtime": 5, - "contentDetails": { - "headings": 6, - "paragraphs": 11, - "schema": [], - "tags": { - "h2": 6, - "p": 11, - "ul": 3 - }, - "elements": 20 - }, - "published": true - } - }, - { - "id": "item-ca8c6ba8-c012-8ace-343a-3701f20609e9", - "indent": "1", - "location": "pages\/integrations-1\/drupal\/index.html", - "slug": "integrations-1\/drupal", - "order": "3", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "Drupal", - "description": "Try on SimplyTest.meTry HAX on Simplytest me in a few steps without needing to install anythingGo to Simplytest me and pick HAX modulePick 9.x,8.x or 7.xLog in, go to Administration -> Configurat", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/scale-50\/d8cdnimage.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/scale-50\/d8cdnimage.jpg", - "url": "files\/scale-50\/d8cdnimage.jpg", - "type": "image\/jpeg", - "name": "d8cdnimage.jpg", - "size": 136928 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/scale-50\/haxd8simply.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/scale-50\/haxd8simply.jpg", - "url": "files\/scale-50\/haxd8simply.jpg", - "type": "image\/jpeg", - "name": "haxd8simply.jpg", - "size": 91967 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 3, - "paragraphs": 3, - "schema": [ - { - "resource": "#3b994c7f-952f-e85f-48b3", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "h2": 2, - "p": 3, - "ol": 2, - "grid-plate": 1, - "h3": 1, - "wikipedia-query": 1 - }, - "elements": 10 - } - } - }, - { - "id": "item-01e0f49a-190a-4c8d-ae0e-83d62675e070", - "indent": "1", - "location": "pages\/welcome\/roadmap-1\/index.html", - "slug": "welcome\/roadmap-1", - "order": "3", - "parent": "item-welcome", - "title": "Roadmap", - "description": "HAX encompasses many different projectsThis roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements a", - "metadata": { - "created": 1565290387, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/\/haxrelationships.jpg", - "fullUrl": "\/sites\/haxtheweb\/files\/haxrelationships.jpg", - "url": "files\/haxrelationships.jpg", - "type": "image\/jpeg", - "name": "haxrelationships.jpg", - "size": 88416 - }, - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/\/Roadmap.jpg", - "fullUrl": "\/sites\/haxtheweb\/files\/Roadmap.jpg", - "url": "files\/Roadmap.jpg", - "type": "image\/jpeg", - "name": "Roadmap.jpg", - "size": 108725 - }, - { - "path": "\/var\/www\/html\/sites\/haxtheweb\/files\/headshot272229.61999999825.jpg", - "fullUrl": "\/sites\/haxtheweb\/files\/headshot272229.61999999825.jpg", - "url": "files\/headshot272229.61999999825.jpg", - "type": "image\/jpeg", - "name": "headshot272229.61999999825.jpg", - "size": 121898 - } - ], - "readtime": 1, - "contentDetails": { - "headings": 2, - "paragraphs": 6, - "schema": [], - "tags": { - "h3": 2, - "p": 6, - "img": 2 - }, - "elements": 10 - } - } - }, - { - "id": "item-5df45272-f6b9-4f4f-b650-16c47aeac6fb", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/publishing\/index.html", - "slug": "documentation-1\/haxcms\/publishing", - "order": "3", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Publishing", - "description": "HAXcms requires being published in order to be visible to other people. Working locally or on Desktop or on a server, is akin to you writing a document on your computer. It's not shared with anyone. W", - "metadata": { - "created": 1550643005, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/gitpublishingdata.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/gitpublishingdata.jpg", - "url": "files\/gitpublishingdata.jpg", - "type": "image\/jpeg", - "name": "gitpublishingdata.jpg", - "size": 12847 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/pubwork1.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/pubwork1.jpg", - "url": "files\/pubwork1.jpg", - "type": "image\/jpeg", - "name": "pubwork1.jpg", - "size": 51662 - }, - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/pubwork2.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/pubwork2.jpg", - "url": "files\/pubwork2.jpg", - "type": "image\/jpeg", - "name": "pubwork2.jpg", - "size": 70772 - } - ] - } - }, - { - "id": "item-44cc230b-07db-442a-90cf-687e2d089a5d", - "indent": "2", - "location": "pages\/item-44cc230b-07db-442a-90cf-687e2d089a5d\/index.html", - "slug": "haxhooks", - "order": "3", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "haxHooks", - "description": "Elements can integrate deeply into HAX state management using what we call \"hax hooks\". By supplying a method on your web component like haxHooks()\u00a0you are magically able to tap into different li", - "metadata": { - "created": 1617802345, - "updated": 1617805490, - "readtime": 5, - "contentDetails": { - "headings": 10, - "paragraphs": 11, - "schema": [], - "tags": { - "p": 11, - "h2": 2, - "ul": 2, - "code-sample": 1, - "h3": 8 - }, - "elements": 24 - } - } - }, - { - "id": "item-c86470aa-0295-4c9d-9f17-48ad79ab05be", - "indent": "1", - "location": "pages\/welcome\/presentations\/index.html", - "slug": "welcome\/presentations", - "order": "4", - "parent": "item-welcome", - "title": "Presentations", - "description": "This is the youtube playlist of all things HAXTheWebThis playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists relat", - "metadata": { - "created": 1552910817, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 2, - "schema": [], - "tags": { - "p": 2, - "iframe": 1 - }, - "elements": 3 - } - } - }, - { - "id": "item-4824986b-1897-568d-fdd9-4b882ea6ee1f", - "indent": "1", - "location": "pages\/integrations-1\/backdropcms\/index.html", - "slug": "integrations-1\/backdropcms", - "order": "4", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "BackdropCMS", - "description": "Getting HAX setup in BackdropCMSSearch for HAX on BackdropCMS.org\u00a0or from within your Backdrop siteFollow the instructions in the Web components module README\u00a0for buildingDon't worry, HAX requ", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 1, - "paragraphs": 1, - "schema": [ - { - "resource": "#5b790bef-7d78-f85e-104d", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 1, - "h2": 1, - "ol": 1, - "media-image": 1 - }, - "elements": 4 - } - } - }, - { - "id": "item-7ab2e2fd-622f-4a0f-9967-599410c6cd43", - "indent": 0, - "location": "pages\/scavenger-hunt-1\/index.html", - "slug": "scavenger-hunt-1", - "order": "4", - "parent": null, - "title": "Scavenger Hunt", - "description": "Become part of our dynasty franchise **by wearing a cool jerseyWe're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next ev", - "metadata": { - "created": 1563970537, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 1, - "paragraphs": 2, - "schema": [ - { - "typeof": "oer:SupportingMaterial", - "resource": "#238ee75a-de4d-02a9-3755", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "h3": 1, - "p": 2, - "ul": 1, - "task-list": 1, - "meme-maker": 1 - }, - "elements": 6 - } - } - }, - { - "id": "item-7f3dd690-4c3f-4616-baa5-159b9a15809c", - "indent": "3", - "location": "pages\/documentation-1\/haxcms\/theming\/dev-workflows\/index.html", - "slug": "documentation-1\/haxcms\/theming\/dev-workflows", - "order": "4", - "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "title": "Dev workflows", - "description": "Our development workflow is as follows (for themes)All custom theme work happens in your _config directoryMake my-theme.js, pull everything together, either in this directory or in a wcfactory cat", - "metadata": { - "created": 1553349518, - "updated": 1617805490 + { + "id": "item-36c4fc60-67c0-43c2-8f71-c6a117e8b7d6", + "indent": "4", + "location": "pages/documentation-1/haxcms/theming/core-elements/query-examples/index.html", + "slug": "documentation-1/haxcms/theming/core-elements/query-examples", + "order": "0", + "parent": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550", + "title": "Query examples", + "description": " Hold up there. You didn't cover any of the query tags in that last section!Ok ok, here's the deal. Queries are so important that they needed their own section. Calm down Dwight we'll handle that n", + "metadata": { + "created": 1553349518, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/2019-03-23_10-51-10.jpg", + "fullUrl": "/_sites/haxtheweb/files/2019-03-23_10-51-10.jpg", + "url": "files/2019-03-23_10-51-10.jpg", + "type": "image/jpeg", + "name": "2019-03-23_10-51-10.jpg", + "size": 54637 + } + ] + } + }, + { + "id": "item-asd7dab5-8208-65e3-c3e4-267f233f60553", + "indent": "1", + "location": "pages/welcome/what-is-hax/index.html", + "slug": "welcome/what-is-hax", + "order": "0", + "parent": "item-welcome", + "title": "What is HAX", + "description": "HAX - Headless Authoring eXperienceHAX is a WYSIWYG unlike any other. You extend your world by extending the web through the web component standard. HAX has a simple schema and integrations to allow", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files//sourceviewthispage.jpg", + "fullUrl": "/sites/haxtheweb/files/sourceviewthispage.jpg", + "url": "files/sourceviewthispage.jpg", + "type": "image/jpeg", + "name": "sourceviewthispage.jpg", + "size": 34616 + } + ], + "readtime": 2, + "contentDetails": { + "headings": 4, + "paragraphs": 8, + "schema": [], + "tags": { + "full-width-image": 1, + "h2": 4, + "p": 8, + "code-sample": 1, + "meme-maker": 1, + "ul": 1, + "img": 1 + }, + "elements": 17 + } + } + }, + { + "id": "item-692eb91c-4003-3429-5d9f-caac64691849", + "indent": "2", + "location": "pages/documentation-1/hax-development/wcfactory-tooling/index.html", + "slug": "documentation-1/hax-development/wcfactory-tooling", + "order": "0", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "WCFactory Tooling", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-welcome", + "indent": 0, + "location": "pages/welcome/index.html", + "slug": "welcome", + "order": 0, + "parent": null, + "title": "Our Mission", + "description": "We're on a mission to empower the next billion creators to share their voice with the world and in doing so, create a less toxic web. Regardless offfff ability, platform,tribe or income", + "metadata": { + "created": 1548826475, + "updated": 1661452015, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/demo.csv", + "fullUrl": "/_sites/haxtheweb/files/demo.csv", + "url": "files/demo.csv", + "type": "text/plain", + "name": "demo.csv", + "size": 830 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/demo.csv", + "fullUrl": "/_sites/haxtheweb/files/demo.csv", + "url": "files/demo.csv", + "type": "text/plain", + "name": "demo.csv", + "size": 830 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/ngdle.png", + "fullUrl": "/_sites/haxtheweb/files/ngdle.png", + "url": "files/ngdle.png", + "type": "image/png", + "name": "ngdle.png", + "size": 307196 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 2, + "paragraphs": 6, + "schema": [ + { + "resource": "#13f8e41a-3150-15b2-162c-327f1132477f", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " + }, + { + "resource": "#18d556e9-a1d7-3069-81d9", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } + ], + "tags": { + "page-break": 1, + "p": 6, + "grid-plate": 1, + "video-player": 1, + "code-sample": 1, + "h3": 2, + "ul": 1 + }, + "elements": 13 }, - { - "id": "item-e6daa06e-dfd2-43a4-ade8-0c0ded24e0b4", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/life-cycle\/index.html", - "slug": "documentation-1\/haxcms\/life-cycle", - "order": "4", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Life cycle", - "description": "This is a general life cycle that happens when HAXcms \"boots up\". When web components are unpacking the contents of what to do it generally will work this way.page load, should it be no-js or a web c", - "metadata": { - "created": 1554496047, - "updated": 1617805490, - "readtime": 3, - "contentDetails": { - "headings": 3, - "paragraphs": 5, - "schema": [], - "tags": { - "p": 5, - "ul": 3, - "h2": 1, - "code-sample": 1, - "h3": 2 - }, - "elements": 12 - } + "published": true, + "locked": false + } + }, + { + "id": "item-96d00871-d866-c65e-b7f0-4e242bde5b15", + "indent": "3", + "location": "pages/documentation-1/hax-development/hax-app-store/apps/index.html", + "slug": "documentation-1/hax-development/hax-app-store/apps", + "order": "0", + "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", + "title": "apps", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-f0af8879-a79c-4d1c-afc4-e23c32f52dc4", + "indent": "3", + "location": "pages/documentation-1/haxcms/theming/css-vars/index.html", + "slug": "documentation-1/haxcms/theming/css-vars", + "order": "0", + "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "title": "CSS vars", + "description": "CSS can be modified via CSS variables. CSS variables create a happy middle ground between the constraints of Shadow DOM (namely that styles are fully encapsulated) and designers wanting flexibility a", + "metadata": { + "created": 1553349518, + "updated": 1617805490 + } + }, + { + "id": "item-dfd62788-ba48-4051-a869-986e5956864f", + "indent": "2", + "location": "pages/documentation-1/haxcms/concepts/index.html", + "slug": "documentation-1/haxcms/concepts", + "order": "0", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Concepts", + "description": "HAXcms seeks to be a microsite generator and manager that doesn't require any command line in order to operate. HAXcms leverages HAX to give a best in class authoring experience while HAXcms seeks to", + "metadata": { + "created": 1550643005, + "updated": 1617805490 + } + }, + { + "id": "item-e3dafe1a-1f50-1834-68f3-9f378e4ddda5", + "indent": "2", + "location": "pages/documentation-1/ux-concepts/add/index.html", + "slug": "documentation-1/ux-concepts/add", + "order": "0", + "parent": "item-06233713-d866-3351-81da-841d3931144c", + "title": "Add Content", + "description": "Add Content is how you create and add complex blocks to the HAX page editor. These blocks can be variable based on what you chose to include (see appstore) but ultimately are just adding web compon", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-34-32.png", + "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-34-32.png", + "url": "files/Screenshot from 2020-08-17 14-34-32.png", + "type": "image/png", + "name": "Screenshot from 2020-08-17 14-34-32.png", + "size": 78391 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "img": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-275a0928-60ab-b7ce-c2b6-d0e35826498b", + "indent": "1", + "location": "pages/documentation-1/core-concepts/index.html", + "slug": "documentation-1/core-concepts", + "order": "1", + "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "title": "Core concepts", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-39074718-758f-d51b-1dc5-15cfbb79e44c", + "indent": "2", + "location": "pages/documentation-1/hax-development/hello-world-element/index.html", + "slug": "documentation-1/hax-development/hello-world-element", + "order": "1", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "hello-world element", + "description": "Let's see what goes into the element called @lrnwebcomponents/example-hax-element in order to learn how we can wire anything up to HAXeditor.@lrnwebcomponents/example-hax-element/example-hax-elem", + "metadata": { + "created": 1548826475, + "updated": 1617806663, + "readtime": 1, + "contentDetails": { + "headings": 1, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "h2": 1, + "code-sample": 1 + }, + "elements": 3 + } + } + }, + { + "id": "item-650eaa59-478c-4674-8ef3-93e4b43e2310", + "indent": "1", + "location": "pages/welcome/why-haxcms-1/index.html", + "slug": "welcome/why-haxcms-1", + "order": "1", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "HAXcms", + "description": "HAXcms powers this website and is a hybrid static site generator, a new class of CMS. It's hybrid in that everything is written to static like a static site generator and it's 100% decoupled via web ", + "metadata": { + "created": 1563972322, + "updated": 1617805490, + "readtime": 2, + "contentDetails": { + "headings": 6, + "paragraphs": 5, + "schema": [ + { + "typeof": "oer:Assessment", + "resource": "#dd2feacf-ed4a-dcb0-b85d", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-4bce3546-4d53-4456-8eae-494c79180229", - "indent": "1", - "location": "pages\/documentation-1\/haxcms\/index.html", - "slug": "documentation-1\/haxcms", - "order": "4", - "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", - "title": "HAXcms", - "description": "HAXcms, that which powers the site you are currently reading is a powerful \"static site generator\" paradigm. It leverages server technology in order to orchestrate a static site. That way the \"server\"", - "metadata": { - "created": 1550643005, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/HAXCms workflow.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/HAXCms workflow.jpg", - "url": "files\/HAXCms workflow.jpg", - "type": "image\/jpeg", - "name": "HAXCms workflow.jpg", - "size": 72736 - } - ] + ], + "tags": { + "grid-plate": 1, + "h2": 2, + "ul": 3, + "p": 5, + "h4": 4, + "img": 1, + "multiple-choice": 1 + }, + "elements": 17 + } + } + }, + { + "id": "item-5a6e6643-3834-4ac5-ae70-0090263759cb", + "indent": "2", + "location": "pages/documentation-1/haxcms/installation/index.html", + "slug": "documentation-1/haxcms/installation", + "order": "1", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Installation", + "description": "Generic PHP install directionsHave PHP? well then you can setup HAXcms pretty quick. Just download HAXcms and navigate to its directory in a browser. It'll attempt to automatically install (which is ", + "metadata": { + "created": 1550643005, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/mampstructure.jpg", + "fullUrl": "/_sites/haxtheweb/files/mampstructure.jpg", + "url": "files/mampstructure.jpg", + "type": "image/jpeg", + "name": "mampstructure.jpg", + "size": 15099 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/mampstart.jpg", + "fullUrl": "/_sites/haxtheweb/files/mampstart.jpg", + "url": "files/mampstart.jpg", + "type": "image/jpeg", + "name": "mampstart.jpg", + "size": 12670 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/mamppage.jpg", + "fullUrl": "/_sites/haxtheweb/files/mamppage.jpg", + "url": "files/mamppage.jpg", + "type": "image/jpeg", + "name": "mamppage.jpg", + "size": 17086 + } + ], + "readtime": 2, + "contentDetails": { + "headings": 6, + "paragraphs": 13, + "schema": [ + { + "resource": "#990ebe5c-04c8-58b2-385a", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " + }, + { + "resource": "#4e5cac2b-786f-596c-b394", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-cdd303d0-4490-4433-94fa-0e78cf849e80", - "indent": "2", - "location": "pages\/item-cdd303d0-4490-4433-94fa-0e78cf849e80\/index.html", - "slug": "documentation-1\/hax-development\/internationalization-i18n", - "order": "4", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "Internationalization - i18n", - "description": "We've created a way to internationalize ANY web component you create. Because this is a complex topic, and we seek to empower anyone, anywhere to work with web components; i18n is a critical piece of ", - "metadata": { - "created": 1617805490, - "updated": 1617806250, - "readtime": 2, - "contentDetails": { - "headings": 1, - "paragraphs": 3, - "schema": [], - "tags": { - "p": 3, - "a": 1, - "h3": 1, - "ul": 1, - "code-sample": 2 - }, - "elements": 8 - } + ], + "tags": { + "h2": 4, + "p": 13, + "code-sample": 2, + "h3": 2, + "media-image": 2, + "img": 1, + "ul": 1 + }, + "elements": 25 + } + } + }, + { + "id": "item-a91393ea-31f8-30bd-888f-275a05e08e0a", + "indent": "3", + "location": "pages/documentation-1/hax-development/hax-app-store/blox/index.html", + "slug": "documentation-1/hax-development/hax-app-store/blox", + "order": "1", + "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", + "title": "blox", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-504d6323-873d-49e3-9de0-ffa56c28fdf5", + "indent": "1", + "location": "pages/get-involved-1/index.html", + "slug": "get-involved-1", + "order": "1", + "parent": "item-welcome", + "title": "Get Involved!", + "description": "Join our communityJoin us on the HAXTheWeb Slack channelJoin us for HAXcamp Un-code every Friday 3 pm - 5 pm (EST)Follow / use the #HAXTheWeb hash tagJoin our projectsHAXcms - That which ", + "metadata": { + "created": 1553197584, + "updated": 1617805490, + "readtime": 2, + "contentDetails": { + "headings": 3, + "paragraphs": 6, + "schema": [], + "tags": { + "h2": 3, + "ul": 3, + "p": 6, + "meme-maker": 1 + }, + "elements": 13 + } + } + }, + { + "id": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "indent": 0, + "location": "pages/integrations-1/index.html", + "slug": "integrations-1", + "order": "1", + "parent": null, + "title": "Integrations", + "description": "HAX provides plenty of ways to integrate into the platforms you already use! Here are some of the plugins and integrations below this heading.Some things a liittle bit crazyCode Pen?!Demonstration", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 1, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "h2": 1, + "ul": 1 + }, + "elements": 3 + } + } + }, + { + "id": "item-3859b3ac-1ef5-45b4-909c-3892f97a9f4c", + "indent": "3", + "location": "pages/documentation-1/haxcms/theming/skin-a-site/index.html", + "slug": "documentation-1/haxcms/theming/skin-a-site", + "order": "1", + "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "title": "Skin a site", + "description": "Theme skinning is the easiest way to build a decent looking theme in HAXcms. This method is geared toward people that know CSS and HTML but can't get into the weeds of web components or javascript.Wo", + "metadata": { + "created": 1553354507, + "updated": 1617805490 + } + }, + { + "id": "item-eca7c8a4-393a-4e68-8cb4-440e94683738", + "indent": "2", + "location": "pages/item-eca7c8a4-393a-4e68-8cb4-440e94683738/index.html", + "slug": "documentation-1/ux-concepts/block-settings", + "order": "1", + "parent": "item-06233713-d866-3351-81da-841d3931144c", + "title": "Block settings", + "description": "Block settings will change contextually based on which block has been selected in the editable area of the page. In this screenshot, a paragraph has been selected and so the icon associated with it is", + "metadata": { + "created": 1597689709, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-42-07.png", + "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-42-07.png", + "url": "files/Screenshot from 2020-08-17 14-42-07.png", + "type": "image/png", + "name": "Screenshot from 2020-08-17 14-42-07.png", + "size": 46191 + }, + { + "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-46-06.png", + "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-46-06.png", + "url": "files/Screenshot from 2020-08-17 14-46-06.png", + "type": "image/png", + "name": "Screenshot from 2020-08-17 14-46-06.png", + "size": 66054 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 2, + "paragraphs": 2, + "schema": [], + "tags": { + "p": 2, + "h2": 2, + "img": 2 + }, + "elements": 6 + } + } + }, + { + "id": "item-44a138ea-5122-4a2b-b2ce-8bf1fb11bb29", + "indent": "2", + "location": "pages/documentation-1/haxcms/structure/index.html", + "slug": "documentation-1/haxcms/structure", + "order": "2", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Structure", + "description": "By design we've got a very simple structure. The goal of HAXcms isn't to lock you into anything and so we've simplified our file structure over other solutions.The key directories / files include:fi", + "metadata": { + "created": 1550643005, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/2019-02-20_01-26-01.png", + "fullUrl": "/_sites/haxtheweb/files/2019-02-20_01-26-01.png", + "url": "files/2019-02-20_01-26-01.png", + "type": "image/png", + "name": "2019-02-20_01-26-01.png", + "size": 19448 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/2019-02-20_01-26-10.png", + "fullUrl": "/_sites/haxtheweb/files/2019-02-20_01-26-10.png", + "url": "files/2019-02-20_01-26-10.png", + "type": "image/png", + "name": "2019-02-20_01-26-10.png", + "size": 59026 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/2019-02-25_16-22-25.png", + "fullUrl": "/_sites/haxtheweb/files/2019-02-25_16-22-25.png", + "url": "files/2019-02-25_16-22-25.png", + "type": "image/png", + "name": "2019-02-25_16-22-25.png", + "size": 37234 + } + ] + } + }, + { + "id": "item-f1c8e3a4-eddb-806a-8a3a-206c1e33f7a9", + "indent": "2", + "location": "pages/documentation-1/hax-development/hax-schema/index.html", + "slug": "documentation-1/hax-development/hax-schema", + "order": "2", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "HAX schema", + "description": "Implementing HAXSchemaIn order for your element to talk to the HAX editor, you need to implement static get haxProperties() on your element. This callback either returns a String based location of ", + "metadata": { + "created": 1548826475, + "updated": 1617979979, + "readtime": 5, + "contentDetails": { + "headings": 6, + "paragraphs": 7, + "schema": [], + "tags": { + "h2": 5, + "p": 7, + "ul": 1, + "code-sample": 5, + "h3": 1, + "grid-plate": 1, + "img": 3 + }, + "elements": 23 + } + } + }, + { + "id": "item-29e7d7f5-db3e-3ef0-733a-ed41d88f2835", + "indent": "1", + "location": "pages/welcome/solutions/index.html", + "slug": "welcome/solutions", + "order": "2", + "parent": "item-welcome", + "title": "Solutions", + "description": "Modularity is key to HAX success. Here are some of the solutions that HAX provides which leverage the HAXeditor interface.HAX editorHAX or HAXeditor is the editor of the future you're using in this ", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 2, + "contentDetails": { + "headings": 4, + "paragraphs": 9, + "schema": [ + { + "resource": "#832335f3-7442-7d40-0d56", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } + ], + "tags": { + "p": 9, + "h2": 3, + "h3": 1, + "media-image": 1 + }, + "elements": 14 }, - { - "id": "item-52727dcf-a7d5-90e9-c459-a4a53dd07ffd", - "indent": "2", - "location": "pages\/documentation-1\/hax-development\/hax-element-schema\/index.html", - "slug": "documentation-1\/hax-development\/hax-element-schema", - "order": "5", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "HAX Element Schema", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 + "published": true + } + }, + { + "id": "item-17449951-7504-468a-b315-4388b85c00e3", + "indent": "3", + "location": "pages/documentation-1/haxcms/theming/web-components/index.html", + "slug": "documentation-1/haxcms/theming/web-components", + "order": "2", + "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "title": "Web components", + "description": "Do you know full on web component development? Well, you can build a new theme from scratch. The best way to learn is by picking a part some of our examples. For this we'll analyze the haxcms-slide-th", + "metadata": { + "created": 1553349518, + "updated": 1617805490 + } + }, + { + "id": "item-5a9ea17e-63ce-96f3-e94f-d5282b290661", + "indent": "1", + "location": "pages/integrations-1/wordpress/index.html", + "slug": "integrations-1/wordpress", + "order": "2", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "WordPress", + "description": "We support WordPress too! In order to use HAX though you'll want to replace the Gutenberg editor. The following steps will help you get it up and running.Get the Classic Editor. This plugin helps re", + "metadata": { + "created": 1549428503, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "ol": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "indent": 0, + "location": "pages/documentation-1/index.html", + "slug": "documentation-1", + "order": 2, + "parent": null, + "title": "Documentation", + "description": "HAX may seem complex, but it's built on a series of standards that will never break. As a result of the complexity of these standards, there are things you should know prior to digging into HAXedit", + "metadata": { + "created": 1548826475, + "updated": 1661452038, + "readtime": 1, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files/3450183.png", + "fullUrl": "/sites/haxtheweb/files/3450183.png", + "url": "files/3450183.png", + "type": "image/png", + "name": "3450183.png", + "size": 9992 + } + ], + "contentDetails": { + "headings": 1, + "paragraphs": 3, + "schema": [ + { + "resource": "#4e04ff57-98de-f227-681f-d3425ba60f04", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } + ], + "tags": { + "page-break": 1, + "p": 3, + "h3": 1, + "grid-plate": 1 + }, + "elements": 6 }, - { - "id": "item-5dede24a-2de7-4fae-a00b-31e8121e3c16", - "indent": "1", - "location": "pages\/welcome\/i-have-issues\/index.html", - "slug": "welcome\/i-have-issues", - "order": "5", - "parent": "item-welcome", - "title": "I have issues", - "description": "You have a problem or would like to contribute to anything in our universe? That's awesome! All issues, feature requests and general thumbs up should happen in our issue queue on github:\u00a0https:\/\/gith", - "metadata": { - "created": 1553556295, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 1, - "schema": [ - { - "resource": "#b54c9847-4d26-90ae-d748", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 1, - "a11y-gif-player": 1 - }, - "elements": 2 - } + "published": true, + "locked": false + } + }, + { + "id": "item-faaa1198-10c7-ff30-ece6-01b30a9c0f85", + "indent": "3", + "location": "pages/documentation-1/hax-development/hax-app-store/stax/index.html", + "slug": "documentation-1/hax-development/hax-app-store/stax", + "order": "2", + "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", + "title": "stax", + "description": "Stax are what most WYSIWYG systems would call Templates. Stax in HAX are a series of HAX element schema's in succession.Below is a definition for the \"example lesson\" seen above. This is a larger ex", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 4 + } + }, + { + "id": "item-251f207e-4046-a4b0-40ce-7c28fe38ae23", + "indent": "2", + "location": "pages/documentation-1/ux-concepts/find/index.html", + "slug": "documentation-1/ux-concepts/find", + "order": "2", + "parent": "item-06233713-d866-3351-81da-841d3931144c", + "title": "Search", + "description": "Search is a data interoperability layer to HAX where web components data binding shines. Search is able to stitch remote data together with local web components in order to streamline workflows. You ", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "published": true, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-36-15.png", + "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-36-15.png", + "url": "files/Screenshot from 2020-08-17 14-36-15.png", + "type": "image/png", + "name": "Screenshot from 2020-08-17 14-36-15.png", + "size": 135869 + }, + { + "path": "/var/www/html/sites/haxtheweb/files/Screenshot from 2020-08-17 14-43-47.png", + "fullUrl": "/sites/haxtheweb/files/Screenshot from 2020-08-17 14-43-47.png", + "url": "files/Screenshot from 2020-08-17 14-43-47.png", + "type": "image/png", + "name": "Screenshot from 2020-08-17 14-43-47.png", + "size": 105778 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "img": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-06233713-d866-3351-81da-841d3931144c", + "indent": "1", + "location": "pages/documentation-1/ux-concepts/index.html", + "slug": "documentation-1/ux-concepts", + "order": "2", + "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "title": "UX concepts", + "description": "The HAX UI can be broken down into three major production concepts. Content authors are either:Adding something they already haveEditing the Settings of the activated element on the pageSearch for ", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "ol": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-0e4cc53c-944f-658a-5440-eacc5a1c0358", + "indent": "1", + "location": "pages/documentation-1/related-technologies/index.html", + "slug": "documentation-1/related-technologies", + "order": "3", + "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "title": "Related technologies", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-a839d5c1-3321-a395-c032-4ea8ea2cfa27", + "indent": "3", + "location": "pages/documentation-1/hax-development/hax-app-store/autoloader/index.html", + "slug": "documentation-1/hax-development/hax-app-store/autoloader", + "order": "3", + "parent": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", + "title": "autoloader", + "description": "Autoloader is waaayyy easier to implement then the other parts of the appstore spec and is probably the most important as it loads all the elements that will be available to your users. All it is is a", + "metadata": { + "created": 1548826475, + "updated": 1617979603, + "readtime": 2, + "contentDetails": { + "headings": 4, + "paragraphs": 5, + "schema": [], + "tags": { + "p": 5, + "ol": 1, + "h3": 1, + "code-sample": 1, + "h4": 3 + }, + "elements": 11 + } + } + }, + { + "id": "item-aa589faa-e860-4221-82fa-df6d57328ac2", + "indent": "2", + "location": "pages/item-aa589faa-e860-4221-82fa-df6d57328ac2/index.html", + "slug": "documentation-1/ux-concepts/templates-and-layouts", + "order": "3", + "parent": "item-06233713-d866-3351-81da-841d3931144c", + "title": "Templates and Layouts", + "description": "Templates and layouts allow you to drop in pre-built pieces of content structure. This might be a series of images or an example of content that could be written.", + "metadata": { + "created": 1597689709, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [], + "tags": { + "p": 1, + "img": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-a84c35ec-85c8-4c7c-b4ab-80c2fbc87550", + "indent": "3", + "location": "pages/documentation-1/haxcms/theming/core-elements/index.html", + "slug": "documentation-1/haxcms/theming/core-elements", + "order": "3", + "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "title": "Core elements", + "description": "While you're not required to use them, HAXcms supplies a series of elements that can make theme development effortless. You can see the source of these in greater detail under the theme directory of h", + "metadata": { + "created": 1552437937, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/2019-03-12_16-45-51.png", + "fullUrl": "/_sites/haxtheweb/files/2019-03-12_16-45-51.png", + "url": "files/2019-03-12_16-45-51.png", + "type": "image/png", + "name": "2019-03-12_16-45-51.png", + "size": 212153 + } + ] + } + }, + { + "id": "item-49d727fb-b5c8-871a-3979-a5143116946d", + "indent": 0, + "location": "pages/f-a-q-1/index.html", + "slug": "f-a-q-1", + "order": 3, + "parent": null, + "title": "F.A.Q.", + "description": "Are web components ready for prime time?Yes. Web components effectively turn the HTML of a site into a consistent API. HAXeditor leverages this approach and standardizes its usage in order to ", + "metadata": { + "created": 1548826475, + "updated": 1661452776, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/pubwork1.jpg", + "fullUrl": "/_sites/haxtheweb/files/pubwork1.jpg", + "url": "files/pubwork1.jpg", + "type": "image/jpeg", + "name": "pubwork1.jpg", + "size": 51662 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/IMG_20190127_153429.jpg", + "fullUrl": "/_sites/haxtheweb/files/IMG_20190127_153429.jpg", + "url": "files/IMG_20190127_153429.jpg", + "type": "image/jpeg", + "name": "IMG_20190127_153429.jpg", + "size": 27242 + } + ], + "readtime": 5, + "contentDetails": { + "headings": 6, + "paragraphs": 11, + "schema": [ + { + "resource": "#4afe6e57-7d57-53d4-cca3-2512c120ffcc", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } + ], + "tags": { + "page-break": 1, + "h2": 6, + "p": 11, + "ul": 3 + }, + "elements": 21 }, - { - "id": "item-677468f6-7bff-4bb6-bd2a-18520d88b3c4", - "indent": "1", - "location": "pages\/integrations-1\/classicpress-1\/index.html", - "slug": "integrations-1\/classicpress-1", - "order": "5", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "ClassicPress", - "description": "ClassicPress is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original!Get the HAX plugin\u00a0from the wordpress registryGo to edit \/ create a page\/post ", - "metadata": { - "created": 1565279009, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 1, - "paragraphs": 2, - "schema": [ - { - "resource": "#85219ed3-d806-24d7-5c02", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 2, - "ol": 1, - "h2": 1, - "video-player": 1 - }, - "elements": 5 - } + "published": true, + "locked": false + } + }, + { + "id": "item-ca8c6ba8-c012-8ace-343a-3701f20609e9", + "indent": "1", + "location": "pages/integrations-1/drupal/index.html", + "slug": "integrations-1/drupal", + "order": "3", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "Drupal", + "description": "Try on SimplyTest.meTry HAX on Simplytest me in a few steps without needing to install anythingGo to Simplytest me and pick HAX modulePick 9.x,8.x or 7.xLog in, go to Administration -> Configurat", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/scale-50/d8cdnimage.jpg", + "fullUrl": "/_sites/haxtheweb/files/scale-50/d8cdnimage.jpg", + "url": "files/scale-50/d8cdnimage.jpg", + "type": "image/jpeg", + "name": "d8cdnimage.jpg", + "size": 136928 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/scale-50/haxd8simply.jpg", + "fullUrl": "/_sites/haxtheweb/files/scale-50/haxd8simply.jpg", + "url": "files/scale-50/haxd8simply.jpg", + "type": "image/jpeg", + "name": "haxd8simply.jpg", + "size": 91967 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 3, + "paragraphs": 3, + "schema": [ + { + "resource": "#3b994c7f-952f-e85f-48b3", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-c7500902-9aed-4117-8949-a6597a02dada", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/troubleshooting\/index.html", - "slug": "documentation-1\/haxcms\/troubleshooting", - "order": "5", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Troubleshooting", - "description": "These are some common issues \/ resolutions in HAXcms related to installation, publishing, etc.I installed HAXcms and forgot my passwordYour username and password can be found in _config\/config.php o", - "metadata": { - "created": 1553555764, - "updated": 1617805490 + ], + "tags": { + "h2": 2, + "p": 3, + "ol": 2, + "grid-plate": 1, + "h3": 1, + "wikipedia-query": 1 + }, + "elements": 10 + } + } + }, + { + "id": "item-01e0f49a-190a-4c8d-ae0e-83d62675e070", + "indent": "1", + "location": "pages/welcome/roadmap-1/index.html", + "slug": "welcome/roadmap-1", + "order": "3", + "parent": "item-welcome", + "title": "Roadmap", + "description": "HAX encompasses many different projectsThis roadmap illustrates all the projects related to HAX and ELMS:LN, which HAX comes from. The little settings gears found throughout illustrate enhancements a", + "metadata": { + "created": 1565290387, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/sites/haxtheweb/files//haxrelationships.jpg", + "fullUrl": "/sites/haxtheweb/files/haxrelationships.jpg", + "url": "files/haxrelationships.jpg", + "type": "image/jpeg", + "name": "haxrelationships.jpg", + "size": 88416 + }, + { + "path": "/var/www/html/sites/haxtheweb/files//Roadmap.jpg", + "fullUrl": "/sites/haxtheweb/files/Roadmap.jpg", + "url": "files/Roadmap.jpg", + "type": "image/jpeg", + "name": "Roadmap.jpg", + "size": 108725 + }, + { + "path": "/var/www/html/sites/haxtheweb/files/headshot272229.61999999825.jpg", + "fullUrl": "/sites/haxtheweb/files/headshot272229.61999999825.jpg", + "url": "files/headshot272229.61999999825.jpg", + "type": "image/jpeg", + "name": "headshot272229.61999999825.jpg", + "size": 121898 + } + ], + "readtime": 1, + "contentDetails": { + "headings": 2, + "paragraphs": 6, + "schema": [], + "tags": { + "h3": 2, + "p": 6, + "img": 2 + }, + "elements": 10 + } + } + }, + { + "id": "item-5df45272-f6b9-4f4f-b650-16c47aeac6fb", + "indent": "2", + "location": "pages/documentation-1/haxcms/publishing/index.html", + "slug": "documentation-1/haxcms/publishing", + "order": "3", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Publishing", + "description": "HAXcms requires being published in order to be visible to other people. Working locally or on Desktop or on a server, is akin to you writing a document on your computer. It's not shared with anyone. W", + "metadata": { + "created": 1550643005, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/gitpublishingdata.jpg", + "fullUrl": "/_sites/haxtheweb/files/gitpublishingdata.jpg", + "url": "files/gitpublishingdata.jpg", + "type": "image/jpeg", + "name": "gitpublishingdata.jpg", + "size": 12847 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/pubwork1.jpg", + "fullUrl": "/_sites/haxtheweb/files/pubwork1.jpg", + "url": "files/pubwork1.jpg", + "type": "image/jpeg", + "name": "pubwork1.jpg", + "size": 51662 + }, + { + "path": "/var/www/html/_sites/haxtheweb/files/pubwork2.jpg", + "fullUrl": "/_sites/haxtheweb/files/pubwork2.jpg", + "url": "files/pubwork2.jpg", + "type": "image/jpeg", + "name": "pubwork2.jpg", + "size": 70772 + } + ] + } + }, + { + "id": "item-44cc230b-07db-442a-90cf-687e2d089a5d", + "indent": "2", + "location": "pages/item-44cc230b-07db-442a-90cf-687e2d089a5d/index.html", + "slug": "haxhooks", + "order": "3", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "haxHooks", + "description": "Elements can integrate deeply into HAX state management using what we call \"hax hooks\". By supplying a method on your web component like haxHooks() you are magically able to tap into different li", + "metadata": { + "created": 1617802345, + "updated": 1617805490, + "readtime": 5, + "contentDetails": { + "headings": 10, + "paragraphs": 11, + "schema": [], + "tags": { + "p": 11, + "h2": 2, + "ul": 2, + "code-sample": 1, + "h3": 8 + }, + "elements": 24 + } + } + }, + { + "id": "item-c86470aa-0295-4c9d-9f17-48ad79ab05be", + "indent": "1", + "location": "pages/welcome/presentations/index.html", + "slug": "welcome/presentations", + "order": "4", + "parent": "item-welcome", + "title": "Presentations", + "description": "This is the youtube playlist of all things HAXTheWebThis playlist is updated on a regular basis so make sure to subscribe to the youtube channel for updates. There's also many other playlists relat", + "metadata": { + "created": 1552910817, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 2, + "schema": [], + "tags": { + "p": 2, + "iframe": 1 + }, + "elements": 3 + } + } + }, + { + "id": "item-4824986b-1897-568d-fdd9-4b882ea6ee1f", + "indent": "1", + "location": "pages/integrations-1/backdropcms/index.html", + "slug": "integrations-1/backdropcms", + "order": "4", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "BackdropCMS", + "description": "Getting HAX setup in BackdropCMSSearch for HAX on BackdropCMS.org or from within your Backdrop siteFollow the instructions in the Web components module README for buildingDon't worry, HAX requ", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 1, + "paragraphs": 1, + "schema": [ + { + "resource": "#5b790bef-7d78-f85e-104d", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", - "indent": "2", - "location": "pages\/documentation-1\/hax-development\/hax-app-store\/index.html", - "slug": "documentation-1\/hax-development\/hax-app-store", - "order": "6", - "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", - "title": "HAX app store", - "description": "", - "metadata": { - "created": 1548826475, - "updated": 1617805490 + ], + "tags": { + "p": 1, + "h2": 1, + "ol": 1, + "media-image": 1 + }, + "elements": 4 + } + } + }, + { + "id": "item-7ab2e2fd-622f-4a0f-9967-599410c6cd43", + "indent": 0, + "location": "pages/scavenger-hunt-1/index.html", + "slug": "scavenger-hunt-1", + "order": "4", + "parent": null, + "title": "Scavenger Hunt", + "description": "Become part of our dynasty franchise **by wearing a cool jerseyWe're building the greatest roster of people ever to HAX the complacency of our industry. Take the HAX scavenger hunt at the next ev", + "metadata": { + "created": 1563970537, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 1, + "paragraphs": 2, + "schema": [ + { + "typeof": "oer:SupportingMaterial", + "resource": "#238ee75a-de4d-02a9-3755", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-897a9839-4ca3-a336-4795-afca7b6de0ee", - "indent": "1", - "location": "pages\/integrations-1\/gravcms\/index.html", - "slug": "integrations-1\/gravcms", - "order": "6", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "GravCMS", - "description": "There's two plugins needed to run HAX on GravCMS - The web components and HAX plugins.Web components plugin\u00a0- provides the build routine and installation instructionsHAX plugin\u00a0- editor capab", - "metadata": { - "created": 1548826475, - "updated": 1617805490, - "readtime": 1, - "contentDetails": { - "headings": 0, - "paragraphs": 2, - "schema": [ - { - "resource": "#f0356db6-f345-316d-1426", - "prefix": "oer:http:\/\/oerschema.org\/ schema:http:\/\/schema.org\/ dc:http:\/\/purl.org\/dc\/terms\/ foaf:http:\/\/xmlns.com\/foaf\/0.1\/ cc:http:\/\/creativecommons.org\/ns# bib:http:\/\/bib.schema.org " - } - ], - "tags": { - "p": 2, - "ul": 1, - "media-image": 1 - }, - "elements": 4 - } + ], + "tags": { + "h3": 1, + "p": 2, + "ul": 1, + "task-list": 1, + "meme-maker": 1 + }, + "elements": 6 + } + } + }, + { + "id": "item-7f3dd690-4c3f-4616-baa5-159b9a15809c", + "indent": "3", + "location": "pages/documentation-1/haxcms/theming/dev-workflows/index.html", + "slug": "documentation-1/haxcms/theming/dev-workflows", + "order": "4", + "parent": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "title": "Dev workflows", + "description": "Our development workflow is as follows (for themes)All custom theme work happens in your _config directoryMake my-theme.js, pull everything together, either in this directory or in a wcfactory cat", + "metadata": { + "created": 1553349518, + "updated": 1617805490 + } + }, + { + "id": "item-e6daa06e-dfd2-43a4-ade8-0c0ded24e0b4", + "indent": "2", + "location": "pages/documentation-1/haxcms/life-cycle/index.html", + "slug": "documentation-1/haxcms/life-cycle", + "order": "4", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Life cycle", + "description": "This is a general life cycle that happens when HAXcms \"boots up\". When web components are unpacking the contents of what to do it generally will work this way.page load, should it be no-js or a web c", + "metadata": { + "created": 1554496047, + "updated": 1617805490, + "readtime": 3, + "contentDetails": { + "headings": 3, + "paragraphs": 5, + "schema": [], + "tags": { + "p": 5, + "ul": 3, + "h2": 1, + "code-sample": 1, + "h3": 2 + }, + "elements": 12 + } + } + }, + { + "id": "item-4bce3546-4d53-4456-8eae-494c79180229", + "indent": "1", + "location": "pages/documentation-1/haxcms/index.html", + "slug": "documentation-1/haxcms", + "order": "4", + "parent": "item-db25d465-f8ee-6d9b-a738-f9e94305d89d", + "title": "HAXcms", + "description": "HAXcms, that which powers the site you are currently reading is a powerful \"static site generator\" paradigm. It leverages server technology in order to orchestrate a static site. That way the \"server\"", + "metadata": { + "created": 1550643005, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/HAXCms workflow.jpg", + "fullUrl": "/_sites/haxtheweb/files/HAXCms workflow.jpg", + "url": "files/HAXCms workflow.jpg", + "type": "image/jpeg", + "name": "HAXCms workflow.jpg", + "size": 72736 + } + ] + } + }, + { + "id": "item-cdd303d0-4490-4433-94fa-0e78cf849e80", + "indent": "2", + "location": "pages/item-cdd303d0-4490-4433-94fa-0e78cf849e80/index.html", + "slug": "documentation-1/hax-development/internationalization-i18n", + "order": "4", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "Internationalization - i18n", + "description": "We've created a way to internationalize ANY web component you create. Because this is a complex topic, and we seek to empower anyone, anywhere to work with web components; i18n is a critical piece of ", + "metadata": { + "created": 1617805490, + "updated": 1617806250, + "readtime": 2, + "contentDetails": { + "headings": 1, + "paragraphs": 3, + "schema": [], + "tags": { + "p": 3, + "a": 1, + "h3": 1, + "ul": 1, + "code-sample": 2 + }, + "elements": 8 + } + } + }, + { + "id": "item-52727dcf-a7d5-90e9-c459-a4a53dd07ffd", + "indent": "2", + "location": "pages/documentation-1/hax-development/hax-element-schema/index.html", + "slug": "documentation-1/hax-development/hax-element-schema", + "order": "5", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "HAX Element Schema", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-5dede24a-2de7-4fae-a00b-31e8121e3c16", + "indent": "1", + "location": "pages/welcome/i-have-issues/index.html", + "slug": "welcome/i-have-issues", + "order": "5", + "parent": "item-welcome", + "title": "I have issues", + "description": "You have a problem or would like to contribute to anything in our universe? That's awesome! All issues, feature requests and general thumbs up should happen in our issue queue on github: https://gith", + "metadata": { + "created": 1553556295, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 1, + "schema": [ + { + "resource": "#b54c9847-4d26-90ae-d748", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", - "indent": "2", - "location": "pages\/documentation-1\/haxcms\/theming\/index.html", - "slug": "documentation-1\/haxcms\/theming", - "order": "6", - "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", - "title": "Theming", - "description": "There are multiple ways to \"theme\" in HAXcms that align with the skillsets of the person doing the theme development. Know web components? Cool. Know basic CSS and HTML? Cool. Want to build something ", - "metadata": { - "created": 1550643005, - "updated": 1617805490 + ], + "tags": { + "p": 1, + "a11y-gif-player": 1 + }, + "elements": 2 + } + } + }, + { + "id": "item-677468f6-7bff-4bb6-bd2a-18520d88b3c4", + "indent": "1", + "location": "pages/integrations-1/classicpress-1/index.html", + "slug": "integrations-1/classicpress-1", + "order": "5", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "ClassicPress", + "description": "ClassicPress is a popular fork of WordPress that's even easier to get HAX up and running then it is in the original!Get the HAX plugin from the wordpress registryGo to edit / create a page/post ", + "metadata": { + "created": 1565279009, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 1, + "paragraphs": 2, + "schema": [ + { + "resource": "#85219ed3-d806-24d7-5c02", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } - }, - { - "id": "item-c5e61b84-e88a-5a48-29c6-5908117ec505", - "indent": "1", - "location": "pages\/integrations-1\/creating-new-ones\/index.html", - "slug": "integrations-1\/creating-new-ones", - "order": "7", - "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", - "title": "Creating new ones!", - "description": "The main piece to our integrations is wrapped up in something we call \"The magic script\". The magic script is a standard way of dynamically discovering and importing the definitions of web components ", - "metadata": { - "created": 1548828434, - "updated": 1617805490, - "files": [ - { - "path": "\/var\/www\/html\/_sites\/haxtheweb\/files\/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", - "fullUrl": "\/_sites\/haxtheweb\/files\/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", - "url": "files\/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", - "type": "image\/jpeg", - "name": "59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", - "size": 51809 - } - ], - "readtime": 3, - "contentDetails": { - "headings": 3, - "paragraphs": 8, - "schema": [], - "tags": { - "p": 8, - "code-sample": 2, - "full-width-image": 1, - "h2": 3, - "ol": 1 - }, - "elements": 15 - } + ], + "tags": { + "p": 2, + "ol": 1, + "h2": 1, + "video-player": 1 + }, + "elements": 5 + } + } + }, + { + "id": "item-c7500902-9aed-4117-8949-a6597a02dada", + "indent": "2", + "location": "pages/documentation-1/haxcms/troubleshooting/index.html", + "slug": "documentation-1/haxcms/troubleshooting", + "order": "5", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Troubleshooting", + "description": "These are some common issues / resolutions in HAXcms related to installation, publishing, etc.I installed HAXcms and forgot my passwordYour username and password can be found in _config/config.php o", + "metadata": { + "created": 1553555764, + "updated": 1617805490 + } + }, + { + "id": "item-4de60a5f-98ab-a602-edfc-0cf024e83755", + "indent": "2", + "location": "pages/documentation-1/hax-development/hax-app-store/index.html", + "slug": "documentation-1/hax-development/hax-app-store", + "order": "6", + "parent": "item-534ed4c7-2468-366f-5410-adc169efcebc", + "title": "HAX app store", + "description": "", + "metadata": { + "created": 1548826475, + "updated": 1617805490 + } + }, + { + "id": "item-897a9839-4ca3-a336-4795-afca7b6de0ee", + "indent": "1", + "location": "pages/integrations-1/gravcms/index.html", + "slug": "integrations-1/gravcms", + "order": "6", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "GravCMS", + "description": "There's two plugins needed to run HAX on GravCMS - The web components and HAX plugins.Web components plugin - provides the build routine and installation instructionsHAX plugin - editor capab", + "metadata": { + "created": 1548826475, + "updated": 1617805490, + "readtime": 1, + "contentDetails": { + "headings": 0, + "paragraphs": 2, + "schema": [ + { + "resource": "#f0356db6-f345-316d-1426", + "prefix": "oer:http://oerschema.org/ schema:http://schema.org/ dc:http://purl.org/dc/terms/ foaf:http://xmlns.com/foaf/0.1/ cc:http://creativecommons.org/ns# bib:http://bib.schema.org " } + ], + "tags": { + "p": 2, + "ul": 1, + "media-image": 1 + }, + "elements": 4 + } + } + }, + { + "id": "item-a52fb685-0a2f-4bc0-8e62-457cf01d66ed", + "indent": "2", + "location": "pages/documentation-1/haxcms/theming/index.html", + "slug": "documentation-1/haxcms/theming", + "order": "6", + "parent": "item-4bce3546-4d53-4456-8eae-494c79180229", + "title": "Theming", + "description": "There are multiple ways to \"theme\" in HAXcms that align with the skillsets of the person doing the theme development. Know web components? Cool. Know basic CSS and HTML? Cool. Want to build something ", + "metadata": { + "created": 1550643005, + "updated": 1617805490 + } + }, + { + "id": "item-c5e61b84-e88a-5a48-29c6-5908117ec505", + "indent": "1", + "location": "pages/integrations-1/creating-new-ones/index.html", + "slug": "integrations-1/creating-new-ones", + "order": "7", + "parent": "item-ac67dab5-8208-65e3-c3e4-267b1bf6079f", + "title": "Creating new ones!", + "description": "The main piece to our integrations is wrapped up in something we call \"The magic script\". The magic script is a standard way of dynamically discovering and importing the definitions of web components ", + "metadata": { + "created": 1548828434, + "updated": 1617805490, + "files": [ + { + "path": "/var/www/html/_sites/haxtheweb/files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", + "fullUrl": "/_sites/haxtheweb/files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", + "url": "files/59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", + "type": "image/jpeg", + "name": "59453a821222752c90fa970c937c2c396bff61f5-ngdle-university-faculty-side.jpg", + "size": 51809 + } + ], + "readtime": 3, + "contentDetails": { + "headings": 3, + "paragraphs": 8, + "schema": [], + "tags": { + "p": 8, + "code-sample": 2, + "full-width-image": 1, + "h2": 3, + "ol": 1 + }, + "elements": 15 } - ] + } + } + ] } \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml index f6411fa..7c8b17b 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1,7 +1,7 @@ - +- +hax-the-web - https://haxtheweb.org//rss.xml -Project home and documentation for all things HAX -Copyright (C) 2021 https://haxtheweb.org/ -en-us -Wed, 07 Apr 2021 14:24:50 +0000 -https://haxtheweb.org/https://haxtheweb.org//documentation-1/hax-development @@ -35,7 +35,7 @@https://haxtheweb.org/https://haxtheweb.org//welcome -2021-04-07T14:24:50+00:00 +2022-08-25T18:26:55+00:00 daily 1.0 https://haxtheweb.org/https://haxtheweb.org//documentation-1 -2021-04-07T14:24:50+00:00 +2022-08-25T18:27:18+00:00 daily 1.0 https://haxtheweb.org/https://haxtheweb.org//f-a-q-1 -2021-04-07T14:43:59+00:00 +2022-08-25T18:39:36+00:00 daily 1.0