joer80

Members
  • Content Count

    292
  • Joined

  • Last visited

Community Reputation

128 Excellent

About joer80

  • Rank
    Sr. Member

Contact Methods

  • Website URL
    http://www.webprojoe.com

Profile Information

  • Gender
    Male
  • Location
    Texarkana, TX

Recent Profile Visitors

3,229 profile views
  1. joer80

    How would you nest more than one deep? For example, with my approach, I can insert a section, then a grid, then a cell, and then put an accordion into one cell, and then put another grid into that accordion. So I can do text in the left part of an accordion and an image in the right. Here is another screencast. Also shows I got rid of the content layer. I don't find it necessary. This is a one pager I did for our imaging clinic. It had an accordion example. https://www.hceimaging.com/
  2. joer80

    I love this idea! I would use it.
  3. I had the need to do something similar before. We wanted to know how far users got into a multi-step order process, and also what values they were putting in during each step and the referring pages. I found inserting a record on every page load worked well and was fast. Don't increment anything or it is slow, just insert new records and use a weekly or monthly cron to process the data to keep the table size manageable. Add in an optimize command also to clear db overhead after rows are deleted. I insert the session_id, timestamp, ip address, etc, but none of the data is public. Used for troubleshooting.
  4. joer80

    Give me a hypothetical situation and I can see if the page layout group method would be enough. By assigning a page layout to each page to form groups of pages. A page can have its own items and the items attached to its page group at the same time. As an additional layer, you can use hanna codes to share code between page groups even.
  5. joer80

    My next step is to see how hard it will be to make a module that will allow me to keep them all up to date as I make changes and add templates. I will have 5 installs within a week!
  6. joer80

    I just noticed that feature earlier today and enabled it! Whats cool also is I can insert a grid inside my accordion so I can do columns inside my accordions! Just tested it out.
  7. joer80

    I have decided to clean this up a bit. It seems adding a content page under a page just to separate it from the detail pages is not optimal or necessary. I have decided on another way to flag what the child items are. I now use the "Page" template for pages that have content rows as children, and every other page type that can be added under Admin Home is made to have detail pages as children. ie. Services, Products, Basic Pages, etc. I show this with the page template using the globe, and the other master types using a dark circle. I also added a "Basic Pages" master/detail set that allowed me to trim up my root page list and move things like Terms and conditions and Privacy Policy under there as detail pages. This also keeps me from building a section just to add a text item to it. I just add new and type content. The basic page template has the inner page heading, and a section and text row built in so it saves time adding these info pages. So you can add a "Page", and still build it out, and also select a page layout of "Inner Page" to give you the automatic page heading, or blank gives you a clean slate, or you can work with an existing page type like "Basic Page" or "Service", or add a new template with custom fields and work with the same master and detail format. Just tell it to use page.php as the template, give it some fields, and make sure it selects a page layout.
  8. joer80

    Here is how the map row looks. Its a regular grid item with the collapse gutter option set and the first child cell set to 1/3 on large screens. I could do the map side as a map.php template though instead of a php snippet even though its just 5-10 lines of code. I did a contact_form.php for the basic form I used on the contact page. It's easy to use checkboxes to know what fields to make with you add it to the page. Address, phone and such is still pulled from hanna codes so if you don't want fax you just leave it blank. My goal is to be able to import the whole row from an external library of some sort and not have to build them.
  9. joer80

    I think I am going to add a lazy cron style auto update module for important security updates, and maybe hit a manual update when you are backed up for feature ones. I can launch this as version 1.0 and check an endpoint for the most recent version from time to time to let the user know if there is an update with new features. If I add a new drop-down/option list to the section.php template in 1.01, it would make the database changes and replace the section.php file to read them. Ryan is also doing a great job with page import and export, so you could go to a website and export the home page and all of its children, and import it into a new website. You can already drag a row from one page to another and carry all of the children items with it. Since the code snippet template has fields for its own css, js, images, php code and html code, you should be about to export whole features by importing one page into your sitewide folder or a page layout folder that target your head, bottom, and page at the same time. I probably need to put a row gallery up somewhere also so I can upload row designs and not just mark them as inactive. Keep the websites clean but browse for ideas and pull them in. Just have to standardize things like the hanna tags so the address info and such comes in right for a map row.
  10. joer80

    Oh cool! Are you a full-time programmer? On the detail page layouts, I didn't want to be required to select a page layout every time I add a child page so I made that drop down. (For blog posts and services and products, etc.) . So if I set a detail page layout on a page, any children will use that even if they do not set one. My page.php template says "if the current page I am showing doesn't have a page layout selected, check its parent to see if there is a detail page layout I can use". So if I add a blog post (blog_post.php), or a new service page, those do not even have to have a drop down for selecting the page layout as part of their template fields. I can also set the blog template only to allow blog post children, so it saves the whole step of selecting a page template or layout at all. If I want, I can allow content children also, but its not really necessary since you can add items to the page layout. blog and blog_post or services and service would still use the page.php template though. They are just templates to get the unique fields. After I clean it up some, I will see about making a site profile.
  11. joer80

    I ended up using mono snap. Worked well! It added an icon to my top bar on my mac and I can do a new recording and start and pause, and it gives me the option to add a small screen to the bottom for my web cam. I can also do full screen or draw a box to just do part of the screen.
  12. joer80

    It is a little messy since I have not set the template families perfectly yet, and normalized the template name case, but this should give you an idea of how it flows so far. I add a banner slide to the homepage, add a new basic page, and add a few sections to that basic page. The basic page layout is what adds the inner page title row. That's the only item I have added to that since the nav is marked sitewide. I then add the test content to the page itself under a content item which allows the uikit items. I could have added it to the page layout, but it would have gone to everything marked as a basic page.
  13. joer80

    The nav_link template and the button template has options for selecting a page so the link never breaks, a page section, which is just a child row of a page which is typically a section, or a url for external links. I also built in code that adds smooth scrolling if you did a section link and you happen to be on the same page already, for one page websites. I made this website today as an example that shows that part and an alternate header look. I also made the external url field used on the button template support hanna codes, so I can use things like [[directions]] or tel:[[phone]] for the button link value. The map row is just a uikit grid with the collapse option set in the gutter drop down. https://www.hcederm.com/
  14. joer80

    Sure. I will try to do a screen recording of building a page with a few rows attached. Do you know of a free web based one I can use? With the concept of having a page that either has detail pages as children or design rows as children, I didn't want to have pages under pages. The Navigation page holds all of my navbar container rows, which select the html tag body->header and dump inside that. The children of navbar container can be a nav_logo, nav_bar, or nav_item. (For buttons) . They have alignment and visibility options. Nav_bar can have nav_links or nav_grid children for mega menus, or you can fill out the selector text box to add a group of pages that is always accurate.
  15. joer80

    The role of my page.php page is to do this: Get the themes page and set it as a variable for later use. (Anything can access this page to get the asset timestamp, active theme, etc.) Set a variable for the selected page layout of the current page, so I know what uikit elements we are adding from that. If there is not one on the current page, check the parent for a detail page layout. Get a list of code snippets that target html tags for this page, sorted by priority. (If they match the page layout, the page, or are sitewide, implement them by adding them to the snippet array.) By implement, if its a code snippet type, it outputs the html or php using output buffer and adds to the snippet array. If its not a code snippet, it is a uikit item and I will start the output buffer also and include the template file directly. (I also set a variable for that page to use inside the template before I include it. (The $page variable gets saved as the template name.) So if its a section template, I save the $page data as a $section variable. In my "section" template, I can access itself with $section, or the root page it is on with $page. Inside the section template I can loop through $section children also, setting the children as $cell so the cell.php page can access itself with $cell->x After the snippet array is built using code snippets and uikit page templates, I loop through the /html/ page and its children. I pass that page to a render function, and it loops through the html tags listed and puts the snippets where they belong, outputting the result to the page. This is a delayed outputting format that lets a snippet tweak other snippets if needed, since they are stored in an array before output, and any snippet can target various parts of the page. ie. The last snippet loaded can still add to the head section.