Skip to content

Commit

Permalink
Titles, git, and that's kinda it
Browse files Browse the repository at this point in the history
- Fixed up the titles on /end and /start
- Added a short how-to on git
  • Loading branch information
DynTylluan committed Nov 21, 2023
1 parent 6738603 commit 3de2e28
Show file tree
Hide file tree
Showing 9 changed files with 104 additions and 6 deletions.
12 changes: 8 additions & 4 deletions accessibility/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -394,11 +394,11 @@ <h3>Contents:</h3>
<p>There are, of course, other ways to write dates so as to not confuse people. 10/Dec/1993 is quick to understand, for example.</p>
<hr>

<a href="text-art"><h2>Displaying text art</h2></a><a name="text-art"></a>
<a href="#text-art"><h2>Displaying text art</h2></a><a name="text-art"></a>

<p>Text art is notoriously cumbersome for those who use screen-readers. This is because, as text art is mostly based around symbols and letters organized in a way to create an image rather than, well, text.</p>
<p>Text art is notoriously cumbersome for those who use screen-readers. This is because, as text art is mostly based around symbols and letters organized in a way to create an image rather than, well, <em>text.</em></p>

<p>When publishing text art online, people usually use the <tt><font color="#81FF7F">&#x3C;pre&#x3E;</font></tt> tag. By adding a simple <tt><font color="#81FF7F">&#x3C;aria-hidden="true"&#x3E;</font></tt> to a tag such as <tt><font color="#81FF7F">&#x3C;pre&#x3E;</font></tt> or <tt><font color="#81FF7F">&#x3C;span&#x3E;</font></tt> (example below), the content it contains will not be read by screen-readers (as described in <a href="http://www.w3.org/TR/wai-aria/states_and_properties#aria-hidden">WAI-ARIA 1.0</a>).</p>
<p>When publishing text art online, people usually use the <tt><font color="#81FF7F">&#x3C;pre&#x3E;</font></tt> tag. All test in this element are displayed in a fixed-width font and the text will preserve both spaces and line breaks - it will show up the same way that it is written in the source code. By adding a simple <tt><font color="#81FF7F">&#x3C;aria-hidden="true"&#x3E;</font></tt> to a tag such as <tt><font color="#81FF7F">&#x3C;pre&#x3E;</font></tt> or <tt><font color="#81FF7F">&#x3C;span&#x3E;</font></tt> (example below), the content it contains will not be read by screen-readers (as described in <a href="http://www.w3.org/TR/wai-aria/states_and_properties#aria-hidden">WAI-ARIA 1.0</a>).</p>

<p><blockquote><pre><font color="#81FF7F"><span aria-hidden="true"> &#x22;AAARRrrrggghhh! Back Evil! You can&#x27;t stop my quest
for The Holly Ascii..IVANOHHHEEEEE&#x22;
Expand All @@ -422,6 +422,10 @@ <h3>Contents:</h3>
,((,-,__\ &#x27;&#x27;, __\_/. __,&#x27;
&#x27;&#x27;./_._._-&#x27;</span></font></pre></blockquote></p>

<p>In the code, it will look something like this:</p>

<blockquote><font color="#81FF7F"><pre>&#x3C;pre aria-hidden=&#x22;true&#x22;&#x3E;ASCII art goes here&#x3C;/pre&#x3E;</pre></font></blockquote>

<p>Of course, it will be still necessary to describe the art if it relevant to the topic at hand. A possible solution to this issue is describing the «image» afterwards with regular text tags. If the text art is meant to be purely decorative, you can probably skip this step though.</p>

<a href="#conclusion"><h2>Final thoughts</h2></a><a name="conclusion"></a>
Expand All @@ -447,7 +451,7 @@ <h3>Contents:</h3>
document.write(year)
</script> by Cass &#xAB;Owly&#xBB; Python and Bruno &#xAB;devils&#xBB; A. of <a href="https://yourdevilfriends.art">yourdevilfriends.art</a>. Please see <a href="../humans.html">humans.html</a> for full credit and thanks. Peace and love.</p>
<p>The song used for <a href="#transcripts">Transcripts and Subtitles</a> is &#xAB;Gonna Dig Up Alec Guinness&#xBB; by Lemon Demon from the album &#xAB;Damn Skippy&#xBB; (2005). I, Cass, am doubtful that the use of this song would fall under fair use in the USA or fair dealing in the UK, but according to the <a href="http://www.lemondemon.com/Lemon%20Demon%20-%20First%20four%20albums/ReadMe.txt"><tt>ReadMe.txt</tt></a> from the official website, &#xAB;feel free to use any of this music in any video/animation projects for school or for fun&#xBB;.</p>
<p>The ASCII art used on this page was made by Joris &#xAB;b'ger&#xBB; Bellenger <a href="https://svzanten.home.xs4all.nl/ascii">from their website</a>. A <a href="https://svzanten.home.xs4all.nl/ascii/copyright.html">copyright notice page exists</a> on the site that reads:</p>
<p><a href="#text-art">The ASCII art used on this page</a> was made by Joris &#xAB;b'ger&#xBB; Bellenger <a href="https://svzanten.home.xs4all.nl/ascii">from their website</a>. A <a href="https://svzanten.home.xs4all.nl/ascii/copyright.html">copyright notice page exists</a> on the site that reads:</p>

<p><blockquote><tt>You may freely copy and distribute the ascii art found on this site provided that use of such ascii art is for non-commercial or personal use only. Use for any other purpose is expressly prohibited without the author's written permission.</tt></p>

Expand Down
2 changes: 1 addition & 1 deletion end/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
<body>
<div class="scrollable">
<div class="container">
<h1 class="title">"The End"<br>by Julian Gough</h1>
<h1 class="title">"The End"<br>Julian Gough</h1>

<p class="speaker-one">I see the player you mean.</p>

Expand Down
Binary file added howto/git/001.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added howto/git/002.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added howto/git/003.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added howto/git/004.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added howto/git/005.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
94 changes: 94 additions & 0 deletions howto/git/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,94 @@
<!DOCTYPE html>
<html lang="en">
<meta charset=UTF-8>
<head>
<title>A Very Simple Guide to Forking on GitHub | The Princess of The Night</title>
<meta charset="utf-8">
<meta itemprop="name" content="OWLY.FANS">
<meta property="og:title" content="OWLY.FANS">
<meta itemprop="description" content="OWLY.FANS">
<meta name="description" content="OWLY.FANS">
<meta property="og:description" content="OWLY.FANS">
<meta name="keywords" content="owly, cass python, neocities, neozones, brit, uk, archive, site ran by a stud, england, wales">
<meta property="og:site_name" content="XXX | OWLY.FANS">
<meta property="og:type" content="website">
<meta property="og:image" content="https://owly.fans/floppy.png">
<meta property="og:url" content="https://owly.fans">
<meta name="referrer" content="no-referrer-when-downgrade">
<a class="account-link" rel="me" href="https://digipres.club/@Owly"></a><a class="account-link" rel="me" href="https://comms.thedigitallancabin.net/cass"></a><link rel="me" href="https://github.com/DynTylluan"><link rel="me" href="https://github.com/NeoZones"><link rel="me" href="mailto:[email protected]"><link rel="me" href="https://owly.fans"><link rel="me" href="https://owlyfans.neocities.org">
<link rel="shortcut icon" type="image/x-icon" href="../../favicon.ico">
<link rel="stylesheet" href="../../style.css">
</head>
<body>
<h1>A Very Simple Guide to Forking on GitHub</h1>
<hr>
<p></p>
<p>If you are new to GitHub and you want to help with a project but don't know where to start, it might seem a little confusing what to do and where to begin, so this simple guide will show the basics of how to use forking on GitHub.</p>

<p>Before anything, you will need to have a GitHub account.</p>

<a href="#Step 1: Find the git you want to contribute to"><h3>Step 1: Find the git you want to contribute to</h3></a><a name="Step 1: Find the git you want to contribute to"></a>
<p>On your browser, go to the git that you want to make changes to, in this case, we're on <a href="https://github.com/DynTylluan/owly.fans">this git</a>. In simple terms, a git is a place that holds all of the code, pictures, sound, and everything else that is used in that project.</p>

<p>If it is for a computer game, then it will have the assets for the game, if it is a website, then it will have stuff like HTML, CSS, etc on it. Git is unique as you can see the edit history for the project and who made that change and when.</p>

<p><center><img src="001.png"></center></p>

<a href="#Step 2: Go fork yourself!"><h3>Step 2: Go fork yourself!</h3></a><a name="Step 2: Go fork yourself!"></a>
<p>On the git that you want to fork, move your mouse to <tt>Fork</tt> and then to <tt>Create a new fork</tt>. Once you do this, your browser will redirect you to a new webpage that will let you decide on what the name of your fork for the project should be. A lot of the time, it's fine to just keep this all the same, so just press <tt>Create fork</tt>.</p>

<p>And boom. You now have your own version of the project. You can make your own changes to this and the original won't be affected at all. Think of it like printing a picture off of the Internet and drawing on it - the original won't change at all.</p>

<p><center><img src="002.png"></center></p>

<a href="#Step 3: Making changes"><h3>Step 3: Making changes</h3></a><a name="Step 3: Making changes"></a>
<p>Now that you have your own version of the git, you can make changes to it. On GitHub, you can simply just drag and drop your new files to the git. You can also delete files as well by clicking on the three dots icon that will be next to <tt>Add file</tt> button that you will see when you are either in a folder or when you are in a file.</p>

<p>Once you are happy with your changes, there will be a box that says <tt>Commit changes</tt>, here you can give a title to your changes and write a description of it. Once happy, click on the green button.</p>

<p><center><img src="003.png"></center></p>

<a href="#Step 4: Making a pull request (PR)"><h3>Step 4: Making a pull request (PR)</h3></a><a name="Step 4: Making a pull request (PR)"></a>

<p>You can now make a pull request (PR). This will send a message to the git of the original project that anyone can see. In this message, people usually write down their changes, why they should be added, and anything else important.</p>

<p>Click on the <tt>Pull request</tt> button. This will lead you to a new page. Now, press on <tt>New pull request</tt>.</p>

<p>You will once again be redirected to a new page that will show all of the changes that you made to the project. When you send in a PR, other people will also be able to see the changes that you made to the project. Once happy, press the very nice <tt>Create pull request</tt> button.</p>

<p><center><img src="004.png"></center></p>

<p>Now is your time to shine. Write about all of the changes that you made and why they should be merged (added) to the project). Once you are happy with what you have done, click the <tt>Create pull request</tt> button for a final time.</p>


<a href="#Step 5: Now you wait"><h3>Step 5: Now you wait</h3></a><a name="Step 5: Now you wait"></a>

<p>Once you have sent out a new PR, the owner (and also anyone who follows the project) will get an E-Mail and a ping to say that you have sent out this request. On GitHub, there is a comment section on this page where people can talk about your pull.</p>

<p>If the owner likes it, they will merge it, effectively adding it to their project. If the owner does not agree with the changes, they can outright reject what you did. If they want something changed, you can fix up the code by changing it on the fork that you made. You will not have to send another pull request.</p>

<p><center><img src="005.png"></center></p>

<p>Hopefully, your changes <em>do</em> get added. Once they do, you will be able to see yourself be credited on the <tt>Contributors</tt> section of the original git.</p>

<p><em>Happy forking!</em></p>

<p></p>
<hr>
<p>

<p><strong>Want to support OwlyFans? <a href="../../nft">See our NFTs</a>!</strong></p> <p>The text is copyrighted 2021 - <script type="text/javascript">
var today = new Date()
var year = today.getFullYear()
document.write(year)
</script> by Cass &#xAB;Owly&#xBB; Python, licensed under the <a href="../../license/mdp" title="The Freedom Owl Public License: Modifications, Distributions, and Private Use" alt="The Freedom Owl Public License: Modifications, Distributions, and Private Use">FOPL-MDP</a>. Please see <a href="../../humans.html">humans.html</a> for full credit and thanks. Peace and love.</p><p><font color="black"><center>&#x2605;</center></font></p>
<p>
<div style="text-align:right">
<a href="http://bytemoth.nfshost.com/cd5k-net/tau">&tau;</a>
</p>
</div>
<p></p>
<script src="../../script.js"></script>
<script src="../../ruffle/ruffle.js"></script>
</body>
</html>
2 changes: 1 addition & 1 deletion start/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@
<body>
<div class="scrollable">
<div class="container">
<h1 class="title">«The Start»<br>by Cass Python</h1>
<h1 class="title">«The Start»<br>Cass Python</h1>

<p class="speaker-one">Did you see that? Look, it's them. Look down and see.</p>

Expand Down

0 comments on commit 3de2e28

Please sign in to comment.