mirrors
/
planiverse
mirror of https://git.stjo.hn/planiverse
1
0
Fork 0
Code Releases Activity
planiverse/resources/views/context.blade.php

34 lines
976 B
PHP
Raw Permalink Normal View History

Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
<!doctype html>
<html lang="{{ app()->getLocale() }}">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>{{ $mastodon_domain }} | Thread</title>
Use dynamically generated links Removed hard-coded and relative links and replaced them with dynamically generated ones. Should allow Planiverse to be served from a subfolder.
2018-09-10 04:55:08 +01:00
<link rel="stylesheet" href="{{ url('css/styles.css') }}" />
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
</head>
<body>
<h1>{{ $mastodon_domain }} | Thread</h1>
@component('navigation')
@endcomponent
Switch from hr dividers to list items Switched from using horizontal rules to divide articles to making each article a list item. This is invisible to graphical browsers, but makes identifying posts and reposts much easier in text browsers.
2018-10-08 01:51:22 +01:00
<ul>
@foreach ($context['ancestors'] as $ancestor)
@component('status', ['status' => $ancestor])
@endcomponent
@endforeach
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
Switch from hr dividers to list items Switched from using horizontal rules to divide articles to making each article a list item. This is invisible to graphical browsers, but makes identifying posts and reposts much easier in text browsers.
2018-10-08 01:51:22 +01:00
@component('status', ['status' => $status])
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
@endcomponent
Switch from hr dividers to list items Switched from using horizontal rules to divide articles to making each article a list item. This is invisible to graphical browsers, but makes identifying posts and reposts much easier in text browsers.
2018-10-08 01:51:22 +01:00
@foreach ($context['descendants'] as $descendant)
@component('status', ['status' => $descendant])
@endcomponent
@endforeach
</ul>
Implement status context page Implemented a new page that shows a status context, though I'm calling it a "thread" in the UI because I think that makes more sense for users. Also moved the action element from the notification into the event info component itself because I also want to use it to indicate when a status is a reply.
2018-08-26 21:37:55 +01:00
</body>
</html>