H2S3: How to add pages and posts in WordPress:

H3S1: Gutenberg code editor:

As with the Site Editor, it is important to understand #, while using Gutenberg, that all changes, even if WYSIWYG<r: WP.MIC-H2S2>, are reflected in code. This is why I recommend, for all students, that they toggle to the code editor by clicking the vertical “…” icon, at the top | right of any Gutenberg page, and toggle to the code | editor mode [D]:

Both the visual editor and code editor work on the same fundamental | meaning.

Also | useful, in this same menu, is locking the top toolbar, as the pop | up version is 1) unstable, 2) counter-intuitive.

H3S2: Block directory:

H4S1: Row:

A row | block can be added, within a container block, adjacent to another sub–item, to become # an associated, always under, but can be toggled to always | above, relative to that other sub–item, and the row, itself, can contain further sub–blocks, as well, as elements, directly.

H5S1: Design: H6S1: Layout: H7S1: Justification: this option will justify components of the row-container, which can be a large | variety of blocks, as components # to the left, mid, or right, of the row block’s borders. H6S2: Color: changes the background, of the row, behind all of its components H6S3: Dimensions: H7S1: There are 4 paddings that can be added, corresponding to the 4 primary compass directions, and the padding can be by px, em, or %, which is dynamically | calculated<Turing-CSS>H7S2: Block spacing: increases the horizontal space, evenly, among all of the row components, between each other.

H4S2: Navigation:

The navigation | block allows you # to load pre-made | menus into the header, or any other part of the site, as well as to extend an existing | menu, replacing the customization functionality of pre.Site-Editor, and create a new | menu, and manage your stable of existing | menus. The navigation block functionality, in conjunction with template parts, and the Site Editors<WP.MIC-H2S2>, permits site owners infinite | flexibility, when it comes to installing different | menus on different | pages of the website. Case | study: H5S1: This rubix–cubing<r: IM John Bartholomew> of the WordPress core dispels the need of an additional plugin, conditional menus.

H4S3: Classic editor:

[D]: The classic | editor inserts a paragraph block that allows a few | more standard text editor | features, which allows you # to make a portion of text, in which you’d like more detailed, Word-type edits, look nice.

H4S4: Table: r: ch-62:

MIC SWOT template:	Helpful:	Harmful:
Internal:	S: 1) Our B contends the e-pp’s adv-sq 2) The two diags occupied by d7 have ≥ 4-sqs <a4->e8, 5> <c8->h3, 6>, meeting M/L’s rule. 3) Our K is unchecked.	W: 1) Our K is 6.4 DU from the e-pp. 2) Our only chance to stop the e6-pp is via d7-blockade; d8 is a dark-sq.
External:	O: 1) If we capture the pp, we draw, even at cost of B <-2> # 2) We cannot win, so our opp-ceiling is limited.	T: 1) The e-N and e-K will coordinate to threat-move our B from contention of d7. 2) If f promotes, we lose.

Hu: A table with 3 columns and 3 rows, and 2×2 content matrix #

H4S5: Container blocks:

Hu: See an example of our implementation # on the contact-page: the Google Form came in # via HTML hard-code left-aligned, with no ability to adjust, but we were able to # center it, by first creating a column block, as a container, and inserting the HTML block, into that column block, which is set to centered, on the page–level.

H4S6: Function | block:

Hu: A futuristic idea, not in WordPress yet, but would allow users to write custom | functions, in a backend programming language, such as a a) calculator, b) a manual time-looped image gif, c) a conditional–triggered form display, d) a random | number | generator that flashes 10 numbers per second, until the user clicks stop, using a while loop<a-r>

H4S7: User command-line | block:

Hu: another futuristic | idea, a command–line | block, which takes user inputs, and is linked to a function block, and returns the output of calculations.

H4S8: Replit oEmbed in WordPress:

Hu: Replit is a powerful, cloud–based, backend | programming IDE, with instantaneous | rendering, and web connectivity, that can be used, to write a variety of functions, and be embedded as a block #n-p, using the embed block. Fin.v-1 // research the exact embed code

H4S9: The nav-menu block:

Hu: The navigation | menu block contains an additional | component of logic, in that it can be programmed, and the name of a specific | menu, saved, and propagated, across multiple pages, templates, or template parts<site-edior>, and when a particular menu # is changed, all instances # of that menu, will be changed, synchronously:

H5S1: Aesthetic | settings:

Hu: Each type of block in WP has its own hard-coded aesthetic settings<malpractice>, and it’s anyone’s guess, which set, the random Automattic employee assigned to work on that block, who doesn’t talk to the other block engineers, decided he has the time to hard.code-in # However, some leeway can be provided, to q.tum-aware developers who can feel out the latent | settings; basically, you are pulling | sliders to write CSS-code<malpractice>

H6S1: Layout H7S1: Justification: aligns the menu within the navigation block either left-aligned, with the left border of the nav-block<good>, centrally, or with the right border. If the nav-block is itself nested within a row<H4S1>, changing the justification in the nav.block-setting<malpractice>has no effect on the positioning of the entire block.

H6S2: Menu: Intimately–tied<good>and hard–coded<malpractice>into the nav-block is Menus, which is a big, and old feature that has been buried in a shadow-URL only accessible by clicking Manage menus here #wp-admin/edit.php?post_type=wp_navigation #dash-opportunity<WP.MIC-H2S13>; one | menu<malpractice>can be selected non-redundantly<Turing>from this list; in order to rename a menu, one has to click through to Manage menus<malpractice>.

H6S3: Display: Relatively sparse, and bearing in mind, what follows, also falls into the category of “display”; you can use these options to select whether an icon, or the full menu, is displayed, when the screen width is too small to display all the items, in the absolute font size<responsive-barely><malpractice-0, est>, where Off corresponds to that full menu, Mobile, for mobile only<est>, and always, never showing the full menu, until that = icon is clicked<malpractice>

H6S4: Color: The text and background color can be set, applying only to the nav-block.

H6S5: Dimensions: an extension of Display, the Dimensions label tends to be the most primitive, and poorly developed, even among all of WordPress<v-t>’s functionality, not just in design. Here, extending the BLOCK SPACING slider increases horizontal spacing for every margin between elements in the menu, and other elements in the nav-block, such as a site | icon; the spacing is graded, only, and there is an unspecified | default value, hard-coded, that is overwritten, permanus, when the slider is touched<malpractice>

H4S10: Image block:

Hu:

The % grid will reset the width and height dimensions of the image, back to modular | quanta<r: MIC-clarinet>, and these values can exceed the width of the content | area; on desktop, this exceeding will cause a cool, out.bleed-E, while on mobile, the image will be automatically | downsized, to fit within screen | limitations<responsive-#defd> # The percentage, is calculated, in terms of proportion, to the content | area, entire, not just its column.

H4S11: Paragraph block:

Hu<life.hack-meme>: WordPress will sporadically convert HMTL into a rendered | version, when you # copy paste into Gutenberg, but using right click + force paste, should cause the HTML to be copied in, as the code, for display, in coding | tutorials<WP.MIC-H2S10> H5S1: Code block: The code block, in lieu of the paragraph | block, can display code snippets, with WP-dev<a-r>: formatted code for others to view.

H3S3: Posts x Site Editor, templates:

Hu: a concrete | merger exists between posts, and pages, and templates, in the post sidebar, in which a template can be selected for each | post, adopting the properties that were created with the Site Editor: [D]: a sidebar | menu item found in /wp-admin/post.php?post=[post-number]&action=edit

H3S4: 5 levels of copy-paste:

H4S1: PSD to HTML: // research

H4S2: Component recreation: // research

H4S3: Staged theme, import, and copy: // research

H4S4: Copy patterns: // research

H5S1: Cross domain copy-paste: Hu: Surprisingly, copy paste works with moderate fidelity across domain; if what is copied is a composite and has a component that is locked to the previous domain, then that component, only, will not render, and an error message will be displayed<Turing>

H5S2: Intra-domain copy-paste: Hu: Generally, blocks, patterns, headings, and larger sections, that have the vertical 3 dot menu<12/22>can be copied, and pasted, into posts, pages, templates, and template parts, from any page, or post, to any other, within a domain<anthro><inductive>.

H5S3: Front.end-copy,paste: Hu: Accessing an article from the visitor’s–view<Tur>can also be copy-pasted, and with block formatting preserved, when the paste–dest<Tur>is a Guten.back–end.

H4S5: Theme installation: // research

// send to mayor Deb when done

H3S5: Page editing:

H4S1: Page editing x access management x users:

Hu: This is a specific workflow, x-ref <WP.MIC-H2S5> that will show you how to create a page, that is restricted, to a specific | user, using AAM plugin x WordPress core. First, you must have purchased # a website build from me, with H3S1 , H3S5, and H3S2, from my services page. With H3S1, I will have set up a menu-client, header-client, and dash-client in your Site Editor templates section. H5S1: Page creation and template selection: create a new page, and title it dash.[name-of-client], select dash-client as the page template. This will load the correct | header, for logged-in users, to the page. H6S1: Duplication: alternatively, duplicate the dash.john-client template page. H5S2: Access management: ⭐ In the AAM menu bar beneath the page editor, restrict access for all content-tiers, under roles; then, switch to users, and override the restriction<Turing-shared>, only for this client, and any other accounts, with this client. H6S1: Note that you will have to repeat this process, for every post, or page, or media item, that you upload, that is also, only for this client, such as legal documents and invoices.

H3S6: Post list:

Hu: To change the order of posts, on any list, that generates, by default, a reverse-chron, of all posts, that are not private or pass-protected, on your site, you must change the date that is assigned to the post, since posts are ordered, by time. To do this, return to the edit page of the post #, and in the Status & visibility sub-menu, of the Post menu, click “Immediately”, next to Publish, and change the publishing date: [D]:

Definitions:

Create (v.) = to cause to exist; bring into being: synonym: establish<Am-Heri> Creative (adj.) = characterized by originality and expressiveness; imaginative.