Minor changes to filenames

blocks/lcp-viewport/.editorconfig

@@ -0,0 +1,18 @@
+# This file is for unifying the coding style for different editors and IDEs
+# editorconfig.org
+
+# WordPress Coding Standards
+# https://make.wordpress.org/core/handbook/coding-standards/
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = tab
+
+[*.{yml,yaml}]
+indent_style = space
+indent_size = 2

blocks/lcp-viewport/.gitignore

@@ -0,0 +1,30 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Output of `npm pack`
+*.tgz
+
+# Output of `wp-scripts plugin-zip`
+*.zip
+
+# dotenv environment variables file
+.env

blocks/lcp-viewport/lcp-viewport.php

@@ -0,0 +1,30 @@
+<?php
+/**
+ * Plugin Name:       Lcp Viewport
+ * Description:       Example block scaffolded with Create Block tool.
+ * Requires at least: 6.6
+ * Requires PHP:      7.2
+ * Version:           0.1.0
+ * Author:            The WordPress Contributors
+ * License:           GPL-2.0-or-later
+ * License URI:       https://www.gnu.org/licenses/gpl-2.0.html
+ * Text Domain:       lcp-viewport
+ *
+ * @package CreateBlock
+ */
+
+if ( ! defined( 'ABSPATH' ) ) {
+	exit; // Exit if accessed directly.
+}
+
+/**
+ * Registers the block using the metadata loaded from the `block.json` file.
+ * Behind the scenes, it registers also all assets so they can be enqueued
+ * through the block editor in the corresponding context.
+ *
+ * @see https://developer.wordpress.org/reference/functions/register_block_type/
+ */
+function create_block_lcp_viewport_block_init() {
+	register_block_type( __DIR__ . '/build' );
+}
+add_action( 'init', 'create_block_lcp_viewport_block_init' );

blocks/lcp-viewport/package.json

@@ -0,0 +1,20 @@
+{
+	"name": "lcp-viewport",
+	"version": "0.1.0",
+	"description": "Example block scaffolded with Create Block tool.",
+	"author": "The WordPress Contributors",
+	"license": "GPL-2.0-or-later",
+	"main": "build/index.js",
+	"scripts": {
+		"build": "wp-scripts build",
+		"format": "wp-scripts format",
+		"lint:css": "wp-scripts lint-style",
+		"lint:js": "wp-scripts lint-js",
+		"packages-update": "wp-scripts packages-update",
+		"plugin-zip": "wp-scripts plugin-zip",
+		"start": "wp-scripts start"
+	},
+	"devDependencies": {
+		"@wordpress/scripts": "^30.4.0"
+	}
+}

blocks/lcp-viewport/readme.txt

@@ -0,0 +1,55 @@
+=== Lcp Viewport ===
+Contributors:      The WordPress Contributors
+Tags:              block
+Tested up to:      6.6
+Stable tag:        0.1.0
+License:           GPL-2.0-or-later
+License URI:       https://www.gnu.org/licenses/gpl-2.0.html
+
+Example block scaffolded with Create Block tool.
+
+== Description ==
+
+This is the long description. No limit, and you can use Markdown (as well as in the following sections).
+
+For backwards compatibility, if this section is missing, the full length of the short description will be used, and
+Markdown parsed.
+
+== Installation ==
+
+This section describes how to install the plugin and get it working.
+
+e.g.
+
+1. Upload the plugin files to the `/wp-content/plugins/lcp-viewport` directory, or install the plugin through the WordPress plugins screen directly.
+1. Activate the plugin through the 'Plugins' screen in WordPress
+
+
+== Frequently Asked Questions ==
+
+= A question that someone might have =
+
+An answer to that question.
+
+= What about foo bar? =
+
+Answer to foo bar dilemma.
+
+== Screenshots ==
+
+1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
+the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
+directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
+(or jpg, jpeg, gif).
+2. This is the second screen shot
+
+== Changelog ==
+
+= 0.1.0 =
+* Release
+
+== Arbitrary section ==
+
+You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
+plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
+"installation." Arbitrary sections will be shown below the built-in sections outlined above.

blocks/lcp-viewport/src/block.json

@@ -0,0 +1,29 @@
+{
+	"$schema": "https://schemas.wp.org/trunk/block.json",
+	"apiVersion": 3,
+	"name": "lcp/viewport",
+	"version": "0.1.0",
+	"title": "Viewport",
+	"category": "widgets",
+	"icon": "smiley",
+	"description": "Viewport container which is designed to be the parent of all other blocks",
+	"example": {},
+	"supports": {
+		"color": {
+            "background": true,
+            "text": false,
+            "link": false
+        }
+	  },
+	"attributes" :{
+		"hasSidecontent":{
+			"type":"boolean",
+			"default":true
+		}
+	},
+	"textdomain": "lcp-viewport",
+	"editorScript": "file:./index.js",
+	"editorStyle": "file:./index.css",
+	"style": "file:./style-index.css",
+	"viewScript": "file:./view.js"
+}

blocks/lcp-viewport/src/edit.js

@@ -0,0 +1,45 @@
+import { __ } from '@wordpress/i18n';
+import { useBlockProps, InnerBlocks, InspectorControls } from '@wordpress/block-editor';
+import { ToggleControl } from '@wordpress/components';
+import './editor.scss';
+
+export default function Edit({ attributes, setAttributes }) {
+    const { hasSidecontent } = attributes;
+
+    // Block props
+    const blockProps = useBlockProps();
+
+    // Custom template logic based on hasSidecontent
+    const template = [
+        hasSidecontent && ['lcp/sidecontent'], // Only include lcp/sidecontent if the toggle is true
+        ['lcp/main-area'], // Always include lcp/main-area
+    ].filter(Boolean); // Filter out falsey values (e.g., undefined when hasSidecontent is false)
+
+    // Render appender logic to handle block insertion
+    const renderAppender = () => {
+        return <InnerBlocks.ButtonBlockAppender />;
+    };
+
+    return (
+        <div {...blockProps}>
+            {/* Inspector Controls: Add a toggle for the `hasSidecontent` attribute */}
+            <InspectorControls>
+                <ToggleControl
+                    label={__('Include Side Content', 'lcp-viewport')}
+                    checked={hasSidecontent}
+                    onChange={(value) => setAttributes({ hasSidecontent: value })}
+                />
+            </InspectorControls>
+
+            <p>
+                {__('Lcp Viewport – hello from the editor!', 'lcp-viewport')}
+            </p>
+
+            {/* Render the InnerBlocks with conditional template */}
+            <InnerBlocks
+                template={template} // Use the template logic here
+                renderAppender={renderAppender} // Custom appender logic
+            />
+        </div>
+    );
+}

blocks/lcp-viewport/src/editor.scss

@@ -0,0 +1,9 @@
+/**
+ * The following styles get applied inside the editor only.
+ *
+ * Replace them with your own styles or remove the file completely.
+ */
+
+.wp-block-create-block-lcp-viewport {
+	border: 1px dotted #f00;
+}

blocks/lcp-viewport/src/index.js

@@ -0,0 +1,39 @@
+/**
+ * Registers a new block provided a unique name and an object defining its behavior.
+ *
+ * @see https://developer.wordpress.org/block-editor/reference-guides/block-api/block-registration/
+ */
+import { registerBlockType } from '@wordpress/blocks';
+
+/**
+ * Lets webpack process CSS, SASS or SCSS files referenced in JavaScript files.
+ * All files containing `style` keyword are bundled together. The code used
+ * gets applied both to the front of your site and to the editor.
+ *
+ * @see https://www.npmjs.com/package/@wordpress/scripts#using-css
+ */
+import './style.scss';
+
+/**
+ * Internal dependencies
+ */
+import Edit from './edit';
+import save from './save';
+import metadata from './block.json';
+
+/**
+ * Every block starts by registering a new block type definition.
+ *
+ * @see https://developer.wordpress.org/block-editor/reference-guides/block-api/block-registration/
+ */
+registerBlockType( metadata.name, {
+	/**
+	 * @see ./edit.js
+	 */
+	edit: Edit,
+
+	/**
+	 * @see ./save.js
+	 */
+	save,
+} );

blocks/lcp-viewport/src/save.js

@@ -0,0 +1,26 @@
+import { useBlockProps, InnerBlocks } from '@wordpress/block-editor';
+
+/**
+ * The save function defines the way in which the different attributes should
+ * be combined into the final markup, which is then serialized by the block
+ * editor into `post_content`.
+ *
+ * @see https://developer.wordpress.org/block-editor/reference-guides/block-api/block-edit-save/#save
+ *
+ * @return {Element} Element to render.
+ */
+export default function Save({ attributes }) {
+    const { hasSidecontent } = attributes; // Retrieve the hasSidecontent attribute
+    const blockProps = useBlockProps.save();
+
+    // Conditionally add the .lcp-has-sidecontent class if hasSidecontent is true
+    const hasSidecontentClass = hasSidecontent ? 'class="lcp-has-sidecontent"' : null;
+
+    return (
+        <div {...blockProps} id="lcp-viewport-outer" >
+            <div hasSidecontentClass id="lcp-viewport-inner">
+            <InnerBlocks.Content />
+            </div>
+        </div>
+    );
+}

blocks/lcp-viewport/src/style.scss

@@ -0,0 +1,7 @@
+/**
+ * The following styles get applied both on the front of your site
+ * and in the editor.
+ *
+ * Replace them with your own styles or remove the file completely.
+ */
+

blocks/lcp-viewport/src/view.js

@@ -0,0 +1,25 @@
+/**
+ * Use this file for JavaScript code that you want to run in the front-end
+ * on posts/pages that contain this block.
+ *
+ * When this file is defined as the value of the `viewScript` property
+ * in `block.json` it will be enqueued on the front end of the site.
+ *
+ * Example:
+ *
+ * ```js
+ * {
+ *   "viewScript": "file:./view.js"
+ * }
+ * ```
+ *
+ * If you're not making any changes to this file because your project doesn't need any
+ * JavaScript running in the front-end, then you should delete this file and remove
+ * the `viewScript` property from `block.json`.
+ *
+ * @see https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/#view-script
+ */
+
+/* eslint-disable no-console */
+console.log( 'Hello World! (from create-block-lcp-viewport block)' );
+/* eslint-enable no-console */